docs: renumber ADR-012's future gates and add the dashboard hosting migration path (issue #76) - #89
Merged
flo2517 merged 3 commits intoAug 7, 2026
Conversation
…igration path (issue #76) Two related documentation fixes, done together because both concern the same gate-numbering scheme. ## ADR-012 §6 renumbering ADR-012 reserved ADR-013 through ADR-020 for eight not-yet-written decentralization gate ADRs. Since then, ADR-013 and ADR-014 were accepted for unrelated work (the Network Validator daemon and wallet-based dashboard login -- neither is a Stage 1+ decentralization gate), and ADR-015 was about to be claimed the same way (independent bandwidth measurement, PR pending). AGENTS.md -- the binding architecture doc -- was citing these stale numbers in its prohibited- changes list, e.g. attributing "another database" to ADR-013, which actually names the Network Validator daemon. Shifted every gate in ADR-012 §6 by three (ADR-013->016 ... ADR- 020->023) and updated every citation in AGENTS.md and ROADMAP.md to match. ADR-012 itself documents the renumbering and why, in its own Consequences section, so this isn't a silent edit. ## Dashboard decentralized-hosting migration path (docs/control-plane/dashboard-decentralized-hosting-migration.md) Closes the last of #76's items that was pure documentation debt: "a migration path from the MVP same-origin UI to decentralized static hosting -- not written up anywhere yet." This is a planning note, not an ADR -- it authorizes no implementation. It explains why this is harder than "upload the build to IPFS" (same-origin CSP as today's read-endpoint auth boundary, wallet-login's origin-scoped localStorage key, multiple-Control-Plane prerequisites, rollback/versioning), and proposes a 4-stage path (decoupled build -> content-addressed mirror -> explicit alternative -> default) mirroring ADR-012 §5's own staging discipline. Explicitly defers to the real gate ADR (renumbered ADR-021) for every actual implementation decision -- pinning, retention, erasure, gateway trust. Leaves #76 open: user/operator views, RBAC, secret-redaction audit, and E2E tests are still outstanding. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ing-and-dashboard-hosting-migration
…ing-and-dashboard-hosting-migration
flo2517
deleted the
docs/adr-012-renumbering-and-dashboard-hosting-migration
branch
August 7, 2026 12:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ADR-012 §6 renumbering
ADR-012 reserved
ADR-013throughADR-020for eight not-yet-written decentralization gate ADRs. Since then,ADR-013andADR-014were accepted for unrelated work this session (the Network Validator daemon and wallet-based dashboard login — neither is a Stage 1+ decentralization gate), andADR-015was about to be claimed the same way (independent bandwidth measurement, PR pending).AGENTS.md— the binding architecture doc — was citing these stale numbers in its prohibited-changes list, e.g. attributing "another database" toADR-013, which actually names the Network Validator daemon.Shifted every gate in ADR-012 §6 by three (
ADR-013→016...ADR-020→023) and updated every citation inAGENTS.mdandROADMAP.mdto match. ADR-012 itself documents the renumbering and why, in its own Consequences section, so this isn't a silent edit.Dashboard decentralized-hosting migration path
New:
docs/control-plane/dashboard-decentralized-hosting-migration.md.Closes the last of #76's items that was pure documentation debt: "a migration path from the MVP same-origin UI to decentralized static hosting — not written up anywhere yet."
This is a planning note, not an ADR — it authorizes no implementation. It explains why this is harder than "upload the build to IPFS" (same-origin CSP as today's read-endpoint auth boundary, wallet-login's origin-scoped
localStoragekey, multiple-Control-Plane prerequisites, rollback/versioning), and proposes a 4-stage path (decoupled build → content-addressed mirror → explicit alternative → default) mirroring ADR-012 §5's own staging discipline. Explicitly defers to the real gate ADR (renumberedADR-021) for every actual implementation decision — pinning, retention, erasure, gateway trust.Testing
Docs-only change. Verified no other file in the repo (outside
.claude/worktrees/scratch dirs) still references the old gate numbers.This leaves #76 open: user/operator views, RBAC, secret-redaction audit, and E2E tests are still outstanding.
🤖 Generated with Claude Code