Some checks failed
Build and publish policy-nexus image / build-and-push (push) Failing after 48s
Packets go to seven owning repos by inbox and checklist. Railiance, NetKingdom, and State Hub now have published architecture stubs.
24 lines
891 B
Markdown
24 lines
891 B
Markdown
# Cleanup packet — net-kingdom
|
|
|
|
From POLICY-NEXUS-WP-0003-T05. Do not apply in policy-nexus.
|
|
|
|
## Blocking
|
|
|
|
| File | Action |
|
|
| --- | --- |
|
|
| `canon/standards/iam-profile_v0.2.md` | Set `status: superseded`. Successor is v0.3. Id `netkingdom-iam-profile` is shared. |
|
|
| `canon/standards/iam-profile_v0.3.md` | Change `id` to `netkingdom-iam-profile-v0.3` (or similar unique id). Then it can be published. |
|
|
|
|
## Ready to publish after prefix + review metadata
|
|
|
|
`docs/adr/ADR-0006` through `ADR-0015`. Suggested ids `NK-ADR-0006` …
|
|
`NK-ADR-0015`. Add `owner`, `revision`, `last_reviewed` /
|
|
`review_interval`.
|
|
|
|
These are unreviewed for relevance except as NetKingdom chapter 9
|
|
candidates. Default if they only bind NetKingdom implementers: still
|
|
`publish` — they constrain flex-auth, key-cape, tenant-engine.
|
|
|
|
## Already published
|
|
|
|
- Tenancy Posture at `/standards/tenancy-posture/v0.1/`.
|