Skip to content

docs(adr): Managed Fleet — canonical server, attaching clients, self-serve repair (ADR 0005) - #282

Merged
jeonghun-jj-lee merged 1 commit into
mainfrom
docs/managed-fleet-adr
Aug 8, 2026
Merged

docs(adr): Managed Fleet — canonical server, attaching clients, self-serve repair (ADR 0005)#282
jeonghun-jj-lee merged 1 commit into
mainfrom
docs/managed-fleet-adr

Conversation

@aarontrowbridge

Copy link
Copy Markdown
Member

Records the Managed Fleet design: three machine-scoped server modes (standalone/server/client), the canonical server as a product-managed system service, the extension-owned Managed Tunnel (one component, two launchers), identity handshake + fleet token, and Local fallback with Rejoin merge as the user-facing repair hatch.

Born from the 2026-08-07 triple fleet failure (silent three-week fork → fork reborn in a tunnel reconnect gap → panel stranded without self-recovery). CONTEXT.md gains the Fleet & serving glossary; the design rationale and flip conditions live in ADR 0005.

Docs-only; no code. The tracking issue for implementation follows.

…serve repair (ADR 0005)

The 2026-08-07 triple fleet failure (silent 3-week fork, fork reborn in a
tunnel reconnect gap, panel stranded with no self-recovery) designed into a
product feature: three machine-scoped server modes, canonical server as a
product-managed system service, extension-owned managed tunnel, identity
handshake + fleet token, and local fallback with rejoin merge as the repair
hatch. Glossary: CONTEXT.md gains Fleet & serving.
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.

2 participants