Persist the gap analysis to history/, open RISK-WP-0005

history/2026-08-21-intent-gap-analysis.md follows the estate's history
convention. RISK-WP-0005 carries the seven gaps, ordered so the one place
the register misreports goes first: fix_tracking is a string nobody
reads, so a stalled fix and a silent owner are currently the same thing.

The two INTENT claims with no implementation at all — incident intake and
external report — are T02. STATE.md now says both of those out loud
rather than leaving them to the assessment.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-21 08:19:57 +02:00
parent ace941ef05
commit 0ff87c22d8
3 changed files with 258 additions and 4 deletions

View file

@ -18,6 +18,7 @@ question carries a default and a date, and the check cadence is scheduled on
| `RISK-WP-0002` | active | Publication handover — T01 with `policy-nexus` |
| `RISK-WP-0003` | **finished** | Regulatory intake; the legal policy set |
| `RISK-WP-0004` | **finished** | Running the register: cadence, verification, inbox-before-grading |
| `RISK-WP-0005` | active | Closing the seven gaps in `history/2026-08-21-intent-gap-analysis.md` |
## The register
@ -87,6 +88,18 @@ python3 tools/register_check.py # just the register
statehub fix-consistency --repo risk-nexus
```
## Known, and being worked
`history/2026-08-21-intent-gap-analysis.md` graded this repo against its own
`INTENT.md`. Five of six ownership claims hold; seven gaps do not, and
`RISK-WP-0005` carries them. The two worth knowing without reading it:
- **`fix_tracking` is a string nobody reads.** The register claims to track
remediation and does not — an owner who goes quiet and a fix that goes quiet
look identical.
- **Incident and external-report intake do not exist**, though `INTENT.md`
claims both. Every finding so far came from a repo reading its own code.
## Known conditions
- **Workplans are not indexed in the hub.** C-06 on all four: this instance is