Audit blocked work and reconcile owner dependency requirements

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1046e-3b46-7cb0-883c-bbb4739ab936

docs/method/intake.md

@@ -49,7 +49,7 @@ the loss is occurring, while the record is being written.
   becoming aware. **`first_observed` is what starts that clock**, and this is
   the one place the register puts a hard deadline on itself. Escalation is
   immediate under trigger 1 or 2 — not batched, notwithstanding the batching
-  rule, because batching exists to protect the operator's attention and a
+  rule, because batching exists to protect the founder's attention and a
   72-hour clock outranks that.
 - **Severity is scored on what is happening, not what could.** The `L4`
   likelihood band — "already happening" — exists for exactly this and is
@@ -66,7 +66,7 @@ stopwatch.
 
 Someone outside the estate finding something and having somewhere to send it.
 
-**No such place exists.** There is no `security.txt` anywhere in the estate, no
+**At proposal time (2026-08-21), no such place was recorded.** There was no `security.txt` in the reviewed records, no
 published address, and no route from an outsider to this register. If someone
 found a flaw in a coulomb.social surface tomorrow, their options would be to
 guess an email address or say nothing.
@@ -86,6 +86,22 @@ approve. Routed on 2026-08-21 with a proposal:
 Until that exists, this register's claim to accept external reports is
 aspirational and `STATE.md` says so.
 
+### Owner disposition reconciled — 2026-10-04
+
+The custodian's committed `CUST-WP-0063-T04` records approval of the bounded
+RFC 9116 route on 2026-08-22, decision
+`051de446-7ae9-4eca-a766-14345655ab35`. The decision-API lookup returned
+404; this is an owner-file reconciliation. `the-custodian/intakes.md`
+records `CUST-IN-0011` as `routed`, owned by `policy-nexus`, with selected
+Contact URI `https://security.coulomb.social/` on 2026-08-23. Selection is
+complete; provisioning and monitored delivery are not established here.
+
+Required owner return: the production host grant, certificate/ingress,
+monitored private receipt mechanism and an end-to-end report-to-risk-nexus
+receipt, followed by the published `security.txt` location and expiry.
+The intake's 2026-08-23 DNS/TLS observation is historical, not a fresh probe.
+Risk-nexus does not provision the endpoint or publish an untested contact.
+
 ## What all four share
 
 The reporter says what is true and how they know. This register says how bad it