Apply GH-DEC-2026-015/016 and the audit-core registration; both blockers cleared

Origin and evidence path both landed today.

T07 origin: railiance-apps deployed decisions.coulomb.social and corrected the
hostname in this repo — not the decide.coulomb.social this workplan proposed.
Verified here rather than taken on report: both paths 200, TLS verify 0, Let's
Encrypt cert valid to 2026-12-09.

T08: audit-core registered the source with every field as proposed and landed
the detection half. INFD-IN-0003 closed. Their refinements booked — reconciliation
on the high-volume class too, since rate detects a stream stopping but never a
stream missing the particular renders that mattered, which is exactly our threat
model; and PR-12, the custody locator must be a stable non-secret identifier
because redact scans data and an existence declaration arriving without its
pointer looks complete while being useless.

INFD-IN-0004 ruled as GH-DEC-2026-015: gate-house reversed itself and nesting is
permitted for this pair. The decisive ground was not the cycle argument we led
with — our binding slice canonicalizes principal and target, two of the five
digest fields, so co-reference left us performing a partial recomputation of one
act in a second vocabulary, closer to the translation R3 forbade than nesting
is. Our ordering objection was withdrawn as mistaken.

The permission is conditioned and NOT ACTIVE until approval-engine states its
presentation exclusion as normative and tested. layer.yaml is deliberately
unchanged and carries nesting_permission_active false — we do not activate on
our own initiative.

GH-DEC-2026-016 ruled NC-03. Its §5 is live rather than hypothetical and is
booked as PR-11: principal_type: human is a property of the client registration,
structurally the same shape as the gap-route tenant, so a human-in-the-loop
control must not be discharged on it as verified humanity.

T07 stays progress: the submission to key-cape is written but unsent, blocked by
the local permission classifier rather than by any repository.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V3W1dQG7GFFM9d94jFx7iR

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1565372@bnt-lap001
Assistant-Session: 16bb2f25-b34c-49ef-8e94-5fec3567a568

intakes/intakes.md

@@ -136,7 +136,7 @@ state_hub_intake_id: "01a0880b-36f8-7d89-ab67-2c91ee16f300"
 id: INFD-IN-0003
 kind: intake
 title: The independent evidence path — what travels to audit-core
-status: open
+status: closed
 origin: residual
 origin_ref: INFD-WP-0001-T05
 priority: high
@@ -148,7 +148,27 @@ tags:
 - cross-repo
 created: '2026-09-09'
 updated: '2026-09-10'
-resolution_partial: >-
+resolution: >-
+  Closed 2026-09-10. audit-core registered this source with every field as
+  proposed — source informed-decision exact, tenants [tenant:platform], write
+  true, read false, evidence_kind load-bearing, secret_policy redact — at
+  c4016a7 as AUDIT-WP-0009-T11 / AUDIT-IN-0003, documented in their
+  docs/informed-decision-source-registration.md. The entry is inert until the
+  token exists, asserted by test rather than by reading. The two extra fields the
+  ruling added (content_exists, custody) needed no schema change: data is stored
+  verbatim into details.data and hash-chained, so a custodian cannot quietly
+  retract the assertion that content existed. One class one source with distinct
+  type values per class, because two senders would split one residual into two
+  smaller-looking ones for a component whose defining property is that the actor
+  and the evidence source are the same. Cadence accepted with the refinement that
+  BOTH heartbeat and reconciliation scope per class, and with reconciliation
+  applying to the high-volume class too since rate detects a stream stopping but
+  never a stream missing the particular renders that mattered. One design
+  consequence booked as PR-12: redact scans data, so the custody locator must be
+  a stable non-secret identifier rather than a credentialed URL, or the existence
+  declaration arrives without its pointer. Both controls are bounded and neither
+  may be described as covering the compromised-emitter residual. Reconstructability
+  is now written down on audit-core's side as well as ours. T08 unblocked.
   Doctrine half ruled 2026-09-10 as GH-DEC-2026-014; the payload remains
   audit-core's custody question and the intake stays open for it. Commitment-only
   is GRANTED for Stage 1, on the GH-DEC-2026-013 test that its distinguishing
@@ -209,7 +229,7 @@ state_hub_intake_id: "01a0880b-4421-747b-9e7f-6e9bff9d2ea3"
 id: INFD-IN-0004
 kind: intake
 title: approval-engine R3 answer conflicts with GH-DEC-2026-012 R3
-status: open
+status: closed
 origin: coordination
 origin_ref: INFD-WP-0001-T02
 priority: high