4
Home
odin edited this page 2026-08-07 09:13:18 +02:00
flaky-mesh operational authority
This wiki is the durable home for design intent, decisions, migration evidence,
and superseded provenance previously tracked under plans/ in the
larandar/flaky-mesh repository.
Executable work lives in Forgejo issues. Where a wiki page and the implementation disagree, the code wins.
Current authority
- Forge flow — branching, merging, and the steward (2026-08-04) — renamed Ratification by the Ting declaration (2026-08-07); body migration to follow
- Ratified fleet brief
- Target architecture
- Aspect registry specification
- Trait specification
- Migration plan and rulings
Postmortems
- Architecture postmortem — flake composition (2026-07-29)
- Buzz retirement and forge migration — operational recovery (2026-08-04)
Audits and evidence
Campaign records
- Aspect registry tickets is historical campaign provenance. A1-A4, B1-B2, and C1-C3 are implemented. Remaining B3 work is tracked by issue #1.
- Deferred work and backlog are preserved as migration provenance. Their live work was reconciled into issues #2-#6.
- Modron Auth Manager ingress is implemented provenance; later commits replaced its internal-TLS proposal with plain HTTP over the WireGuard trust boundary.
Superseded provenance
The following pages are historical evidence only. Buzz was ratified out on 2026-08-03 and none of this work may be dispatched:
- Buzz agent key minting
- Buzz sidecar specification
- Buzz sidecar tickets
- et0 relay bringup
- librefang to Buzz bridge plan
The playground VPS plan is also discarded. The ratified brief explicitly supersedes it.
Migration provenance
- Source repository:
larandar/flaky-mesh - Migration date: 2026-08-04
- Source set: 19 tracked
plans/*.mdfiles plus the untracked ratifiedplans/brief.mdbaseline required byAGENTS.md - Content policy: source pages are copied verbatim; this index classifies their current authority without rewriting history
- Repository deletion is a separate owner-approved pass after round-trip verification