Publish estate ADRs, platform ADRs, and IAM Profile v0.3
Some checks failed
Build and publish policy-nexus image / build-and-push (push) Failing after 48s

T04 classifies the remaining corpus. Chapter 9 on the first-wave
arc42 stubs now matches what is published.
This commit is contained in:
tegwick 2026-08-19 01:09:41 +02:00
parent 5cb88edf4d
commit 25dd59a7c6
53 changed files with 9563 additions and 787 deletions

View file

@ -195,7 +195,7 @@ on chapter 9 (now present on the estate stub; re-check in T04).
```task
id: POLICY-NEXUS-WP-0003-T04
status: progress
status: done
priority: high
```
@ -220,6 +220,10 @@ copies. Publish (after prefix/metadata packets): estate ADRs 001007 and
Profile v0.3. Remainder still `unreviewed`. Kind 5 against the estate
chapter 9: the listed estate ADRs match; no miss on that document.
Completed 2026-08-19. Remaining rows are classified: fleet-binding
records `publish`, product-local notes `local`, templates and draft
companions `local`. Unsupported formats stay inventoried, not published.
### T05 — Cleanup packets
```task
@ -276,7 +280,7 @@ publication-ready) are registered.
```task
id: POLICY-NEXUS-WP-0003-T07
status: todo
status: progress
priority: medium
```
@ -287,6 +291,10 @@ unresolved `conflict` rows as current.
This is a PR in the owning repo of the arc42 document, same as T05.
Depends on WP-0002-T04/T05 and on this workplan's T04.
2026-08-19: first-wave chapter 9 lists CUST-ADR-001011, published
Railiance/NetKingdom/activity-core/ops-warden/platform ADRs, and keeps
hosts/infra conflicts out. Stubs bumped to draft-2.
## Sequencing
T01 → T02 → T03 and T04 (T04's kind-5 slice waits on WP-0002-T04).