Architecture
Observe. Decide. Enforce. Execute.
The system is designed around a simple rule: the component proposing an action is not the component that grants authority for the effect.
Telemetry
Identity
Policy
Authority
Guarded Execute
Audit Receipt
A
Observe first
Runtime signals and context are evidence. They inform the decision boundary without silently becoming execution authority.
B
Fail closed
Missing or invalid authority is a reason to stop or verify, not a reason to guess.
C
Fixed capability paths
Early integrations deliberately prefer narrow, inspectable capabilities over broad general-purpose machine control.
Design principle
Model decision ≠ authority.
A model can recommend an action, classify risk or propose a route. That does not make the model the source of permission. Authority is evaluated independently at the execution boundary.
Current read-only MCP boundary
✓Fixed repository target
✓Read-only repo status capability
✓Policy decision returned with execution result
✓Receipt records success and effects