Intent is not permission.
A request can enter the boundary, but it does not authorize impact.
Foundation / contract layer
The contract separates requests from effects.
Agents can ask. The Core decides. Adapters only act on admitted work.
Without that separation, a successful agent message can become an uncontrolled external change.
Core rule
Agents can ask.
The Core decides.
Adapters only act on admitted work.
Simple path
RequestDecisionAdmitted workAdapterOutcome
The core separations
Three principles keep request, execution, and result separate.
Admission is not execution.
Admitted work may continue, but the external effect has not happened yet.
Outcome is not promise.
Outcome reports what actually happened after execution was attempted.
What the contract does not claim
The contract controls the path. It does not overclaim correctness.
- It does not prove that the agent is correct.
- It does not replace human review.
- It does not make every admitted request wise.
- It only controls the path from request to external effect.
Reference vocabularyOptional appendix
Exact meanings of the terms used above.
- Intent
- A structured request submitted into the boundary.
- State view
- The current target-system state returned to the Core for checking.
- Core decision
- The result of the Core check: admitted, blocked, or needs re-check.
- Admitted work
- Work that has passed the Core decision and may be claimed by an adapter.
- Outcome
- The report of what actually happened after the adapter tried the action.
- Evidence
- Information the Core uses to decide whether the request may continue.
- Replay
- A safe explanation of the decision path without repeating the external action.
- Adapter
- The target-specific component that connects admitted work to an external system.