Add publication ids and metadata to estate ADRs
Prefix CUST-ADR-001–011 and record owner, revision, and review dates so policy-nexus can publish them. Estate arc42 chapter 9 updated.
This commit is contained in:
parent
80eb367dd2
commit
4039c9d1c0
10 changed files with 62 additions and 25 deletions
|
|
@ -3,9 +3,9 @@ id: coulomb-estate-architecture
|
|||
title: "Coulomb estate architecture"
|
||||
status: proposed
|
||||
owner: the-custodian
|
||||
revision: "draft-1"
|
||||
revision: "draft-2"
|
||||
version: "0.1"
|
||||
last_reviewed: "2026-08-18"
|
||||
last_reviewed: "2026-08-19"
|
||||
review_interval: 6m
|
||||
---
|
||||
|
||||
|
|
@ -177,21 +177,23 @@ already in §4 and the ADRs in §9.
|
|||
Estate ADRs in `the-custodian/canon/architecture/`. Publication ids
|
||||
still need repo prefixes (WP-0003). Status is the source front-matter.
|
||||
|
||||
| Source | Status | Decision |
|
||||
| Id | Status | Decision |
|
||||
| --- | --- | --- |
|
||||
| `adr-001-workplans-as-repo-artefacts.md` | accepted | Workplans and tasks originate as repo files; the hub is a read model. |
|
||||
| `adr-002-custodian-agent-runtime-design.md` | accepted | Custodian agent runtime design. |
|
||||
| `adr-003-materialized-derived-state.md` | accepted | Hub state is derived and fingerprint-invalidated. |
|
||||
| `adr-004-connectivity-first-network-posture.md` | accepted | Connectivity-first network posture. |
|
||||
| `adr-005-cross-repo-workplans-project-repos.md` | accepted | Cross-repo work lives in a `prj-*` repo. |
|
||||
| `adr-006-canon-federation-concept-ownership.md` | accepted | Three canons; import, do not redefine. |
|
||||
| `adr-007-workplan-identity-and-repo-worker-topology.md` | accepted | Globally unique workplan ids; one registrar. |
|
||||
| `adr-008-multi-tenancy-model.md` | superseded | Relocated to NetKingdom Tenancy Posture. |
|
||||
| `adr-010-hub-authority-and-local-cache-model.md` | proposed | Two kinds of hub data; local cache vs authority. |
|
||||
| `adr-011-federated-namespaces-and-reconciliation-limits.md` | proposed | Federated namespaces and reconciliation limits. |
|
||||
| `CUST-ADR-001` | accepted | Workplans and tasks originate as repo files; the hub is a read model. |
|
||||
| `CUST-ADR-002` | accepted | Custodian agent runtime design. |
|
||||
| `CUST-ADR-003` | accepted | Hub state is derived and fingerprint-invalidated. |
|
||||
| `CUST-ADR-004` | accepted | Connectivity-first network posture. |
|
||||
| `CUST-ADR-005` | accepted | Cross-repo work lives in a `prj-*` repo. |
|
||||
| `CUST-ADR-006` | accepted | Three canons; import, do not redefine. |
|
||||
| `CUST-ADR-007` | accepted | Globally unique workplan ids; one registrar. |
|
||||
| `adr-008` | superseded | Relocated to NetKingdom Tenancy Posture. |
|
||||
| `CUST-ADR-010` | proposed | Two kinds of hub data; local cache vs authority. |
|
||||
| `CUST-ADR-011` | proposed | Federated namespaces and reconciliation limits. |
|
||||
|
||||
Related, not estate-owned: policy-nexus ADR-0001 (addressing), NetKingdom
|
||||
Tenancy Posture (published), railiance-master ADR-0001–0008 (published).
|
||||
Related and published elsewhere: policy-nexus ADR-0001; Tenancy Posture
|
||||
and IAM Profile v0.3; railiance-master ADR-0001–0008; activity-core
|
||||
ACT-ADR-001–005; ops-warden ADR-0001–0005; railiance-platform
|
||||
RPLAT-ADR-0001–0003.
|
||||
|
||||
Unresolved WP-0003 conflicts (hosts/infra duplicate ADR-003/004,
|
||||
coulomb-social ADR-0002 partial supersession) are **not** listed as
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue