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

Start the arc42 contract and publish the first ADR set

Browse source 
Add the owner-facing publication contract, a regenerable ADR review
ledger, and publication entries for this repo's ADR-0001 plus the eight
ready railiance-master ADRs.
This commit is contained in:
tegwick 2026-08-18 22:16:02 +02:00
parent 7a24e9107f
commit a8fb62a3bc
34 changed files with 9669 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -4,7 +4,7 @@ type: workplan
title: "Publish an arc42 architecture collection from owning repos"
domain: infotech
repo: policy-nexus
status: proposed
status: active
owner: the-custodian
topic_slug: policy-nexus
created: "2026-08-18"
@ -120,7 +120,7 @@ Required publication front-matter is the same contract as for ADRs: `id`,
```task
id: POLICY-NEXUS-WP-0002-T01
status: todo
status: done
priority: high
```
@ -141,6 +141,11 @@ not a second architecture). Fold the addressing into ADR-0001 only if the
**Why first:** WP-0003's relevance and conflict checks need to know what an
architecture document is.
Completed 2026-08-18 in `docs/publication-contract.md`. ADR-0001 now names
the four kinds (`standards`, `architecture`, `constitution`, `adr`). The
policy-nexus first-wave stub is at `docs/architecture/policy-nexus_v0.1.md`
and is not published until the architecture selector and inventory catch up.
### T02 — Markitect arc42 schema handoff
```task
@ -210,7 +215,7 @@ is "this decision does not fit the estate".
```task
id: POLICY-NEXUS-WP-0002-T05
status: todo
status: progress
priority: medium
```
@ -223,6 +228,11 @@ publish. Deeper chapters are the owning repo's follow-on, not a gate here.
This repo authors only `docs/architecture/policy-nexus_v0.1.md`.
2026-08-18: policy-nexus stub exists with real chapters 1, 3 and 9. It is
not in `publication.json` yet — inventory selectors do not include
`docs/architecture/` until this file is on `HEAD` and T06 reviews it.
The other four documents remain owning-repo work.
### T06 — Register and publish
```task

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

@ -4,7 +4,7 @@ type: workplan
title: "Review ADRs for conflict, keep what governs, publish the rest properly"
domain: infotech
repo: policy-nexus
status: proposed
status: active
owner: the-custodian
topic_slug: policy-nexus
created: "2026-08-18"
@ -127,7 +127,7 @@ Everything else waits on the review row.
```task
id: POLICY-NEXUS-WP-0003-T01
status: todo
status: done
priority: high
```
@ -139,11 +139,14 @@ Use `source-inventory.json` as the input set. Do not rediscover by glob.
**Output:** `docs/adr-review/` (ledger + protocol). Not published.
Completed 2026-08-18. Protocol, regenerable `ledger.json`, and
`tools/adr_review_ledger.py` are in place.
### T02 — Corpus map
```task
id: POLICY-NEXUS-WP-0003-T02
status: todo
status: done
priority: high
```
@ -159,6 +162,11 @@ relevance.
Depends on T01. Does not depend on WP-0002.
Completed 2026-08-18. `docs/adr-review/ledger.json` records front-matter,
gaps, identifier collisions, and the known ADR-008 / Tenancy Posture
special. First-publish-set rows start as `publish`; everything else is
`unreviewed`.
### T03 — Conflict and inconsistency pass
```task
@ -220,7 +228,7 @@ not as an edit of the ADR bodies. This repo applies the packet only for
```task
id: POLICY-NEXUS-WP-0003-T06
status: todo
status: progress
priority: high
```
@ -237,6 +245,11 @@ priority: high
Further registrations happen as packets return, still under this task
until the ledger has no `publish` row left unpublished.
2026-08-18: first publish set is in `publication.json` — this repo's
ADR-0001 (with publication front-matter) and railiance-master
ADR-0001–0008. Inventory dispositions match. Remaining `publish` rows
wait on later packets.
### T07 — Point the architecture documents at what remains
```task