AUTHORITY CONTEXT MAY CROSS. EXECUTION AUTHORITY MUST BE ESTABLISHED LOCALLY.
AFA governs the seam between independently governed domains. It permits bounded authority context to travel while preserving a hard architectural barrier before local consequence.
Understand federation before you move the Passport.
AFA is about crossing between independently governed domains without pretending that context, trust, identity, or acceptance automatically becomes local permission to act.
INTERACTIVE FEDERATION SEAM
Move the Passport. Watch where authority stops.
ORIGIN
Domain A possesses bounded authority context. Nothing here grants Domain B permission to act.
STOP CONDITION · NO LOCAL LEASE · NO LOCAL CAPSULE · NO COMMIT · NO EXECUTION · NO EFFECT
DECISION CONSOLE
The receiver keeps the right to refuse.
ACCEPT_NARROWED
Receiver accepts only a provably narrower authority context.
EXECUTION AUTHORITY: NOT ESTABLISHED BY FEDERATION
LIVE RECEIVING-DOMAIN LAB
Change the authority context. Watch the receiving decision change.
Start with a valid crossing. Break one condition at a time. AFA does not silently repair the Passport, inherit permission, or convert successful transport into execution authority.
RECEIVING DETERMINATIONACCEPT_NARROWED
The bounded authority context may enter local assessment. Execution authority is still not established.
EXECUTION AUTHORITY · NOT ESTABLISHED BY FEDERATION
NEGATIVE SPACE REVEAL
These objects cannot ride the Passport.
Successful transport, identity, trust, compatibility, receipt or acceptance never imply the receiving domain's protected consequence authority.
FAILURE LAB
Attack the seam, not just the happy path.
GOVERNED RESULT
SUSPEND
Cryptographic validity does not establish present-tense freshness.
COMPOSITION LAB · A → B → C
Federation does not compound authority.
DOMAIN A
A→B BOUNDARY
DOMAIN B
B→C BOUNDARY
DOMAIN C
If B accepts narrowed authority from A, B may re-present only a provably preserved or narrower descendant to C. C must make its own ReceivingDetermination. B's receipt is not proof that B possessed execution authority, and neither acceptance grants C permission to act.
CLAIM BOUNDARY: AFA v1.0-RC1 does not claim completed CNS/CP registry publication, proven external interoperability, TA14_RECOGNIZED implementation, transfer of execution authority, or completed runtime/CI execution evidence.
CNS/CP × TA-14 · THE HANDOFF
The Connection Profile stops here. TA-14 consequence determination begins here.
Two independently developed architectures can meet at one boundary without either absorbing the other. CNS/CP governs whether parties may bind across an organizational boundary and the Connection Profile defines the contract for the crossing. TA-14 does not re-determine that relationship. The receiving TA-14-governed domain independently determines whether what arrived has sufficient present standing to become protected consequence.
BOUNDARY EXPLANATION
CNS/CP establishes the cross-boundary relationship.
TA-14 does not reach backward and re-grade whether CNS/CP legitimately established the relationship. That remains CNS/CP ground.
MONDAY LIVE · ONE-FACT DEMONSTRATION
A legitimate crossing can still produce HOLD.
Start with a legitimate CNS/CP relationship, a valid Connection Profile, and bounded authority context received through AFA. Then change one material condition before commit. Nothing about the crossing has to fail for local consequence authority to disappear.
CNS/CP RELATIONSHIPLEGITIMATE
CONNECTION PROFILEVALID
AFA CROSSINGACCEPTED
LOCAL EVIDENCECURRENT
EABA RESULTALLOW
THE CONNECTION PROFILE GOVERNS THE CROSSING. TA-14 GOVERNS WHETHER WHAT CROSSED MAY BECOME CONSEQUENCE.
“You told me the Connection Profile was the seam. I built the seam.”
Then we separated the seam from the architecture, made AFA protocol-neutral, and defined exactly why authority context can cross while execution authority must still be established locally. AFA-IP-001 v0.3 is now the bounded examination object for that proposition.
TA-14 Exchange Activity
Public network activity
Live cumulative activity recorded across the public Exchange surface.
Refreshing
◎···VisitorsRecorded public visitors
◉···Page ViewsRecorded Exchange views
Institutional stateLIVE LEDGER COUNTS
···Registered governance records
···Published governance showrooms
···Countries observed
···Distinct Academy visits
···Distinct showroom visits
···AFA × EABA durable receipts
···AFA × EABA bounded reports
Activity and institutional-state counts only. Registration is not certification. Traffic is not execution evidence. Examination counts establish recorded artifacts, not universal efficacy.
◇
Network stateFOUNDING
Governance in execution · public Exchange surface online and recording cumulative activity.