Registered repository migration — fleet ledger
Runtime discovery fixed the effective 12-project registry at SHA-256 ce521fc435f51c893ccf7a334cdfdedf13d1452ca987c3b5cb3bd820d4616034. Every row has a content-bearing snapshot and a terminal state.
Coverage
| Project | Before resources | State | Evidence or required action |
|---|---|---|---|
L2G | 1 legacy | Deferred | Create the missing project index, then authorise a reviewed wave. |
hanney | 21 legacy | Deferred | Preflight clean; explicit external repository write authority required. |
helix | 3 legacy | Deferred | Preflight clean; explicit external repository write authority required. |
imas-ambix | 162 legacy, 1 typed | Deferred | Four active alternate worktrees must finish or stand down. |
imas-codex | 112 legacy, 37 typed | Deferred | Three active worktrees and a nested research path violate the canonical resolver contract. |
imas-efit | 458 legacy, 439 typed | Deferred | A nested research path violates the canonical resolver contract. |
imas-standard-names | 48 legacy | Deferred | One active worktree; mounted branch is two commits behind its upstream. |
norma | 11 legacy | Deferred | Preflight clean; explicit external repository write authority required. |
nova | 49 legacy | Deferred | Two active alternate worktrees must finish or stand down. |
reckon | 26 legacy, 9 typed | Verified | 157f1c8 pushed to origin/main; 0 legacy and 35 typed after. |
tessera | 5 legacy | Deferred | Preflight clean; explicit external repository write authority required. |
vv | 4 legacy | Deferred | Preflight clean; explicit external repository write authority required. |
Snapshot and promotion guarantees
- All 12 snapshots exist under
~/.config/reckon/migrations/registry-canary-20260729/snapshots/and have independent SHA-256 values in the machine ledger. - The five clean external repositories were not selected and therefore received no writes.
- The six repositories with preflight blockers received no writes and preserve exact blocker evidence.
- Promotion stopped at the authorisation boundary; compatibility retirement remains outside this migration.
The next reviewed wave can start with helix and hanney after explicit cross-repository write authority. Blocked repositories remain independently resumable after their named conditions clear.