EMILIA Gate sits on a configured executor or system-of-record path where an action can still be refused. For one exact material action, it verifies the required evidence under relying-party-pinned trust, applies local authorization policy, and reserves admission before invocation.
The four-document path below explains the evidence Gate can consume. It does not turn a SATISFIED evidence result into an AUTHORIZED decision, prove execution, or establish complete mediation across routes a deployment has not put behind Gate.
Start with the approval artifact, carry it into the host record, establish scoped authority under the relying party's trust roots, then evaluate whether the verified, action-matched bundle satisfies that party's evidence requirement.
This is a reader-facing path over four active individual Internet-Drafts. It does not merge, replace, retire, or subordinate the rest of the protocol portfolio.
What action-bound organizational approval evidence was produced under the receipt profile?
One approval-evidence profile. It does not establish scoped authority or evidence satisfaction by itself.
Read Receipts -11 →How is named-human authorization evidence bound into an adjacent host record?
A host-agnostic by-value or by-reference binding. It does not redefine the authorization artifact or host format.
Read Binding -00 ↗Under the relying party's trust roots, did the verified key have authority for this scope?
Trust-root introduction and scoped authority. Signature verification alone does not create authority.
Read Authority -03 ↗Does the natively verified, action-matched bundle satisfy the relying party's evidence requirement?
Returns SATISFIED or UNSATISFIED. It never returns a universal authorization verdict.
Read AEC -05 →Each result has a separate owner and claim. Passing one stage never silently proves a later one.
The protocol keeps evidence portable. Gate joins that evidence to local authority and one-time admission at the protected effect boundary.
Bind the operation, target, material parameters, actor, and context before asking for authority. A receipt for a different payload does not transfer.
Check each artifact under its native rules and relying-party-pinned trust inputs, then match every required leg to the same material action.
AEC satisfaction is evidence, not permission. Gate applies local policy and current-status checks, then reserves one-time admission at the protected boundary before the provider call begins.
Preserve refusal, consumption, and outcome evidence. An indeterminate provider result enters authenticated reconciliation; it is not fresh authority to retry.
The four documents define portable evidence semantics. Gate enforces only on the configured effect-capable boundaries a deployment actually controls. A complete-mediation claim needs current deployment evidence that every in-scope route is covered.
Read the current posted receipt profile, then continue through binding, authority, and AEC.
New drafts, conformance releases, and reference updates — sent only when there’s something worth your time.
No spam. One email field, nothing else.