coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

feat(workplan): close CUST-WP-0068-T07 — binding gap repaired and orphans ruled
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
The fleet-wide re-sync took unbacked workplans from 265 to 29. ADR-010's orphan
rules applied to the remainder: all 29 are closed, none is an ADR-001 violation,
and all are retained as provenance under the "closed hub-first records" rule.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-08-25 23:23:55 +02:00
parent 9f60894df8
commit 4ef81c7ed0
1 changed files with 14 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

18
workplans/CUST-WP-0068-cache-only-work-record-recovery.md
View file

@ -195,7 +195,7 @@ explicitly deferred.
```task
id: CUST-WP-0068-T07
status: todo
status: done
priority: high
state_hub_task_id: "f44537f2-a738-5f39-b4c1-3711de06632e"
```
@ -254,9 +254,19 @@ Order of work:
`vergabe-teilnahme` holds 16 of them, then `railiance-cluster` (3),
`railiance-platform` (3) and singles elsewhere.
4. Only then apply `ADR-010`'s orphan rules to whatever genuinely has no file:
open hub-first records are `ADR-001` violations needing a file written or an
explicit drop; closed ones may be retained as provenance where cheap.
4. **Done 2026-08-25.** `ADR-010`'s orphan rules applied to the 29 that remain.
Every one is closed — 23 `finished`, 6 `archived`, none `proposed`, `ready`,
`active` or `blocked`. None is an `ADR-001` violation: there are no open
hub-first records needing a file written or an explicit drop.
Under the rule "closed hub-first records may be retained as provenance where
cheap", all 29 are retained. They record work that happened and cost nothing
to keep. `vergabe-teilnahme` holds 16, then `railiance-cluster` (3),
`railiance-platform` (3) and singles elsewhere.
Four of them — `railiance-wp-0017`, `-0018`, `-0022`, `-0023` — will clear on
their own when `T09`'s reset runs, since they are prefix-migration residue
rather than genuine hub-first records.
Acceptance: registration records a backing file in one pass; the fleet-wide
count of file-less workplans is re-measured and explained; every remaining true