railiance-platform asked and declined to guess, which was right — this registration carries the widest scope set of the pair. Nothing in this repo obtains an OAuth token; it only verifies them. Scope by scope the bundle describes no single actor: approve now belongs to informed-decision's human client, emit is redundant against the server's own heartbeat, and no requester identity was ever settled for create. Cancel CCR-2026-0020 as an owner decision rather than leave it in_flight, keep verifier custody CCR-2026-0018, and record that a future presenter gets a narrowed registration — approve must not travel with the operational scopes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HyybaE7DUXrWYrhbnESCTe Assistant: claude-code Assistant-Model: opus Assistant-Process: 1275879@bnt-lap001 Assistant-Session: eb464208-f821-41b2-bc5a-a6c33d92a8ad |
||
|---|---|---|
| .. | ||
| reviews | ||
| approval-claim.md | ||
| approval-consumption.md | ||
| approver-surface-requirements.md | ||
| audit-source-registration.md | ||
| caller-authentication.md | ||
| emission-cadence.md | ||
| flex-auth-handoff.md | ||
| gate-house-decision-request-claim-envelope.md | ||
| image-scan-2026-09-06.md | ||
| keycape-service-registrations.md | ||
| outbox-contract.md | ||
| pep-integration.md | ||
| storage-operations.md | ||