feat: publish reviewed architecture and ADR batch
Some checks failed
Build and publish policy-nexus image / build-and-push (push) Failing after 19s
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:
parent
023badb512
commit
93608c1f17
120 changed files with 17791 additions and 727 deletions
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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-001–005 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.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Cleanup packet — coulomb-social
|
||||
|
||||
From POLICY-NEXUS-WP-0003-T05.
|
||||
From PNEX-WP-0003-T05.
|
||||
|
||||
## Conflict
|
||||
|
||||
|
|
|
|||
|
|
@ -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.1–v0.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/`.
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
||||
|
|
|
|||
12
docs/adr-review/packets/railiance-master.md
Normal file
12
docs/adr-review/packets/railiance-master.md
Normal 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.
|
||||
|
|
@ -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
|
||||
|
|
|
|||
9
docs/adr-review/packets/state-hub.md
Normal file
9
docs/adr-review/packets/state-hub.md
Normal 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.
|
||||
|
|
@ -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
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue