coulomb/state-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(workplan): reset diff is clean — zero retirements across five repositories
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Eleven files declared types canon does not define while the hub held each as a
workplan. Eight had their type corrected; three lacking identifiers were given
one continuing their repository sequence, preserving hub identifiers.

The diff now proposes no retirements anywhere tested. Nothing in the reset's
logic changed: the retirements disappeared because the sources were repaired.
The reset had been reporting the truth about a fleet whose files could not be
read.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
This commit is contained in:
tegwick 2026-08-26 10:30:26 +02:00
parent 7c45534115
commit 76a7c7ed24
1 changed files with 39 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

44
workplans/STATE-WP-0083-forge-derived-projection-reset.md
View file

@ -502,11 +502,19 @@ both cases an inference from a parser's silence rather than a check against the
directory. "The tool did not find it" was repeatedly reported as "it does not
exist".
Ten files in `workplans/` directories declare something other than
`type: workplan` — `feature`, `api`, `target`, `runbook`, `domain`,
`extension-workplan`. Some are registered as workplans on the hub. Each needs a
disposition: either the file's type is wrong, or the hub record should not exist.
Until then a reset will keep proposing to retire them.
Eleven files in `workplans/` directories declared something other than
`type: workplan` — `feature`, `runbook`, `bug-report`, `extension-workplan`,
`scorecard`, `session-note`, `adhoc` — while the hub held every one of them as a
workplan.
**Resolved 2026-08-26 by owner decision.** Canon defines six kinds — workplan,
task, intake, decision, engagement, register-entry — and none of these was among
them, so the declarations were simply wrong rather than a missing vocabulary.
Eight files with valid workplan identifiers had their type corrected. Three that
lacked an identifier as well were given one continuing their repository's
sequence, with existing hub identifiers preserved so no record was orphaned.
Zero non-workplan types now remain in any `workplans/` directory.
### The reset crashes where it should refuse
@ -532,3 +540,29 @@ Worth recording how nearly this was mis-reported. A first check run against the
*cache* returned `refused` and was almost reported as proof; it had exercised the
retirement path instead, because the cache does not hold the colliding record.
The output looked like success while testing nothing of the sort.
## Reset diff, clean (2026-08-26)
After the frontmatter repairs (`T08`) and the type corrections, the diff proposes
**no retirements at all**:
| Repository | created | updated | would retire |
|---|---|---|---|
| `the-custodian` | 3 | 71 | **0** |
| `activity-core` | 3 | 40 | **0** |
| `phase-memory` | 0 | 18 | **0** |
| `ground-game` | 0 | 9 | **0** |
| `open-cmis-tck` | 0 | 3 | **0** |
Every hub record in these repositories now derives from a file. `the-custodian`
began this sequence proposing to retire four live workplans; it proposes none.
Worth stating what changed and what did not. Nothing about the reset's logic was
altered to reach this: the retirements disappeared because the *sources* were
repaired — unterminated frontmatter, and types that made files invisible. The
reset was reporting the truth about a fleet whose files could not be read.
That is the argument for `T02` existing separately from `T03`. Had the reset
applied on first run, it would have retired live work in at least five
repositories, and every one of those retirements would have looked like tidy-up.