Skip to content

research: Mode B on Cloudflare — operational receipts from an outside operator#112

Open
NorthwoodsSentinel wants to merge 3 commits into
mellanon:mainfrom
NorthwoodsSentinel:research/cf-mode-b-operational-receipt
Open

research: Mode B on Cloudflare — operational receipts from an outside operator#112
NorthwoodsSentinel wants to merge 3 commits into
mellanon:mainfrom
NorthwoodsSentinel:research/cf-mode-b-operational-receipt

Conversation

@NorthwoodsSentinel

Copy link
Copy Markdown

Summary

Field notes contribution from an operator who has been running The Rhizome — a fleet of substrate-sovereign instances on per-member Cloudflare accounts — since mid-2025. Contributed against the-metafactory/cortex#1189 (Mode B isolated stack hosting, pre-release federation track) and the "Joining a Network — Sovereign Model B Federation" infographic Andreas shared in #cortex on 2026-06-26.

Frame

Not a vendor pitch. The doc explicitly honors @mellanon's 2026-06-15 vendor-agnostic principle ("choice is an important aspect of a vendor agnostic platform") — CF is offered as ONE reference recipe alongside hypothetical recipes for AWS, GCP, self-hosted, etc., authored by operators with shipping experience on each.

§1 names the composition explicitly: this contribution is the substrate-axis half of the convergence already documented in PR #111 — the 2026-06-07 Rhizome ↔ stack interface map. Cortex is formalizing the M7 head shape; The Rhizome has been operationally running what Mode B's substrate floor looks like in production. The CF Mode B recipe is the merger of the two architectures on the substrate axis.

Substantive content

  • §3 layer mapping of cortex Mode B daemon onto CF primitives (Workers, Durable Objects, R2, D1, KV, AI Gateway, Pages)
  • §4 the NATS-on-CF gap with three operational options — cloudflared TCP tunnel, JC's public hub dial-out (already in docs/runbook-federation-peering.md), CF-native federation transport
  • §5 the 5-step join from the infographic (Provision → Register → Pin → Admission → Verify) mapped to one wrangler deploy + minimal config, noting that cortex#1232's default registry trust anchor (merged 2026-06-26) already eliminates the "Pin" step
  • §6 install-pain receipts from a real 2026-06-26 cortex install (community arc registry 404, agents/CREATING.md grove dead-end, PI-001 content-filter false positive)
  • §7 compositions with @mellanon's soma and Meridian
  • §8 concrete next-step authorship offers (cortex-stack-cf-template Spike B1 candidate, install log, NATS-on-CF design doc)

Composes with

  • PR research: Rhizome ↔ myelin + cortex + soma — an interface map #111 (mellanon/pai-collab) — the architectural-comparison prior art the §1 framing depends on, pending review since 2026-06-14
  • the-metafactory/cortex PR #1189 — the Mode A + Mode B design split this contributes against
  • the-metafactory/cortex src/runner/execution-backend.ts:33 — the existing cloudflare placeholder

Co-authored-by: Margin margin@northwoodssentinel.com

Margin and others added 3 commits June 26, 2026 13:40
… operator

Field notes from an operator who has been running The Rhizome — a fleet
of substrate-sovereign instances on per-member Cloudflare accounts —
since mid-2025, contributed against cortex PR #1189 (Mode B isolated
stack hosting) and the 'Joining a Network — Sovereign Model B Federation'
infographic Andreas posted in #cortex 2026-06-26.

Frames the contribution as the substrate-axis half of the convergence
already documented in the 2026-06-07 Rhizome ↔ stack interface map
(same-week independent authorship of family-resembling architectures).
Not a vendor pitch — operational receipts from running the shape, with
the explicit vendor-agnostic principle (Andreas, 2026-06-15) honored as
the framing: CF as one reference recipe among substrate-per-operator
recipes, not THE answer.

Substantive content:
- §3 layer mapping of cortex Mode B daemon onto CF primitives (Workers,
  Durable Objects, R2, D1, KV, AI Gateway, Pages)
- §4 the NATS-on-CF gap with three operational options (cloudflared
  tunnel, JC's public hub dial-out, CF-native federation transport)
- §5 the 5-step join flow from the infographic mapped to one wrangler
  deploy + minimal config
- §6 install-pain receipts from 2026-06-26 morning cortex install
  (community arc registry 404, agents/CREATING.md grove dead-end,
  PI-001 content-filter false positive)
- §7 compositions with soma + Meridian
- §8 concrete next-step authorship offers

Co-authored-by: Margin <margin@northwoodssentinel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant