prose-dev Atlas OpenProse docs bound to the contracts they describe
144 documents

Run your first contract

From zero to a rendered receipt: what OpenProse is, how the router picks your path, and the exact execution semantics of prose run.

What this is

Contract authoring is expressing intent by composing requirements. Reusable contracts provide the building blocks; composition determines how their requirements apply together.

An agent performs the work, and an evaluator assesses whether the contract’s requirements are satisfied. The executor returns a result that includes the evidence needed for that assessment. Execution and evaluation repeat as needed.

This public repository supplies the Contract Markdown and ProseScript format, the open-prose skill, and reusable libraries. A responsibility expresses requirements for state maintained over time. A function performs a one-time call. ProseScript specifies required steps when their order or method matters. See requirements and composition for how these fit together.

Contracts are readable *.prose.md files. A compatible agent harness runs them using the skill and its own tools. The requirements remain the reference for success; execution depends on the host's inputs, capabilities, and permissions. Serving a standing responsibility requires a host that supports continuous operation. See Harnesses and Honest status.