Owner is the-custodian; regulatory intake leaves for risk-nexus

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>

INTENT.md

@@ -3,10 +3,14 @@
 ## Why this repo exists
 
 `policy-nexus` is the permanent home for the estate's **policy surface**: the
-place where policy is published, kept current, and gathered from the outside
-world. It serves `policy.coulomb.social`.
+place where policy is published and kept current. It serves
+`policy.coulomb.social`, and is **owned by `the-custodian`**.
 
-Before this repo existed, policy lived in two bad places.
+It does one thing. Gathering policy from the outside world was originally
+scoped here and moved to `risk-nexus` on 2026-08-17 — judging what an external
+rule demands of the estate is risk work, not publishing work.
+
+Before this repo existed, published policy lived in a bad place.
 
 **Published policy was temporary.** Documents that other people needed to read
 were pushed to disposable artifact pages — private URLs, no index, no history,
@@ -16,17 +20,7 @@ already been bitten by the adjacent failure: a canon draft routed for
 ratification on 2026-08-10 sat unratified in neither canon directory because
 nothing tracked that it was in flight.
 
-**Incoming policy was nowhere.** Government and regulatory policy that bears on
-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. 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.
-
-This repo exists so that policy has a permanent address, a known freshness, and
-a path in as well as out.
+This repo exists so that policy has a permanent address and a known freshness.
 
 ## What it owns
 
@@ -49,16 +43,9 @@ a path in as well as out.
 - **Currency.** Every published document carries its status, revision, and when
   it was last reviewed. A stale document is visibly stale rather than silently
   wrong.
-- **Information gathering**, scoped to **regulation bearing on the estate**.
-  The intake path for external policy: what was found, when, from where, and
-  which internal decision it bears on.
-
-  The test for inclusion is whether a rule constrains something the estate
-  actually does. A regulation that governs data the estate holds, a market it
-  sells into, or an obligation it takes on is in scope. Public policy that is
-  merely interesting is not. This is not a civic-information corpus; it is the
-  estate's own compliance surface, kept in one place so the same question is
-  not researched twice and its answer does not silently expire.
+- **Publication for `risk-nexus`.** Regulatory records and publishable findings
+  arrive as another source in the manifest. This repo renders and hosts them;
+  it does not decide what they mean or when they may be seen.
 - **The relevance loop.** Detecting when a published or gathered document has
   gone out of date, and surfacing that rather than waiting for someone to
   notice.