Take over the renderer; defer controlled disclosure to a risk service
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>
This commit is contained in:
parent
1843ba40c9
commit
06be56fdff
6 changed files with 1004 additions and 23 deletions
|
|
@ -106,12 +106,10 @@ nobody. It reads; it does not write back. That direction is deliberate: a
|
|||
publication surface with write authority becomes a second source of truth, and
|
||||
the estate has a standing rule against exactly that.
|
||||
|
||||
The first content it must carry is already waiting: Custodian ADR-008
|
||||
(*Tenancy Posture*), which needs to reach six reviewing repos and is currently
|
||||
The first content it must carry is already waiting: NetKingdom's *Tenancy
|
||||
Posture* standard, which needs to reach six reviewing repos and is currently
|
||||
served from a disposable artifact URL. The renderer that produces that page
|
||||
from canon markdown (`the-custodian/tools/render-artifact.py`) is a prototype
|
||||
of what this repo generalises — and taking it over rather than reimplementing
|
||||
it is the intended path.
|
||||
from canon markdown now lives here as `tools/render.py`.
|
||||
|
||||
## What good looks like
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue