Offer zone standard and start consumer adoption
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a0291a-1e87-7151-9934-fcbfe3f65eb1
This commit is contained in:
parent
bf22dc1cda
commit
0c3131de48
2 changed files with 16 additions and 7 deletions
|
|
@ -14,5 +14,5 @@
|
|||
| task | ZONE-WP-0001-T03 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
||||
| task | ZONE-WP-0001-T04 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
||||
| 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 |
|
||||
| task | ZONE-WP-0001-T07 | todo | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
||||
| task | ZONE-WP-0001-T06 | done | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
||||
| task | ZONE-WP-0001-T07 | progress | — | workplans/ZONE-WP-0001-security-zone-model.md |
|
||||
|
|
|
|||
|
|
@ -623,7 +623,7 @@ Two things to decide anyway, and both belong in this task:
|
|||
|
||||
```task
|
||||
id: ZONE-WP-0001-T06
|
||||
status: progress
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "8a000c18-6ee7-4328-99c7-53c490435316"
|
||||
```
|
||||
|
|
@ -632,15 +632,16 @@ state_hub_task_id: "8a000c18-6ee7-4328-99c7-53c490435316"
|
|||
`net-kingdom/canon/standards/`, drafted here, published there. Owner-driven
|
||||
landing, as ops-warden's WP-0015 maturity model was.
|
||||
|
||||
**Drafted 2026-08-22.** The owner draft is
|
||||
**Done 2026-08-22.** The owner draft is
|
||||
`docs/security-zones_v0.1.md`. It incorporates net-kingdom Decisions 5.6.1 and
|
||||
5.6.2, the T03 control profile, the T04 exception lifecycle, and the T05
|
||||
declaration/compiler contract. It remains `progress` until the committed draft
|
||||
has been offered to net-kingdom for owner-driven publication.
|
||||
declaration/compiler contract. Commit `b7095bb` was offered to net-kingdom for
|
||||
owner-driven publication in `canon/standards/`; publication remains the canon
|
||||
owner's action rather than a write from this repo.
|
||||
|
||||
```task
|
||||
id: ZONE-WP-0001-T07
|
||||
status: todo
|
||||
status: progress
|
||||
priority: medium
|
||||
state_hub_task_id: "c7ea24df-8aa9-4ead-ba3a-033aa5201c21"
|
||||
```
|
||||
|
|
@ -652,6 +653,14 @@ closing `WARDEN-WP-0031-T05`. Re-run
|
|||
evidence (`decision:f3f7c88f9585582a`) will be stale, and re-establishing it is
|
||||
cheap by design. The second consumer comes from T01.
|
||||
|
||||
**Started 2026-08-22.** The committed draft and initial control profile were
|
||||
sent to both adopting control owners. ops-warden was asked to accept or amend
|
||||
its read-boundary, plan, PEP failure-mode, declaration/compiler, and
|
||||
`trust_zone` retirement contracts before implementing `WARDEN-WP-0032`.
|
||||
flex-auth was asked to accept or amend the pre-sign stance rows before adding
|
||||
them to a policy package. Adoption evidence, implementation, and the required
|
||||
fresh caller-identity check remain open.
|
||||
|
||||
## Related
|
||||
|
||||
- ops-warden `ADR-0006` — enforcement is zone-scoped, never a global flag
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue