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.
May this authority context cross?
Even ACCEPT_NARROWED establishes no local commit or execution authority.
May this exact consequence occur now?
EABA evaluates consequence independently. Federation success cannot manufacture permission.
Try to move from context to consequence.
AFA: ACCEPT_NARROWED → EABA: ALLOW. The route may proceed to protected commit; effect still requires evidence.
Changed reality creates a new examination.
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.