cel-contracts

Open CEL boundary contracts for planned actions, planning views, execution receipts, and runtime capabilities.

cel-contracts contains pure data types shared between an agent/planner and a runtime. It is intentionally small: no LLM clients, no runtime loop, no storage backend, no policy engine.

What It Owns

• PlannedAction — what a planner asks a runtime to do.
• PlanningView — budgeted context shape a planner can consume.
• ExecutionReceipt — what the runtime actually dispatched and observed.
• DispatchRoute — adapter, CDP, accessibility, native input, focus, or other.
• ObservedEffect — whether the expected effect was observed, timed out, contradicted, or not checked.
• RuntimeCaps and related planning/run contracts.

Why It Exists

Agent frameworks and runtimes need a shared language at the boundary:

planner → PlannedAction → runtime → ExecutionReceipt

The commercial Cellar/Dilipod runtime can execute these contracts continuously, but the schema itself stays open and inspectable.

Receipt Boundary

ExecutionReceipt proves dispatch and observed effect. It does not prove the whole user goal is complete. Completion still requires post-state evidence such as adapter readback, CDP/AX state, a fresh context snapshot, screenshot, or external system confirmation.

License

Apache-2.0