Article
The part of an agent demo you cannot see
Why ChaseOS Forge publishes every workflow pack's contract — inputs, steps, approval gates and enforced limits — before you run it.
The part of an agent demo I care about most is usually the part you cannot see: the rules behind the run.
Before I trust a workflow, I want to know what it takes in, the steps it follows, where it needs approval, and what it cannot do.
That is the idea behind ChaseOS Forge. The live marketplace publishes first-party workflow-pack previews, and each one publishes its contract up front.
The Software Review Pack makes this concrete. It turns repo context, diffs, tests, and review notes into an approval-ready engineering packet: six visible steps, four approval gates, and four enforced limits. You can inspect all of it before the workflow runs.
Forge is in Early Access. Paid marketplace checkout and direct installation from the public page are not live yet.
I’m building this in public because the trust model matters as much as the demo.
Explore the live contracts: chaseos.ai/forge
If you were reviewing an agent workflow, what would you need to see before letting it run?