coulomb/policy-nexus
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record ADR conflicts and publish the estate arc42
Some checks failed
Build and publish policy-nexus image / build-and-push (push) Failing after 39s
Details

Browse source 
T03 writes a rulings overlay and a readable conflict list. T04 starts
relevance: five superseded, five live conflicts, estate and activity-core
ADRs marked publish-after-prefix. The Coulomb estate map is now a
published architecture document.
This commit is contained in:
tegwick 2026-08-18 22:27:05 +02:00
parent 9c6a1d3ce0
commit d1f9ac6cd7
17 changed files with 1263 additions and 126 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/POLICY-NEXUS-WP-0002-arc42-architecture-collection.md
View file

@ -196,7 +196,7 @@ even as a stub.
```task
id: POLICY-NEXUS-WP-0002-T04
status: todo
status: done
priority: high
```
@ -211,6 +211,11 @@ satisfy T01 so this repo can publish it.
This is the document WP-0003 checks other ADRs against when the conflict
is "this decision does not fit the estate".
Completed 2026-08-18 in
`the-custodian/canon/architecture/coulomb-estate_v0.1.md`. Chapters 1, 3,
4, 5.1, 9 and 12 are real. Chapter 9 lists the estate ADRs and excludes
unresolved WP-0003 conflicts.
### T05 — Remaining first-wave stubs in owning repos
```task
@ -254,7 +259,8 @@ publication stays explicit.
2026-08-18: `docs/architecture/*.md` is a policy-nexus selector.
`policy-nexus-architecture` is published at
`/architecture/policy-nexus/v0.1/`. Other first-wave documents still
`/architecture/policy-nexus/v0.1/`. Estate map is published at
`/architecture/coulomb-estate/v0.1/`. Other first-wave documents still
need owning-repo files.
### T07 — Smoke the published collection

17
workplans/POLICY-NEXUS-WP-0003-adr-review-cleanup-publish.md
View file

@ -171,7 +171,7 @@ special. First-publish-set rows start as `publish`; everything else is
```task
id: POLICY-NEXUS-WP-0003-T03
status: todo
status: done
priority: high
```
@ -185,11 +185,17 @@ estate-level). Do not resolve a custodian-level clash in this repo.
**Acceptance:** every `conflict` row is readable by the owning-repo
agent that will have to act on it.
Completed 2026-08-18. `docs/adr-review/conflicts.md` and `rulings.json`.
Kind 1 is automatic on a shared front-matter id and is a prefix packet.
Live unpublished conflicts: hosts/infra ADR-003, hosts/infra ADR-004,
coulomb-social ADR-0002. No kind-4 contradiction found. Kind 5 waits
on chapter 9 (now present on the estate stub; re-check in T04).
### T04 — Relevance filter
```task
id: POLICY-NEXUS-WP-0003-T04
status: todo
status: progress
priority: high
```
@ -207,6 +213,13 @@ publishes them. Per-repo proposals go out in T05 packets.
Kind-5 (architecture miss) runs here once WP-0002-T04 exists, and again
when T05 of that workplan lands a system document.
2026-08-18: first relevance slice is in `rulings.json`. Superseded:
custodian ADR-008, both IAM Profile predecessors, both ADR-002 host/infra
copies. Publish (after prefix/metadata packets): estate ADRs 001–007 and
010–011, activity-core 001–005, railiance-platform 0001–0003, IAM
Profile v0.3. Remainder still `unreviewed`. Kind 5 against the estate
chapter 9: the listed estate ADRs match; no miss on that document.
### T05 — Cleanup packets
```task