REHT quickstart

The integration pattern is simple: propose → authorize → enforce → receipt. REHT decides whether this exact consequence may become real now.

Minimal integration contract

1 · Describe the consequence
Bind actor/trigger, target, action, parameters, purpose and relevant resource state into an exact request.
2 · Resolve current authority
REHT evaluates current mandate, rights, purpose, constraints, authoritative state and evidence.
3 · Receive RACS
The decision contract is exactly ALLOW, DENY or ESCALATE.
4 · Enforce before effect
The Gateway/PEP releases the consequence only when the returned decision permits it. No direct effect path exists.
5 · Preserve the receipt
Record the evaluated request, authoritative inputs, decision, effect or refusal, and resulting evidence.

Failure semantics

Missing or stale authority is not inferred into existence. Unknown remains unknown. If the consequence cannot be authorized from authoritative state, execution does not silently proceed.

For a runnable public example, use the Executable Authority demo. For category semantics, see Consequence-time authorization.