The inventory resolves sources as sibling checkouts named by key; the checkout is
now access-engine. Four metadata-pending dispositions and four ADR-review rulings
re-keyed; no published lineage references the old key.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 101414@bnt-lap001
Assistant-Session: 60b5a221-d435-42b9-b778-983c90c7eed6
These workplans exist only in the retired local hub. Their random pre-ADR-007
identifiers are refused by C-06 as stale references, so they cannot be
registered. Deriving from the canonical record id takes no identity from
anything: central does not hold them and the old ids die with the cache.
Records central already holds were deliberately left untouched.
Refs CUST-WP-0068-T06
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
Updated by fix-consistency on 2026-08-25:
- update .custodian-brief.md for policy-nexus
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
Updated by fix-consistency on 2026-08-25:
- update .custodian-brief.md for policy-nexus
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
Harvest ops-warden's five ready records. Register ACT-ADR-001–005 after
publication metadata landed in activity-core. Markitect arc42-v1 and
the estate infospace are now the validation and retrieval path.
T03 writes a rulings overlay and a readable conflict list. T04 starts
relevance: five superseded, five live conflicts, estate and activity-core
ADRs marked publish-after-prefix. The Coulomb estate map is now a
published architecture document.
Add the owner-facing publication contract, a regenerable ADR review
ledger, and publication entries for this repo's ADR-0001 plus the eight
ready railiance-master ADRs.
WP-0002 names the first-wave architecture documents and the
markitect/infospace split. WP-0003 reviews the inventoried ADRs for
conflicts, then publishes what still governs.
Authority is three-way and stated rather than held by one repo: policy-nexus
owns the surface, the-custodian owns what counts as canon and when it is
ratified, railiance-platform owns the substrate. The middle one is the guard
against the real hazard here - a repo that reads every other repo is one step
from becoming the place where "what is current" is decided, and this says
plainly that it renders that judgement rather than making it.
The tell that the split is right is that T01 and T04 need different
competences. T01 asks what supersession means and what a permanent URL
promises; T04 is DNS and ingress. One owner would be weak at one of them.
T06 withdrawn. Regulatory intake is risk work, not publishing work, and it
wanted a different owner and a different skill from everything else in this
workplan. risk-nexus publishes through here, arriving as another manifest
source rather than as a second content type this repo curates.
The consequence is the point: this repo now does one thing, which is what made
its ownership answerable.
Domain corrected from government, a leftover from when this looked like a civic
policy site.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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>
The renderer and its stylesheet moved in from the-custodian with a make build
target, so T02 generalises something that works rather than starting from
scratch. Publication tooling belongs to the repo that owns publication.
Disclosure is resolved for now: full public is fine in build mode, where there
are no users to expose and no attacker with anything to gain. Recorded as
deferred rather than closed, because it stops being true at production - the
same blast-radius disclosure that a consumer must read becomes a map once real
tenant data exists.
Controlled disclosure is deliberately not this repo's job. Publication is about
permanence and currency; embargo is about severity, remediation and timing, and
building it here would put risk judgement in the repo least qualified to make
it. It likely wants a service of its own - a risk-nexus - with this repo as its
publication surface rather than its brain.
The only cost today is one line in T01: the addressing scheme must not assume
every document is public from birth, so that adding an embargo state later is a
new status rather than a URL migration.
First publication retargeted - the framework relocated to NetKingdom canon and
is now tenancy-posture_v0.1, five axes rather than five planes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
