OpenProse, Inc.

People who want AI agents to do work today must either write brittle step-by-step scripts or trust vague natural-language prompts, with no reusable way to express requirements like sourcing claims, limiting scope, or requiring independent review. Combining separate concerns such as source grounding, company disclosure policy, and review into one task normally means rewriting logic each time, and there is no standard way to parameterize one agreement with another (like supplying a checker to a review process). Without a shared format, verifying whether an agent's output actually satisfied the stated intent is ad hoc and hard to audit.

OpenProse defines a contract as Markdown at an address: a document that states work, supplies context, limits scope, and adopts other reusable contracts via ordinary Markdown links. Contracts can compose requirements from multiple sources (for example source grounding, a private policy document, and an independent review agreement), each contributing constraints within its stated scope, with conflicts requiring explicit resolution. Contracts can also take other contracts as parameters, such as a containing agreement that receives a Subject and a Checker, letting the review relationship itself be reused. An executor produces a result with evidence, and a separate evaluator uses the agreement and that evidence to judge which requirements are satisfied, unmet, or unresolved, with roles like independent review requiring actual separation between executor and checker.