Deliver ADR cleanup packets and publish first-wave arc42 stubs

Packets go to seven owning repos by inbox and checklist. Railiance,
NetKingdom, and State Hub now have published architecture stubs.

docs/adr-review/SUMMARY.md

@@ -1,12 +1,12 @@
 # ADR review ledger summary
 
-Rows: 127
+Rows: 130
 
 ## Inventory dispositions
 
 - `excluded`: 2
 - `metadata-pending`: 105
-- `published`: 12
+- `published`: 15
 - `unsupported-format`: 8
 
 ## Proposed dispositions
@@ -14,7 +14,7 @@ Rows: 127
 - `conflict`: 5
 - `publish`: 27
 - `superseded`: 5
-- `unreviewed`: 90
+- `unreviewed`: 93
 
 ## Front-matter `id` collisions
 

docs/adr-review/ledger.json

@@ -2229,6 +2229,33 @@
       "source_repo": "net-kingdom",
       "successor": ""
     },
+    {
+      "bare_adr": "",
+      "bare_adr_collisions": [],
+      "conflict_kinds": [],
+      "file_present": true,
+      "frontmatter": {
+        "id": "net-kingdom-architecture",
+        "last_reviewed": "2026-08-18",
+        "owner": "net-kingdom",
+        "review_interval": "6m",
+        "revision": "draft-1",
+        "status": "proposed",
+        "title": "NetKingdom architecture",
+        "updated": "",
+        "version": "0.1"
+      },
+      "id_collisions": [],
+      "inventory_disposition": "published",
+      "inventory_reason": "Published through an explicit publication.json document entry.",
+      "missing_fields": [],
+      "notes": "",
+      "proposed_disposition": "unreviewed",
+      "review_notes": "",
+      "source_path": "docs/architecture/net-kingdom_v0.1.md",
+      "source_repo": "net-kingdom",
+      "successor": ""
+    },
     {
       "bare_adr": "ADR-0001",
       "bare_adr_collisions": [
@@ -2904,6 +2931,33 @@
       "source_repo": "railiance-master",
       "successor": ""
     },
+    {
+      "bare_adr": "",
+      "bare_adr_collisions": [],
+      "conflict_kinds": [],
+      "file_present": true,
+      "frontmatter": {
+        "id": "railiance-architecture",
+        "last_reviewed": "2026-08-18",
+        "owner": "railiance-master",
+        "review_interval": "6m",
+        "revision": "draft-1",
+        "status": "proposed",
+        "title": "Railiance architecture",
+        "updated": "",
+        "version": "0.1"
+      },
+      "id_collisions": [],
+      "inventory_disposition": "published",
+      "inventory_reason": "Published through an explicit publication.json document entry.",
+      "missing_fields": [],
+      "notes": "",
+      "proposed_disposition": "unreviewed",
+      "review_notes": "",
+      "source_path": "docs/architecture/railiance_v0.1.md",
+      "source_repo": "railiance-master",
+      "successor": ""
+    },
     {
       "bare_adr": "ADR-0001",
       "bare_adr_collisions": [
@@ -3296,6 +3350,33 @@
       "source_repo": "rein-aharness",
       "successor": ""
     },
+    {
+      "bare_adr": "",
+      "bare_adr_collisions": [],
+      "conflict_kinds": [],
+      "file_present": true,
+      "frontmatter": {
+        "id": "state-hub-architecture",
+        "last_reviewed": "2026-08-18",
+        "owner": "state-hub",
+        "review_interval": "6m",
+        "revision": "draft-1",
+        "status": "proposed",
+        "title": "State Hub architecture",
+        "updated": "",
+        "version": "0.1"
+      },
+      "id_collisions": [],
+      "inventory_disposition": "published",
+      "inventory_reason": "Published through an explicit publication.json document entry.",
+      "missing_fields": [],
+      "notes": "",
+      "proposed_disposition": "unreviewed",
+      "review_notes": "",
+      "source_path": "docs/architecture/state-hub_v0.1.md",
+      "source_repo": "state-hub",
+      "successor": ""
+    },
     {
       "bare_adr": "ADR-0001",
       "bare_adr_collisions": [

docs/adr-review/packets/README.md

@@ -0,0 +1,10 @@
+# Cleanup packets
+
+Per-repo checklists from POLICY-NEXUS-WP-0003-T05. They are work
+artefacts, not published policy.
+
+`policy-nexus` will not edit your ADR bodies. Apply the checklist in
+your repo, then tell this repo the publication `id` is ready.
+
+Contract: `docs/publication-contract.md`.
+Conflicts: `docs/adr-review/conflicts.md`.

docs/adr-review/packets/activity-core.md

@@ -0,0 +1,23 @@
+# Cleanup packet — activity-core
+
+From POLICY-NEXUS-WP-0003-T05.
+
+Ids `ACT-ADR-001`–`005` are already unique. This site is ready to
+publish all five once each file has:
+
+```yaml
+owner: activity-core
+revision: "accepted-1"
+last_reviewed: "YYYY-MM-DD"
+review_interval: 6m
+```
+
+| File | Why it publishes |
+| --- | --- |
+| `adr-001-event-bridge-architecture.md` | Cross-repo event bridge |
+| `adr-002-definition-format.md` | Definition format others consume |
+| `adr-003-rule-instruction-model.md` | Rule vs instruction |
+| `adr-004-producer-trust-boundary.md` | Producer trust boundary |
+| `adr-005-ops-runs-vs-dev-work-records.md` | Ops-run vs work-record split |
+
+No body rewrite required.

docs/adr-review/packets/coulomb-social.md

@@ -0,0 +1,18 @@
+# Cleanup packet — coulomb-social
+
+From POLICY-NEXUS-WP-0003-T05.
+
+## Conflict
+
+- `docs/adr/ADR-0002-space-content-forgejo-markdown.md` — status is
+  **superseded in part** by ADR-0003 / ADR-0004. Choose one:
+  1. `status: superseded` with those two as successors, or
+  2. keep a narrowed `accepted` decision and say which clause survived.
+
+Until that is one status, this site will not publish ADR-0002.
+
+## Also needed before any publish
+
+Prefix publication ids (`CSOC-ADR-0001` …). `ADR-0001` collides with
+key-cape and target-revenue. Add `owner`, `revision`, `last_reviewed`,
+`review_interval` to 0001, 0003, 0004.

docs/adr-review/packets/net-kingdom.md

@@ -0,0 +1,24 @@
+# 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/`.

docs/adr-review/packets/railiance-hosts.md

@@ -0,0 +1,24 @@
+# Cleanup packet — railiance-hosts
+
+From POLICY-NEXUS-WP-0003-T05. Shared with `railiance-infra`.
+
+## Already ruled
+
+- `docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md` — superseded by
+  ADR-003. Add YAML `status: superseded` so the body and metadata agree.
+  Byte-identical copy exists in railiance-infra.
+
+## Conflict — do not publish both
+
+These files are **byte-identical** and **accepted** in both
+`railiance-hosts` and `railiance-infra`:
+
+- `ADR-003-railiance-5repo-stack-architecture.md`
+- `ADR-004-forgejo-in-cluster-actions-runner.md`
+
+Pick one publication source. The other becomes `superseded` or a
+pointer, not a second current document. If the stack story moved to
+`railiance-master`, say so.
+
+Who rules: railiance-hosts, railiance-infra, or railiance-master.
+Nothing is published from these two ADRs until that ruling lands.

docs/adr-review/packets/railiance-infra.md

@@ -0,0 +1,23 @@
+# Cleanup packet — railiance-infra
+
+From POLICY-NEXUS-WP-0003-T05. Shared with `railiance-hosts`.
+
+## Already ruled
+
+- `docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md` — superseded by
+  ADR-003. Add YAML `status: superseded`. Identical hosts copy exists.
+
+## Conflict — do not publish both
+
+Byte-identical accepted copies also live in `railiance-hosts`:
+
+- `ADR-003-railiance-5repo-stack-architecture.md`
+- `ADR-004-forgejo-in-cluster-actions-runner.md`
+
+One current publication source, not two. See the hosts packet.
+
+## Still unreviewed here
+
+- `docs/adr/ADR-005-k3s-api-tunnel-only.md` — relevance not ruled. If it
+  still binds cluster access, add publication front-matter and a unique
+  id (`RINFRA-ADR-0005`).

docs/adr-review/packets/railiance-platform.md

@@ -0,0 +1,15 @@
+# Cleanup packet — railiance-platform
+
+From POLICY-NEXUS-WP-0003-T05.
+
+These bind other repos. Add a unique `id` (suggested
+`RPLAT-ADR-0001` … `0003`). 0002 and 0003 already have most other
+publication fields; 0001 needs `id`.
+
+| File | Disposition |
+| --- | --- |
+| `ADR-0001-s3-platform-service-boundary.md` | publish |
+| `ADR-0002-placement-policy-ownership.md` | publish (proposed is fine) |
+| `ADR-0003-decisions-live-in-the-repo.md` | publish |
+
+`docs/adr/README.md` stays excluded (directory index).

docs/adr-review/packets/the-custodian.md

@@ -0,0 +1,38 @@
+# Cleanup packet — the-custodian
+
+From POLICY-NEXUS-WP-0003-T05. Do not apply in policy-nexus.
+
+## Ready to publish after this packet
+
+Estate architecture ADRs in `canon/architecture/`. Suggested
+publication ids (filename can stay):
+
+| File | Suggested `id` |
+| --- | --- |
+| `adr-001-workplans-as-repo-artefacts.md` | `CUST-ADR-001` |
+| `adr-002-custodian-agent-runtime-design.md` | `CUST-ADR-002` |
+| `adr-003-materialized-derived-state.md` | `CUST-ADR-003` |
+| `adr-004-connectivity-first-network-posture.md` | `CUST-ADR-004` |
+| `adr-005-cross-repo-workplans-project-repos.md` | `CUST-ADR-005` |
+| `adr-006-canon-federation-concept-ownership.md` | `CUST-ADR-006` |
+| `adr-007-workplan-identity-and-repo-worker-topology.md` | `CUST-ADR-007` |
+| `adr-010-hub-authority-and-local-cache-model.md` | `CUST-ADR-010` |
+| `adr-011-federated-namespaces-and-reconciliation-limits.md` | `CUST-ADR-011` |
+
+Add to each: `owner`, `revision` (or `version`), `last_reviewed` or
+`updated`, `review_interval` (`6m` unless you declare otherwise).
+
+Bare `ADR-001`–`ADR-005` collide with coulomb-loop and kaizen-agentic.
+A prefix is required before this site can register them.
+
+## Already ruled, small fix
+
+- `adr-008-multi-tenancy-model.md` — superseded, successor Tenancy
+  Posture. No body rewrite.
+- `canon/standards/iam-profile_v0.1.md` — already superseded; point
+  `superseded_by` at `iam-profile_v0.3.md`, not v0.2.
+
+## Already published from this repo
+
+- `canon/architecture/coulomb-estate_v0.1.md` at
+  `/architecture/coulomb-estate/v0.1/`.