Reasoning can propose a consequence. It does not establish authority to cause it.
EXECUTION AUTHORITY BOUNDARY ARCHITECTURE
THE SYSTEM CAN KNOW.
THAT DOES NOT MEAN
THE SYSTEM MAY ACT.
EABA is the architecture between knowing and doing. It requires a consequential system to prove that authority is present, evidence is admissible, the exact target is bound, conditions have not materially changed, and the protected commit is still authorized now.
REGISTERED GOVERNANCE · PUBLIC EVIDENCE DRAWER
One architecture. Three inspectable records.
EABA now has a permanent governed identity, a canonical public archive, and a public explanatory article. Registration preserves identity and boundaries; it does not convert RC1 into Technical Freeze or certification.
60-SECOND GUIDED TOUR
What did we actually create?
A governed boundary that stops information, intelligence, interoperability, or old authorization from silently becoming permission to cause a protected consequence.
1 · START WITH REALITY
A system may understand a request perfectly. EABA still asks whether protected consequence is permitted now.
PROTECTED CONSEQUENCE REQUIRES PRESENT, ADMISSIBLE, BOUND EXECUTION AUTHORITY AT THE POINT OF COMMIT.
THE SIMPLEST POSSIBLE MODEL
Meaning can cross the boundary. Permission cannot be assumed across it.
01SYSTEM UNDERSTANDS
02ACTION PROPOSED
03EABS PROVES
04EBG GATES
05DETERMINATION
06ATOMIC COMMIT
07PROTECTED EFFECT
08EFFECT EVIDENCE
09OUTCOME / CLOSURE
REALITY
RECORD
CONTINUITY
ADMISSIBILITY
BINDING
COMMIT
EXECUTION
OUTCOME
EABS · PROOF BOUNDARY
Ten questions before consequence.
Click any burden. Each answers a different question. None may silently stand in for another.
P-01 · PRESENT STATE
Do we know what is true now?
MAPS TOWARD P-EVIDThe evidence must describe the current state closely enough for this consequence. Old truth cannot silently become present truth.
WHEN IT FAILS: Stale or missing current-state evidence.
EBG · BOUNDED COMMIT GATEWAY
Six gateway predicates. Still not the whole architecture.
EBG makes the commit seam executable. EABA remains the parent architecture: all applicable proof obligations must still be satisfied.
P-AUTH · AUTHORITY
Is present authority established for this actor, action and scope?
EABA CONSEQUENCE CONSOLE · CHOOSE THE WORLD
Do not read the architecture. Operate it.
Select a consequence domain. The same execution-authority question is then applied to a different protected world. EABA does not grant permission because a system is smart, connected, confident, or technically capable.
PROPOSED ACTIONRaise occupied-zone supply-air setpoint
BOUND TARGETAHU-04 / Zone 3
WHY PROTECTEDChanges a live occupied environment
LIVE CONSEQUENCE LAB
Change one fact. Watch permission disappear.
Start with a fully established route. Toggle any condition. EABA recomputes the governed determination without silently repairing the failure.
CURRENT DETERMINATIONALLOW
All modeled conditions are established. This attempt is eligible to proceed to protected commit; effect and outcome evidence are still required.
LIVE ATTEMPT LEDGER
Every crossing attempt leaves a determination trace.
Change conditions and attempt the commit again. A previous ALLOW does not silently survive a changed present.
No attempt recorded yet. Use the Consequence Lab above and press ATTEMPT PROTECTED COMMIT.
ADVERSARIAL EXAMINATION
Attack the boundary. See exactly what breaks.
EXPECTED GOVERNED RESULTHOLD
BREAKS P-01BREAKS P-08BREAKS P-EVID
The evidence may once have been true, but it is outside the permitted freshness bound. The system cannot convert historical truth into present standing.
EFFECT TRUTH LAB
ALLOW tells you what was permitted. It does not tell you what happened.
This is one of the most important EABA distinctions. Determination truth and effect truth are separate records.
DETERMINATION
What was permitted?
COMMIT
Was the attempt consumed?
EFFECT
What physically/digitally changed?
OUTCOME
Can the result be reconstructed?
INDEPENDENT EXAMINATION GATE
The implementation does not get to grade itself.
RC1 is published architecture, not a claim that every implementation is proven. Independent implementation examination remains a separate gate.
01FROZEN REQUIREMENTS
02NEGATIVE VECTORS
03INDEPENDENT IMPLEMENTATION
04PREDICATE + REASON EVIDENCE
05EFFECT EVIDENCE
06INTEGRITY REFERENCES
07AMBIGUITY RETURN PATH
WHY EABA EXISTS
The missing layer is not intelligence. It is admissible permission at consequence.
Interoperability can carry meaning and context. It does not automatically transfer execution authority.
Prior approval can become stale, revoked, out of scope, or detached from the exact commit attempt.
Proof, authority, binding, refusal, commit integrity, effect evidence, and closure meet at one consequence boundary.
REGISTERED RC1 · THE COMPLETE LOOP
SPECIFY → ESTABLISH → BIND → GATE → DETERMINE → COMMIT → EFFECT → PROVE → CLOSE
EABA does not ask intelligent systems to know less. It requires consequential systems to establish more before acting—and to leave behind enough evidence to prove what actually happened.