2026-08-19 21:20:12 +02:00
|
|
|
# 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 |
|
|
|
|
|
| --- | --- | --- | --- | --- |
|
2026-08-22 13:01:14 +02:00
|
|
|
| workplan | ZONE-WP-0001 | active | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
|
|
|
|
| task | ZONE-WP-0001-T01 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
ZONE-WP-0001-T03: maturity-derived risk defaults, and what they can attach to
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>
2026-08-19 23:23:49 +02:00
|
|
|
| task | ZONE-WP-0001-T02 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
2026-08-22 14:03:46 +02:00
|
|
|
| task | ZONE-WP-0001-T03 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
2026-08-22 13:01:14 +02:00
|
|
|
| task | ZONE-WP-0001-T04 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
2026-08-22 14:03:46 +02:00
|
|
|
| task | ZONE-WP-0001-T05 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
|
|
|
|
| task | ZONE-WP-0001-T06 | progress | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
2026-08-19 21:20:12 +02:00
|
|
|
| task | ZONE-WP-0001-T07 | todo | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
