Apply GH-DEC-2026-013 and GH-DEC-2026-014; close INFD-IN-0002

Two rulings landed and both corrected something.

GH-DEC-2026-013 accepted our binding-versus-awareness argument, wrote it into
the record as its §6, and did not change the outcome — it sharpened the defect.
Two different facts share one field named tenant: the act-scope, a property of
the act that our binding slice commits, and the principal's membership, a
property of the person that approval-engine exact-matches. Gate House's
correction stands: a binding slice that must commit the scope being entered
should commit that scope, not borrow a membership claim to stand in for it. Our
schema already does — binding.target IS the act-scope and is inside view_hash —
so no field was added, only a statement (PR-08) and a provenance record (PR-09),
since key-cape emits tenant as a bare string.

key-cape had already implemented registration-bound tenancy on 2026-09-09,
correct under both candidate rulings, so the fail-closed-at-first-use risk that
made us withhold the client strings was already retired. IN-0002 closed. The one
remaining input to T07 is the deployed origin.

GH-DEC-2026-014 granted commitment-only evidence and bounded it. It satisfies
non-alteration and NOT reconstructability, and must not be described otherwise
anywhere. It also corrected our wording of the gap: we wrote that it leaves us
able to erase the content, which understates it. Commitment-only moves integrity
out of our control and leaves availability entirely inside it — the party that
can withhold the content is the party the evidence is about. Limit 3's condition
reduced, not removed.

The grant carries a condition we did not propose and would not have thought of:
the path must assert that committed content exists and where custody sits, so
non-production is a finding attributable to the custodian rather than an
unremarkable blank. A commitment with no assertion that something is being
committed to is indistinguishable from a commitment to nothing. Booked as PR-53,
and marked not-a-reversal-candidate.

Recorded the meta-rule Gate House named, now in its third setting here: unknown
versus absent in the stance map, directory-asserted versus registration-supplied
in the tenant claim, erased versus never held in the evidence path. Wherever a
system reaches one appearance by two routes, the record must say which route.

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

SCOPE.md

@@ -103,13 +103,26 @@ Stated here because a scope file that only lists capabilities overstates them.
 - **`view_hash` is not inside the approval entry.** `POST /entries` discards its
   body by design. Correlation is `(approval_id, subject, approved_at)`, so an
   auditor holding only the approval object cannot reach the presentation.
+- **Commitment-only evidence is not reconstructability.** `GH-DEC-2026-014`
+  granted it for Stage 1 and bounded it: it satisfies non-alteration, and moves
+  integrity out of our control while leaving *availability* entirely inside it.
+  The party that can withhold the content is the party the evidence is about.
+  Narrowed by the required existence assertion; not closed.
+- **The registration-bound tenant is a declared bounded gap**, not the terminal
+  state. `GH-DEC-2026-013` ruled directory-sourced terminal and admitted
+  `key-cape`'s shape because its distinguishing case fails closed. Build to it
+  as transitional.
 - **Nothing is deployed**, so nothing is observed in production and nothing is
   contained automatically.
 
 ## Open
 
-- **Human token tenant** — blocks `T07`. A human access token cannot carry
-  `tenant:platform` today. Registration-bound versus directory-sourced; not this
-  repository's to decide alone.
-- **The independent evidence path** — mechanism unchosen; required by limit 3
-  before `T08` ships.
+- **The deployed origin** — the one remaining input to `T07`. `client_id` and
+  the callback URI must name a real origin, since redirects match exactly.
+- **`audit-core` registration and cadence** — the payload is ruled
+  (commitment-only, with the existence assertion); the sender registration and
+  whether reconciliation-plus-heartbeat suits a mixed-volume source are still
+  `audit-core`'s to answer. Required before `T08` ships.
+
+*Closed 2026-09-10:* the human token tenant (`GH-DEC-2026-013`, `key-cape`
+`329e48f`) and the evidence payload question (`GH-DEC-2026-014`).