coulomb/policy-nexus
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Retarget references after the framework moved to NetKingdom

Browse source 
The forcing case is now tenancy-posture_v0.1, not Custodian ADR-008, and the
renderer is tools/render.py rather than a path in another repo.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-17 15:42:11 +02:00
parent 06be56fdff
commit dd127578c4
2 changed files with 6 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
INTENT.md
View file

@ -20,7 +20,7 @@ nothing tracked that it was in flight.
what the estate may do — data protection, procurement rules, sector regulation
— was consulted ad hoc, at the moment somebody needed it, and never retained.
The same question was researched more than once, and the answer was never
recorded against the decision it informed. ADR-008's retention plane is a live
recorded against the decision it informed. Tenancy Posture's retention axis is a live
example: whether key destruction satisfies an erasure obligation is a question
about external policy that the estate answered in a research digest and has no
mechanism to keep current when the position moves.

11
workplans/POLICY-NEXUS-WP-0001-permanent-publication-surface.md
View file

@ -32,7 +32,7 @@ draft-5) needs review from six repos —
disposable artifact URL. Routing a document that governs six repos to a link
that may not resolve later is the problem this workplan exists to end.
ADR-008 is therefore the first publication and the acceptance test. If the site
Tenancy Posture is therefore the first publication and the acceptance test. If the site
cannot carry it correctly — five ladders, a threat matrix, an E×P grid, twelve
owner-attributed open questions — the site is not finished.
@ -50,7 +50,7 @@ per-repo ADRs live in their own repos. This repo reads and never writes back.
A publication surface with write authority is a second source of truth, and the
estate has a standing rule against that.
**The adoption stance applies** (ADR-008 §14): adopt published standards and
**The adoption stance applies** (Tenancy Posture §14): adopt published standards and
structural patterns; build tooling ground-up unless it is an established
industry standard with broad application. A static-site generator with a
plugin ecosystem is exactly what this rule excludes.
@ -92,8 +92,7 @@ breaks the one promise the repo exists to make.
### T02 — Generalise the renderer
Move `render-artifact.py` and `artifact-style.css` in, and lift them from
one-document to many.
Lift `tools/render.py` from one document to many.
- Multi-document: a manifest of sources rather than one path argument.
- Front-matter driven: title, status, revision, review date, owner from the
@ -103,7 +102,7 @@ one-document to many.
evidence chips, section rail) and keep it stdlib-only.
- Keep the "generated from canon — do not edit" marker on every page.
**Acceptance:** ADR-008 renders byte-identically in substance to the current
**Acceptance:** Tenancy Posture renders byte-identically in substance to the current
generated page, plus an index entry.
### T03 — Source ingestion
@ -139,7 +138,7 @@ record the choice.
single-node rail gives restart recovery, not high availability. Do not claim
an SLA the substrate cannot support.
- Rollback: republishing a previous build must be a single command.
- Smoke check after every deploy: the index resolves, ADR-008 resolves, and a
- Smoke check after every deploy: the index resolves, Tenancy Posture resolves, and a
known superseded URL still resolves.
### T05 — Currency and staleness