feat: publish reviewed architecture and ADR batch
Some checks failed
Build and publish policy-nexus image / build-and-push (push) Failing after 19s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a058f3-8ba0-7692-a042-9a870fc3d663
This commit is contained in:
tegwick 2026-08-31 21:34:23 +02:00
parent 023badb512
commit 93608c1f17
120 changed files with 17791 additions and 727 deletions

View file

@ -1,26 +1,25 @@
# ADR review ledger summary
Rows: 142
Rows: 162
## Inventory dispositions
- `excluded`: 3
- `metadata-pending`: 93
- `published`: 38
- `excluded`: 10
- `metadata-pending`: 84
- `published`: 60
- `unsupported-format`: 8
## Proposed dispositions
- `conflict`: 5
- `local`: 36
- `publish`: 82
- `superseded`: 5
- `unreviewed`: 14
- `local`: 50
- `publish`: 95
- `superseded`: 12
## Front-matter `id` collisions
- `ADR-001`: coulomb-loop/docs/adr/ADR-001-workplan-prefix.md, kaizen-agentic/docs/adr/ADR-001-workplan-convention.md, rein-aharness/docs/adr/ADR-001-agent-harness-architecture.md
- `ADR-002`: coulomb-loop/docs/adr/ADR-002-customer-supplier-boundary.md, kaizen-agentic/docs/adr/ADR-002-project-memory-convention.md
- `ADR-002`: coulomb-loop/docs/adr/ADR-002-customer-supplier-boundary.md, kaizen-agentic/docs/adr/ADR-002-project-memory-convention.md, rein-aharness/docs/adr/ADR-002-governed-execution-responsibility-chain.md
- `ADR-003`: coulomb-loop/docs/adr/ADR-003-cadence-ramp-policy.md, kaizen-agentic/docs/adr/ADR-003-protocols-artifact-convention.md
- `ADR-004`: coulomb-loop/docs/adr/ADR-004-repo-rotation-on-diminishing-returns.md, kaizen-agentic/docs/adr/ADR-004-project-metrics-convention.md
- `ADR-0001`: coulomb-social/docs/adr/ADR-0001-netkingdom-identity.md, key-cape/docs/adr/ADR-0001-choose-go-for-keycape.md, target-revenue/docs/adr/ADR-0001-stage0-library-stack.md
@ -28,15 +27,17 @@ Rows: 142
## Bare ADR-NNNN collisions
- `ADR-0001`: activity-core/docs/adr/adr-001-event-bridge-architecture.md, coulomb-loop/docs/adr/ADR-001-workplan-prefix.md, coulomb-social/docs/adr/ADR-0001-netkingdom-identity.md, evidence-binder/docs/adr/ADR-0001-reference-ui-surface.md, glas-harness/docs/adr/ADR-001-rein-harness-family.md, kaizen-agentic/docs/adr/ADR-001-workplan-convention.md, key-cape/docs/adr/ADR-0001-choose-go-for-keycape.md, markitect-main/docs/adr/ADR-001-client-side-debug-storage.md, ops-warden/docs/adr/ADR-0001-catalog-is-a-pointer-layer.md, policy-nexus/docs/adr/ADR-0001-addressing-and-permanence.md, railiance-master/docs/adr/ADR-0001-repository-prefix-architecture.md, railiance-platform/docs/adr/ADR-0001-s3-platform-service-boundary.md, rapp-postgres/docs/adr/ADR-0001-consumer-boundary-and-tenant-isolation.md, rein-aharness/docs/adr/ADR-001-agent-harness-architecture.md, target-revenue/docs/adr/ADR-0001-stage0-library-stack.md, the-custodian/canon/architecture/adr-001-workplans-as-repo-artefacts.md
- `ADR-0002`: activity-core/docs/adr/adr-002-definition-format.md, coulomb-loop/docs/adr/ADR-002-customer-supplier-boundary.md, coulomb-social/docs/adr/ADR-0002-space-content-forgejo-markdown.md, glas-harness/docs/adr/ADR-002-credential-brokering-and-composable-reins.md, kaizen-agentic/docs/adr/ADR-002-project-memory-convention.md, markitect-main/docs/adr/ADR-002-robustness-principle-for-production-use.md, ops-warden/docs/adr/ADR-0002-conduit-not-broker.md, railiance-hosts/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md, railiance-infra/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md, railiance-master/docs/adr/ADR-0002-rail-kubernetes-wave-1-boundary.md, railiance-platform/docs/adr/ADR-0002-placement-policy-ownership.md, rapp-postgres/docs/adr/ADR-0002-data-retention-and-erasure.md, target-revenue/docs/adr/ADR-0002-hosted-trust-service-stack.md, the-custodian/canon/architecture/adr-002-custodian-agent-runtime-design.md
- `ADR-0002`: activity-core/docs/adr/adr-002-definition-format.md, coulomb-loop/docs/adr/ADR-002-customer-supplier-boundary.md, coulomb-social/docs/adr/ADR-0002-space-content-forgejo-markdown.md, glas-harness/docs/adr/ADR-002-credential-brokering-and-composable-reins.md, kaizen-agentic/docs/adr/ADR-002-project-memory-convention.md, markitect-main/docs/adr/ADR-002-robustness-principle-for-production-use.md, ops-warden/docs/adr/ADR-0002-conduit-not-broker.md, railiance-hosts/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md, railiance-infra/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md, railiance-master/docs/adr/ADR-0002-rail-kubernetes-wave-1-boundary.md, railiance-platform/docs/adr/ADR-0002-placement-policy-ownership.md, rapp-postgres/docs/adr/ADR-0002-data-retention-and-erasure.md, rein-aharness/docs/adr/ADR-002-governed-execution-responsibility-chain.md, target-revenue/docs/adr/ADR-0002-hosted-trust-service-stack.md, the-custodian/canon/architecture/adr-002-custodian-agent-runtime-design.md
- `ADR-0003`: activity-core/docs/adr/adr-003-rule-instruction-model.md, coulomb-loop/docs/adr/ADR-003-cadence-ramp-policy.md, coulomb-social/docs/adr/ADR-0003-page-centric-markdown-sor.md, glas-harness/docs/adr/ADR-003-scheduling-and-blueprint-sourcing-stay-rein-local.md, kaizen-agentic/docs/adr/ADR-003-protocols-artifact-convention.md, ops-warden/docs/adr/ADR-0003-cover-gaps-never-silently-own-them.md, railiance-hosts/docs/adr/ADR-003-railiance-5repo-stack-architecture.md, railiance-infra/docs/adr/ADR-003-railiance-5repo-stack-architecture.md, railiance-master/docs/adr/ADR-0003-rapp-first-wave-selection.md, railiance-platform/docs/adr/ADR-0003-decisions-live-in-the-repo.md, rapp-postgres/docs/adr/ADR-0003-e3-row-level-security-contract.md, the-custodian/canon/architecture/adr-003-materialized-derived-state.md
- `ADR-0004`: activity-core/docs/adr/adr-004-producer-trust-boundary.md, coulomb-loop/docs/adr/ADR-004-repo-rotation-on-diminishing-returns.md, coulomb-social/docs/adr/ADR-0004-content-plane-thin-git-upgrades.md, glas-harness/docs/adr/ADR-004-composable-reins-stay-deferred.md, kaizen-agentic/docs/adr/ADR-004-project-metrics-convention.md, ops-warden/docs/adr/ADR-0004-agent-read-boundary-on-high-risk-lanes.md, railiance-hosts/docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md, railiance-infra/docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md, railiance-master/docs/adr/ADR-0004-first-wave-reef-rollout.md, rapp-postgres/docs/adr/ADR-0004-platform-pg-cell-ceiling.md, the-custodian/canon/architecture/adr-004-connectivity-first-network-posture.md
- `ADR-0005`: activity-core/docs/adr/adr-005-ops-runs-vs-dev-work-records.md, kaizen-agentic/docs/adr/ADR-005-scheduled-agent-execution.md, ops-warden/docs/adr/ADR-0005-implement-narrowly-route-broadly.md, railiance-infra/docs/adr/ADR-005-k3s-api-tunnel-only.md, railiance-master/docs/adr/ADR-0005-derived-rail-composition.md, the-custodian/canon/architecture/adr-005-cross-repo-workplans-project-repos.md
- `ADR-0006`: kaizen-agentic/docs/adr/ADR-006-customer-engagement-convention.md, net-kingdom/docs/adr/ADR-0006-recursive-multi-tenant-identity-authorization.md, railiance-master/docs/adr/ADR-0006-reef-production-admission.md, the-custodian/canon/architecture/adr-006-canon-federation-concept-ownership.md
- `ADR-0007`: kaizen-agentic/docs/adr/ADR-007-forward-deployed-engagement-convention.md, net-kingdom/docs/adr/ADR-0007-security-orchestration-boundary.md, railiance-master/docs/adr/ADR-0007-rapp-declaration-contract.md, the-custodian/canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md
- `ADR-0008`: net-kingdom/docs/adr/ADR-0008-object-storage-sts-credential-vending.md, railiance-master/docs/adr/ADR-0008-private-by-default-exposure.md, the-custodian/canon/architecture/adr-008-multi-tenancy-model.md
- `ADR-0010`: net-kingdom/docs/adr/ADR-0010-orchestration-vs-dependency-self-coherent-intent.md, the-custodian/canon/architecture/adr-010-hub-authority-and-local-cache-model.md
- `ADR-0006`: activity-core/docs/adr/adr-006-glas-profile-execution.md, kaizen-agentic/docs/adr/ADR-006-customer-engagement-convention.md, net-kingdom/docs/adr/ADR-0006-recursive-multi-tenant-identity-authorization.md, ops-warden/docs/adr/ADR-0006-enforcement-is-zone-scoped.md, railiance-master/docs/adr/ADR-0006-reef-production-admission.md, the-custodian/canon/architecture/adr-006-canon-federation-concept-ownership.md
- `ADR-0007`: activity-core/docs/adr/adr-007-bounded-operations.md, kaizen-agentic/docs/adr/ADR-007-forward-deployed-engagement-convention.md, net-kingdom/docs/adr/ADR-0007-security-orchestration-boundary.md, ops-warden/docs/adr/ADR-0007-build-stage-stops-at-credential-disclosure.md, railiance-master/docs/adr/ADR-0007-rapp-declaration-contract.md, the-custodian/canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md
- `ADR-0008`: net-kingdom/docs/adr/ADR-0008-object-storage-sts-credential-vending.md, ops-warden/docs/adr/ADR-0008-grade-the-path-not-the-field.md, railiance-master/docs/adr/ADR-0008-private-by-default-exposure.md, the-custodian/canon/architecture/adr-008-multi-tenancy-model.md
- `ADR-0010`: net-kingdom/docs/adr/ADR-0010-orchestration-vs-dependency-self-coherent-intent.md, ops-warden/docs/adr/ADR-0010-ops-warden-is-staff.md, the-custodian/canon/architecture/adr-010-hub-authority-and-local-cache-model.md
- `ADR-0011`: net-kingdom/docs/adr/ADR-0011-iam-profile-ownership-and-version-governance.md, the-custodian/canon/architecture/adr-011-federated-namespaces-and-reconciliation-limits.md
- `ADR-0012`: net-kingdom/docs/adr/ADR-0012-playbook-capability-contract-ownership.md, the-custodian/canon/architecture/adr-012-projection-source-and-preliminary-overlay.md
- `ADR-0009`: ops-warden/docs/adr/ADR-0009-adopt-security-zones-as-a-consumer.md, railiance-master/docs/adr/ADR-0009-netkingdom-security-layer-interaction.md
## Conflict rows

File diff suppressed because it is too large Load diff

View file

@ -1,6 +1,6 @@
# Cleanup packets
Per-repo checklists from POLICY-NEXUS-WP-0003-T05. They are work
Per-repo checklists from PNEX-WP-0003-T05. They are work
artefacts, not published policy.
`policy-nexus` will not edit your ADR bodies. Apply the checklist in

View file

@ -1,9 +1,17 @@
# Cleanup packet — activity-core
From POLICY-NEXUS-WP-0003-T05.
From PNEX-WP-0003-T05.
Ids `ACT-ADR-001``005` are already unique. This site is ready to
publish all five once each file has:
Ids `ACT-ADR-001``007` are unique and all seven records are registered for
publication.
## Owner changes applied
ACT-ADR-001005 advanced to `accepted-2` in activity-core commit `b72fdb5`.
ACT-ADR-006 and ACT-ADR-007 retain their first published revisions. The
retained-history Policy Nexus build accepts all seven records.
The required publication fields are:
```yaml
owner: activity-core
@ -19,5 +27,7 @@ review_interval: 6m
| `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 |
| `adr-006-glas-profile-execution.md` | Cross-repo execution-selection contract |
| `adr-007-bounded-operations.md` | Cross-repo mutation-boundary exception |
No body rewrite required.

View file

@ -1,6 +1,6 @@
# Cleanup packet — coulomb-social
From POLICY-NEXUS-WP-0003-T05.
From PNEX-WP-0003-T05.
## Conflict

View file

@ -1,24 +1,21 @@
# Cleanup packet — net-kingdom
From POLICY-NEXUS-WP-0003-T05. Do not apply in policy-nexus.
From PNEX-WP-0003-T05. Do not apply in policy-nexus.
## Blocking
## Completed and registered
| File | Action |
| Source set | Publication state |
| --- | --- |
| `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. |
| `canon/standards/iam-profile_v0.3.md` | Published. |
| `docs/adr/ADR-0006` through `ADR-0015` | Prefixed and published (ADR-0009 does not exist in the corpus). |
| Posture Feedback, Security Scenario Composition, Security Zones | Published as proposed. |
| Security Layer Model v0.7 | Published as the accepted current version; v0.1v0.6 remain excluded superseded history. |
## Ready to publish after prefix + review metadata
## Owner changes applied
`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
Completed in net-kingdom commit `d4e57e6`. IAM Profile v0.3 now has explicit
revision `accepted-1`; NetKingdom architecture advanced to `draft-3` and chapter
9 lists the nine accepted `NK-ADR-*` records plus the six current published
standards. The retained-history Policy Nexus build accepts both revision URLs.
- Tenancy Posture at `/standards/tenancy-posture/v0.1/`.

View file

@ -1,6 +1,6 @@
# Cleanup packet — railiance-hosts
From POLICY-NEXUS-WP-0003-T05. Shared with `railiance-infra`.
From PNEX-WP-0003-T05. Shared with `railiance-infra`.
## Already ruled

View file

@ -1,6 +1,6 @@
# Cleanup packet — railiance-infra
From POLICY-NEXUS-WP-0003-T05. Shared with `railiance-hosts`.
From PNEX-WP-0003-T05. Shared with `railiance-hosts`.
## Already ruled

View file

@ -0,0 +1,12 @@
# Cleanup packet — railiance-master
From PNEX-WP-0003-T06/T07. Do not apply in policy-nexus.
RMASTER-ADR-0009 is registered and already appears in the Railiance
architecture chapter 9.
## Owner changes applied
Railiance architecture advanced to `draft-3`; RMASTER-ADR-0006 and
RMASTER-ADR-0008 advanced to `accepted-2` in railiance-master commit `5ffd7d1`.
The retained-history Policy Nexus build accepts all three new revision URLs.

View file

@ -1,6 +1,6 @@
# Cleanup packet — railiance-platform
From POLICY-NEXUS-WP-0003-T05.
From PNEX-WP-0003-T05.
These bind other repos. Add a unique `id` (suggested
`RPLAT-ADR-0001``0003`). 0002 and 0003 already have most other

View file

@ -0,0 +1,9 @@
# Cleanup packet — state-hub
From PNEX-WP-0003-T07. Do not apply in policy-nexus.
Completed in state-hub commit `da30ce6`. The architecture advanced to
`draft-3`; chapter 9 now includes CUST-ADR-011/012, preserves the proposed
status of CUST-ADR-010/011, and describes deterministic identity instead of a
single UUID writer. The retained-history Policy Nexus build accepts the new
revision URL.

View file

@ -1,8 +1,8 @@
# Cleanup packet — the-custodian
From POLICY-NEXUS-WP-0003-T05. Do not apply in policy-nexus.
From PNEX-WP-0003-T05. Do not apply in policy-nexus.
## Ready to publish after this packet
## Published from this packet
Estate architecture ADRs in `canon/architecture/`. Suggested
publication ids (filename can stay):
@ -18,12 +18,21 @@ publication ids (filename can stay):
| `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` |
| `adr-012-projection-source-and-preliminary-overlay.md` | `CUST-ADR-012` |
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.
These records are registered with the prefixed ids above.
## Owner changes applied
CUST-ADR-001 was reviewed and amended as `accepted-2`; CUST-ADR-003 and
CUST-ADR-007 advanced to `accepted-2`; CUST-ADR-010 advanced to `draft-2`; and
the estate architecture advanced to `draft-3` with CUST-ADR-012 and the current
publication ranges. The canon changes landed in the-custodian commit `d3c6f13`.
The retained-history Policy Nexus build accepts all new revision URLs and the
currency gate is current.
## Already ruled, small fix

View file

@ -1,6 +1,6 @@
# ADR review protocol
Working protocol for POLICY-NEXUS-WP-0003. The ledger in this directory
Working protocol for PNEX-WP-0003. The ledger in this directory
is a work artefact. It is not published on `policy.coulomb.social`.
Input is `source-inventory.json` only. Do not rediscover by glob.

View file

@ -1,7 +1,7 @@
{
"schema_version": 1,
"ruled_at": "2026-08-18",
"workplan": "POLICY-NEXUS-WP-0003",
"workplan": "PNEX-WP-0003",
"note": "T03/T04 overlay. Regenerating the ledger merges these fields onto inventory facts. Kind 1 on a shared front-matter id is also applied automatically.",
"rulings": [
{
@ -992,6 +992,278 @@
"conflict_kinds": [],
"successor": "",
"review_notes": "Schema companion."
},
{
"source_repo": "activity-core",
"source_path": "docs/adr/adr-006-glas-profile-execution.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted cross-repo execution-selection contract affecting Activity Core, Glas and Rein; publication-ready."
},
{
"source_repo": "activity-core",
"source_path": "docs/adr/adr-007-bounded-operations.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted mutation-boundary exception affecting Activity Core, SBOM Nexus and Railiance Platform; publication-ready."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/posture-feedback_v0.1.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Proposed governing posture-feedback standard with complete publication metadata."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-layer-model_v0.1.md",
"proposed_disposition": "superseded",
"conflict_kinds": [],
"successor": "net-kingdom/canon/standards/security-layer-model_v0.2.md",
"review_notes": "Unpublished predecessor in the security-layer-model chain; retain in inventory but do not establish a public URL."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-layer-model_v0.2.md",
"proposed_disposition": "superseded",
"conflict_kinds": [],
"successor": "net-kingdom/canon/standards/security-layer-model_v0.3.md",
"review_notes": "Unpublished predecessor in the security-layer-model chain; retain in inventory but do not establish a public URL."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-layer-model_v0.3.md",
"proposed_disposition": "superseded",
"conflict_kinds": [],
"successor": "net-kingdom/canon/standards/security-layer-model_v0.4.md",
"review_notes": "Unpublished predecessor in the security-layer-model chain; retain in inventory but do not establish a public URL."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-layer-model_v0.4.md",
"proposed_disposition": "superseded",
"conflict_kinds": [],
"successor": "net-kingdom/canon/standards/security-layer-model_v0.5.md",
"review_notes": "Unpublished predecessor in the security-layer-model chain; retain in inventory but do not establish a public URL."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-layer-model_v0.5.md",
"proposed_disposition": "superseded",
"conflict_kinds": [],
"successor": "net-kingdom/canon/standards/security-layer-model_v0.6.md",
"review_notes": "Unpublished predecessor in the security-layer-model chain; retain in inventory but do not establish a public URL."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-layer-model_v0.6.md",
"proposed_disposition": "superseded",
"conflict_kinds": [],
"successor": "net-kingdom/canon/standards/security-layer-model_v0.7.md",
"review_notes": "Unpublished predecessor in the security-layer-model chain; retain in inventory but do not establish a public URL."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-layer-model_v0.7.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted current security-layer model, reviewed by affected consumers and publication-ready."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-scenario-composition_v0.1.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Proposed governing security-scenario composition contract with complete publication metadata."
},
{
"source_repo": "net-kingdom",
"source_path": "canon/standards/security-zones_v0.1.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Proposed governing zone model already adopted by consumers; publication-ready."
},
{
"source_repo": "ops-warden",
"source_path": "docs/adr/ADR-0006-enforcement-is-zone-scoped.md",
"proposed_disposition": "superseded",
"conflict_kinds": [],
"successor": "ops-warden/docs/adr/ADR-0009-adopt-security-zones-as-a-consumer.md",
"review_notes": "Superseded before publication by ADR-0009; retain in inventory but do not establish a public URL."
},
{
"source_repo": "ops-warden",
"source_path": "docs/adr/ADR-0007-build-stage-stops-at-credential-disclosure.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted credential-handling floor that binds catalog contributors and agent runtimes; publication-ready."
},
{
"source_repo": "ops-warden",
"source_path": "docs/adr/ADR-0008-grade-the-path-not-the-field.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted disclosure-path grading rule binding every catalog lane; publication-ready."
},
{
"source_repo": "ops-warden",
"source_path": "docs/adr/ADR-0009-adopt-security-zones-as-a-consumer.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted consumer adoption of the NetKingdom security-zone model; publication-ready and successor to ADR-0006."
},
{
"source_repo": "ops-warden",
"source_path": "docs/adr/ADR-0010-ops-warden-is-staff.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted cross-repo security-layer boundary for ops-warden; publication-ready."
},
{
"source_repo": "railiance-master",
"source_path": "docs/adr/ADR-0009-netkingdom-security-layer-interaction.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted Railiance/NetKingdom interaction boundary, already indexed by the Railiance architecture; publication-ready."
},
{
"source_repo": "rein-aharness",
"source_path": "docs/adr/ADR-002-governed-execution-responsibility-chain.md",
"proposed_disposition": "publish",
"conflict_kinds": [1],
"successor": "",
"review_notes": "Accepted cross-repo execution responsibility chain; needs a REIN-prefixed id plus owner, revision and review metadata before publication."
},
{
"source_repo": "the-custodian",
"source_path": "canon/architecture/adr-012-projection-source-and-preliminary-overlay.md",
"proposed_disposition": "publish",
"conflict_kinds": [],
"successor": "",
"review_notes": "Accepted estate projection-source and working-copy overlay rule; publication-ready."
},
{
"source_repo": "the-custodian",
"source_path": "canon/architecture/infospace/discipline/arc42.md",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Infospace retrieval metadata, explicitly excluded from the governing publication corpus."
},
{
"source_repo": "the-custodian",
"source_path": "canon/architecture/infospace/entities/coulomb-estate.md",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Infospace pointer to the owning document; publishing it would create a second copy."
},
{
"source_repo": "the-custodian",
"source_path": "canon/architecture/infospace/entities/net-kingdom.md",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Infospace pointer to the owning document; publishing it would create a second copy."
},
{
"source_repo": "the-custodian",
"source_path": "canon/architecture/infospace/entities/policy-nexus.md",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Infospace pointer to the owning document; publishing it would create a second copy."
},
{
"source_repo": "the-custodian",
"source_path": "canon/architecture/infospace/entities/railiance.md",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Infospace pointer to the owning document; publishing it would create a second copy."
},
{
"source_repo": "the-custodian",
"source_path": "canon/architecture/infospace/entities/state-hub.md",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Infospace pointer to the owning document; publishing it would create a second copy."
},
{
"source_repo": "the-custodian",
"source_path": "canon/standards/privileged-execution-control_v0.2",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Unsupported non-Markdown source stays inventoried until a renderer and explicit address exist."
},
{
"source_repo": "the-custodian",
"source_path": "canon/standards/repo-classification.allowed.yaml",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Machine-readable companion stays inventoried; no renderer or independent publication address."
},
{
"source_repo": "the-custodian",
"source_path": "canon/standards/repo-classification.exclusions.yaml",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Machine-readable companion stays inventoried; no renderer or independent publication address."
},
{
"source_repo": "the-custodian",
"source_path": "canon/standards/schemas/work-records/decision.schema.json",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Machine-readable schema companion stays inventoried; unsupported by the publication renderer."
},
{
"source_repo": "the-custodian",
"source_path": "canon/standards/schemas/work-records/engagement.schema.json",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Machine-readable schema companion stays inventoried; unsupported by the publication renderer."
},
{
"source_repo": "the-custodian",
"source_path": "canon/standards/schemas/work-records/intake.schema.json",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Machine-readable schema companion stays inventoried; unsupported by the publication renderer."
},
{
"source_repo": "the-custodian",
"source_path": "canon/standards/schemas/work-records/spine.schema.json",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Machine-readable schema companion stays inventoried; unsupported by the publication renderer."
},
{
"source_repo": "the-custodian",
"source_path": "canon/standards/work-record-types.yaml",
"proposed_disposition": "local",
"conflict_kinds": [],
"successor": "",
"review_notes": "Machine-readable companion stays inventoried; no renderer or independent publication address."
}
]
}

View file

@ -2,7 +2,7 @@
How a governing document gets a permanent address on
`https://policy.coulomb.social`. This note is the owner-facing contract
from POLICY-NEXUS-WP-0002-T01. It is not itself a published policy
from PNEX-WP-0002-T01. It is not itself a published policy
document.
`policy-nexus` publishes. It does not author your document and it does