[docs] define hub-and-spoke IPC doctrine over sovereign transport #160

Merged
Timmy merged 1 commits from timmy/issue-157-hub-spoke-ipc into main 2026-04-04 21:34:47 +00:00
Owner

Closes #157.

Summary

  • add a transport-agnostic IPC doctrine for hub-and-spoke fleet communication
  • define coordinator-first routing, anti-cascade behavior, limited peer mesh, and circuit-breaker expectations
  • anchor the doctrine in Timmy world-state, including the ongoing sovereign transport migration and the fact that Telegram is not the target backbone
  • surface the new doctrine from the repo README

Notes

  • documentation-only change
  • semantics are defined independently of Matrix, Nostr, NATS, or any future carrier
  • explicitly forbids human-token fallback patterns as the resilience plan
Closes #157. ## Summary - add a transport-agnostic IPC doctrine for hub-and-spoke fleet communication - define coordinator-first routing, anti-cascade behavior, limited peer mesh, and circuit-breaker expectations - anchor the doctrine in Timmy world-state, including the ongoing sovereign transport migration and the fact that Telegram is not the target backbone - surface the new doctrine from the repo README ## Notes - documentation-only change - semantics are defined independently of Matrix, Nostr, NATS, or any future carrier - explicitly forbids human-token fallback patterns as the resilience plan
Timmy added 1 commit 2026-04-04 21:21:05 +00:00
Author
Owner

Reviewed by Timmy. Delegated work is clean, scoped, and grounded in current world-state. Merging now.

Reviewed by Timmy. Delegated work is clean, scoped, and grounded in current world-state. Merging now.
Timmy merged commit 624b1a37b4 into main 2026-04-04 21:34:47 +00:00
Timmy deleted branch timmy/issue-157-hub-spoke-ipc 2026-04-04 21:34:48 +00:00
Sign in to join this conversation.