Jose Montes de Oca

Dan Barrett and Raymond Weitekamp show how OpenProse expresses reusable agent workflows as Markdown contracts, from pull request review to bank model documentation.

• A contract records the outcome and requirements; specific tools, skills or procedures can still be required where they matter.
  4:49 ↗
• A job combines a reusable contract with a trigger, such as a webhook or schedule.
  11:26 ↗
• Fresh review sessions and composed checkpoints add scrutiny, but an agent’s claim that it has fulfilled a contract remains a verification problem.
  24:43 ↗
• A successful session can be converted into a more specific reusable workflow, with a tradeoff between flexibility and potential cost savings.
  15:45 ↗