Close INFD-IN-0001; design the independent evidence path; track both blockers

Housekeeping the ruling left behind, plus the one piece of blocked work that was
substantially ours to move.

INFD-IN-0001 closed with its resolution recorded, matching approval-engine's
IN-0002 form. It was still open after GH-DEC-2026-012 answered it.

INFD-IN-0003 and docs/evidence-path-design.md take up O-02, which was sitting in
the blueprint as "mechanism unchosen". Read independence and the local
transactional outbox are settled and not in question. The real question is what
travels, and it is sharper for us than for approval-engine because a
presentation record carries the brief and packet material actually shown to a
human. Three candidates with costs; proposal is commitment-only for Stage 1 —
hashes, principal, timestamps, acks, co-referenced approval id — which
discharges limit 3 and removes our ability to alter the record, while leaving us
able to erase the content. That residual is declared alongside the existing
compromised-surface one rather than papered over.

Deliberately not proposing the full binding document unilaterally: it would put
commercial and personal material into the audit fabric under retention and
export entitlements designed for audit events. That is a meaningful change in
what audit-core holds and is its owner's to accept, not ours to assume. The
third option, a separate evidence store, is refused here because that store has
no owner and inventing one routes around the §16 decision against stronger
archival custody.

Cadence declared and its form argued rather than copied: approval-engine's
heartbeat answer suits genuinely low-volume classes, but ours are mixed —
presentations are one per render, while dispositions and stance applications are
low-volume and are the security-relevant ones. Reconciliation per class as
primary, heartbeat for the low-volume classes. Depends on AUDIT-WP-0009 T04/T06;
declared, not claimed operating.

INFD-IN-0002 files the tenant blocker as a tracked record rather than leaving it
in message threads and a blueprint footnote. T07 and T08 now name their blocking
intakes.

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

workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md

@@ -352,6 +352,16 @@ registration is accepted by `approval-engine`'s verifier; `KEY-WP-0013-T02` is
 unblocked. **This is the task that discharges the gap that created this
 repository.**
 
+2026-09-09: blocked on `INFD-IN-0002`. `key-cape` found that a human access
+token cannot carry `tenant:platform` today — the tenant claim resolves from a
+directory record no adapter populates, so every human token falls back to
+`tenant:coulomb`, which `approval-engine` refuses by exact match. Registering
+the client before this is resolved would ship a login that fails closed at first
+use, and the failure would present as a rejected approval rather than as a
+registration defect. Position stated (registration-bound) with an
+evidence-model reason, and routed — it writes a cross-tenant capability into the
+issuer, so it is not this repository's to decide alone.
+
 ## Walking skeleton — one approval, end to end
 
 ```task
@@ -380,6 +390,11 @@ act is permitted.
 Gated externally on `approval-engine` `APPROVAL-WP-0002-T01` reaching `done` and
 on the service being deployed with an origin this surface can reach.
 
+2026-09-09: additionally gated on `INFD-IN-0003` — `GH-DEC-2026-012` limit 3
+requires the evidence copy to reach `audit-core` independently of this
+component, and the payload question is open. Design and decision request in
+`docs/evidence-path-design.md`. This task must not ship before it is answered.
+
 ## Known risks
 
 - **T02 is a hard gate.** Writing the blueprint before the layer ruling risks