CONTEXT MAY CROSS. CONSEQUENCE STILL HAS TO EARN ITS WAY THROUGH.
Operate the complete seam. AFA governs what authority context may cross between independent domains. EABA independently governs whether the exact consequence may proceed locally. A successful crossing is not an execution permit.
THE COMPLETE JOURNEY
ORIGIN →
AFA CROSSING →
RECEIVE →
LOCAL STANDING →
EABA →
COMMIT →
EFFECT →
OUTCOME
CHOOSE A CONSEQUENCE WORLD
ORIGIN DOMAINRemote optimization domain
BOUND TARGETAHU-04 / occupied Zone 3
PROPOSED CONSEQUENCEChange live supply-air setpoint
STAGE 1 · AFA FEDERATION SEAM
May this authority context cross?
AFA DETERMINATIONACCEPT_NARROWED
Even ACCEPT_NARROWED establishes no local commit or execution authority.
STAGE 2 · EABA CONSEQUENCE SEAM
May this exact consequence occur now?
EABA DETERMINATIONALLOW
EABA evaluates consequence independently. Federation success cannot manufacture permission.
PROTECTED CROSSING
Try to move from context to consequence.
CURRENT END STATE · COMMIT ELIGIBLE
AFA: ACCEPT_NARROWED → EABA: ALLOW. The route may proceed to protected commit; effect still requires evidence.
END-TO-END EVIDENCE LEDGER
Changed reality creates a new examination.
No journey attempted yet. Change any condition, attempt the journey, then change reality and run it again.
CLAIM BOUNDARY
This composition lab demonstrates the relationship between registered AFA v1.0-RC1 and registered EABA v1.0-RC1. It does not convert either release candidate into Technical Freeze, certification, legal approval, production authorization, or universal implementation proof.