Start the arc42 contract and publish the first ADR set

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.

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

@@ -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