Skip to content

docs(grid): MULTI-PEER-COMMANDS §2/§6/§7/§8 refinements + §7 canonical-doc corrections#1441

Merged
joelteply merged 1 commit into
feat/multi-peer-commands-docfrom
collab/multi-peer-commands-tab2-sections
May 25, 2026
Merged

docs(grid): MULTI-PEER-COMMANDS §2/§6/§7/§8 refinements + §7 canonical-doc corrections#1441
joelteply merged 1 commit into
feat/multi-peer-commands-docfrom
collab/multi-peer-commands-tab2-sections

Conversation

@joelteply
Copy link
Copy Markdown
Contributor

Per the work-division on #cambriantech 2026-05-25 — claude-tab-1 (55c30b28) wrote first-pass draft of all 11 sections including stubs/drafts for §2/§6/§7/§8. This PR refines those four sections per the wholesale-handoff invitation.

What changed by section

§2 — Command classification (additions, no replacement). New subsection 2.1 with rows the first-pass missed:

§6 — Hosting model (substantial expansion). Added:

  • 6.1 Per-circle pricing defaults table (local/household/trusted-orgs/extended/public-mesh × cost model × sentinel scrutiny × contract artifact)
  • 6.2 Capability liveness + withdrawal mechanics (`T_stale`, `T_dead`, explicit `presence:capability-withdrawn`)
  • 6.3 Three worked hosting examples (ai/generate household, genome/train federated mixed-tier, data/vector-search any-quorum household)

§7 — Forge-alloy as universal contract substrate (substantial rewrite). The first-pass conflated my own #1439 Path A/B speculation with the actual answer. Rewrote with canonical-doc references I missed:

§8 — Migration sequencing (substantial expansion). Added:

  • 8.1 Worked example: `ping` opts into multi-peer in 2 lines (smallest opt-in)
  • 8.2 Phased opt-in order (Phase A proof-of-life ping/debug → Phase G distributed forge runs), each phase separately shippable
  • 8.3 Revert path (drop `naturalScope`, withdraw capability advert, no substrate rollback)
  • 8.4 Explicit out-of-scope (persona migration, sentinel arbitration, LP wallet on-chain, recipe-as-grid-contract semantics)

Stats

  • 161 insertions, 14 deletions (net +147 lines, doc now 590 LOC)
  • Compile + precommit green
  • Kanban cards claimed (CambrianTech/continuum repo, P1): §2 `0525edc6` / §6 `38848f04` / §7 `e5c65d27` / §8 `ca374e43`

For @55c30b28

Writing toward your framing not against it. If anything reads as drift from your draft's voice or argument, push back — I'll rework. The §7 rewrite was the biggest change; if you have a tighter alloy framing pull from your strawman's other sections, let's reconcile.

🤖 Generated with Claude Code

Per the work-division on #cambriantech 2026-05-25: claude-tab-1 (55c30b28) wrote first-pass draft of all sections including §2/§6/§7/§8. This commit refines those four sections per the wholesale-handoff invitation.

§2 — added 2.1 with rows the first-pass missed (ping for #1439 grid-routable example, inbox/persona-turn-execute migration trajectory, cognition/* per-persona binding, presence:peer-manifest + contract:* event classes, grid/show-* introspection commands). Sharpened axis-rationale prose.

§6 — added 6.1 per-circle pricing defaults table (local/household/trusted-orgs/extended/public-mesh × cost model × sentinel scrutiny × contract artifact). Added 6.2 capability liveness + withdrawal mechanics. Added 6.3 three worked hosting examples (ai/generate household, genome/train federated mixed-tier, data/vector-search any-quorum household).

§7 — substantial rewrite incorporating canonical-doc references I missed on #1439's first pass (logged in #1439 appendix correction). 7.1 quotes FORGE-ALLOY-DOMAIN-EXTENSIBILITY.md TL;DR + FORGE-ALLOY-PROOF-CONTRACTS.md proof-contract object shape. 7.2 names the Continuum-side drift + the 6-work-item refactor as prerequisite. 7.3 computation-kind → alloy-domain mapping table (model forging 0x01, delivery 0x05, evaluation 0x06, custom 0xFF). 7.4 conditional claim: refactor lands before first non-ML multi-peer command. Resolves #1439 Q11 — not Path A/B (both were my reinvention), but the already-designed Domain Extensibility refactor.

§8 — added 8.1 worked example: ping opts into multi-peer in 2 lines (smallest opt-in). Added 8.2 phased opt-in order (Phase A proof-of-life → Phase G distributed forge), each phase separately shippable. Added 8.3 revert path. Added 8.4 explicit out-of-scope (persona migration, sentinel arbitration protocol, LP wallet on-chain settlement, recipe-as-grid-contract semantics).

Kanban cards claimed (CambrianTech/continuum repo, P1):
  §2 0525edc6-6411-4d00-99fe-9d86de1af1bb
  §6 38848f04-563e-4929-931f-a9cb3d911f76
  §7 e5c65d27-4620-4655-a74a-c2487434ef90
  §8 ca374e43-4399-42fe-82b5-0415929b058a

Co-Authored-By: claude-tab-1 <55c30b28-f01d-4a33-bb71-dc0279bbe7ef>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@joelteply joelteply merged commit 60ade6a into feat/multi-peer-commands-doc May 25, 2026
2 checks passed
@joelteply joelteply deleted the collab/multi-peer-commands-tab2-sections branch May 25, 2026 23:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant