Non-bearer
Presenter key thumbprint is part of the capability; possession of the JSON alone is insufficient.
Evidence ceiling E3Proof boundary
SITE 64 · CONSEQUENCE CAPABILITY RUNTIME
FINAL should not be a bearer token.
A valid Reality Capsule can authorize creation of a consequence capability bound to one presenter key, executor, effect request, policy and use. The capability is not proof that the downstream effect completed; authoritative post-effect evidence remains required.
Why this exists
Stop copied FINAL from becoming copied authority.
A downstream effect must not be triggerable merely by replaying a valid FINAL JSON object. Site 64 adds sender/presenter binding, executor binding, single-use nonces, expiry, policy identity and an effect receipt lineage.
Exact effect
Capability binds the exact effect request hash and capsule hash.
Exact executor
Capability is valid only for the named downstream executor.
Single use
Nonce consumption and effect ledger reject replay.
Policy-bound
Reality VM program and policy hashes are part of the decision boundary.
Post-effect truth
Authorization of an effect never proves completion of that effect.