Scope: canon and ADRs outward, estate-bearing regulation inward

Operator answered the two blocking questions, so T06 is now specifiable and
T03 has a bounded corpus: two canon trees and roughly 68 ADRs across 18
repositories. Workplans, evidence and runbooks are out - a site that publishes
everything publishes nothing in particular.

T06 gains an inclusion test (does the rule constrain something the estate
actually does), a record format, and a candidate register drawn from what the
estate demonstrably touches rather than from a list of well-known regulations -
data protection and erasure, residency, procurement via vergabe-teilnahme,
identity assurance via the aal2 class, and the agentic tenant grouping. The
register is to confirm, not to assume.

The hard rule is now in the format itself: a record states what a source said
and when. Interpretation belongs to the repo making the decision. The estate
has no legal function and this repo must not grow one by accident.

Rewrote the README, which described a broader civic corpus than the repo is
scoped to and would have attracted the wrong contributions.

One question got sharper rather than resolved: publishing every ADR across 18
repos puts the estate's architecture, known gaps and residual risks in one
indexed public place. That is right for a document consumers must read, and it
is a decision to take deliberately rather than inherit from a default.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

INTENT.md

@@ -32,16 +32,33 @@ a path in as well as out.
 
 - **`policy.coulomb.social`** — the public publication surface: its
   infrastructure, deployment, availability and rollback.
-- **Publication of estate policy.** Rendering governing documents from their
-  source repos into a durable, addressable, indexed site. The source of truth
-  stays in the owning repo; this repo owns the *publication*, not the content.
+- **Publication of estate policy**, scoped to **canon and architecture decision
+  records**. Rendering governing documents from their source repos into a
+  durable, addressable, indexed site. The source of truth stays in the owning
+  repo; this repo owns the *publication*, not the content.
+
+  The corpus in scope today is bounded and countable: two canon trees
+  (`the-custodian/canon`, `net-kingdom/canon`) and roughly 68 ADRs across 18
+  repositories. Workplans, evidence, runbooks and general documentation are
+  **out of scope** — this is a policy site, not a documentation site. That line
+  is deliberate: a site that publishes everything publishes nothing in
+  particular, and the value here is that a reader knows what governs and what
+  merely describes.
 - **Stable addressing.** A published document keeps its URL. Superseded
   versions remain reachable and are marked superseded rather than removed.
 - **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.** The intake path for external policy: what was
-  found, when, from where, and which internal decision it bears on.
+- **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.
 - **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.