tegwick
158efab24a
Operator direction: an ungraded lane inherits the default its maturity context implies — accepted in experimental context, high or critical in production. M0-M3 is the right ladder and already carries rank, phase, max_dataclass and promotion gates; what it lacks is a join to lanes, which is T02's gap. .repo-classification.yaml category cannot carry it: railiance-platform, which runs production OpenBao and owns three of RISK-F-0003's five exposed lanes, is category tooling, while net-kingdom, a canon docs repo, is product. It orders work mode, not blast radius. Also records that maturity must come from the lane's owner, not the repo holding the catalog, and that 'accepted' is an acceptance rather than a grade — it needs an owner and an expiry, so it is a second field, not a rung. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Work Records — zone-engine
Generated by
statehub fix-consistency(CUST-WP-0061-T04, work-record stage 3). Do not edit by hand — edit the source file/block listed for each record and re-run fix-consistency to refresh this index. Archived workplans are omitted; closed decisions/intakes/engagements stay listed so recently-resolved work is still visible. [auto]
| Kind | ID | Status | Lane | Source |
|---|---|---|---|---|
| workplan | ZONE-WP-0001 | proposed | — | workplans/ZONE-WP-0001-security-zone-model.md |
| task | ZONE-WP-0001-T01 | todo | — | workplans/ZONE-WP-0001-security-zone-model.md |
| task | ZONE-WP-0001-T02 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
| task | ZONE-WP-0001-T03 | todo | — | workplans/ZONE-WP-0001-security-zone-model.md |
| task | ZONE-WP-0001-T04 | todo | — | workplans/ZONE-WP-0001-security-zone-model.md |
| task | ZONE-WP-0001-T05 | todo | — | workplans/ZONE-WP-0001-security-zone-model.md |
| task | ZONE-WP-0001-T06 | todo | — | workplans/ZONE-WP-0001-security-zone-model.md |
| task | ZONE-WP-0001-T07 | todo | — | workplans/ZONE-WP-0001-security-zone-model.md |