An obstruction explains why Echo cannot lawfully produce the requested admission, execution, reading, revelation, or retained evidence under the present basis and posture.
- Rejection: named law considered a candidate and lawfully declined it.
- Obstruction: a required support, capability, basis, aperture, budget, or evidence condition is not satisfied.
- Conflict: declared footprints or causal expectations are incompatible for the attempted act.
- Internal fault: Echo failed to uphold its own runtime invariant and may require quarantine or trusted recovery.
- Absence: requested retained material is not present; absence must not be silently converted into success.
These postures must remain typed and attributable. Catch-all strings erase whether retry, authorization, repair, a new basis, or operator intervention is appropriate.
Retained material may be present, redacted, encrypted with an unavailable key, missing, corrupt, outside budget, or policy-obstructed. Content identity and semantic coordinates remain distinct: matching bytes do not prove that a reading, receipt, or witness belongs to the requested causal coordinate.
A capability presentation is checked against its authority domain, scope, subject, basis, expiry or revocation posture, and requested operation. Runtime support is checked independently. Possessing a syntactically valid capability cannot invent an unavailable observer, codec, handler, retention class, or budget.
Obstruction facts and receipts are evidence projections over admitted history. They do not create a parallel mutable error database. Public surfaces should preserve enough typed information for product adapters to map posture without importing product nouns into Echo core.