Inside the factory
People shape it. Agents carry it forward. Humans verify Your team verifies the plan with a planning agent.
Agents execute Role-based agents share one cloud machine and its files.
Humans validate Your team validates the result against the agreed work.
The walkthrough opens when JavaScript is available. Contact us to request early access.
The behavior you ask for.The evidence that proves it.
Humans verify · plan and requirements
Shared work
Checkout improvements Team documentRevision 03
Keep the guest cart through sign-in. C1 Guest cart survives sign-in
MI AL Mia · Product
Current step 01 / 03 Discussing
Propose a guest-cart recovery approach.
Planning agent · Claude Code harness
Expected behavior / C1 Restore the guest cart after sign-in.
AI Planning agent · Claude Code harness “Keep the guest cart in the session, then restore it after sign-in.”
Behavior and check are shaped together.
Propose Comment Agree ⌘ Agents execute Shared machine · shared files
Builder agent Claude Code harness
↔ Reviewer agent Codex harness
Test agent Codex harness
Agents build, review and refine the same files, together.
Cloud sandbox 01 · build / review / test loop Current step 01 / 04 Building
Build the guest-cart recovery path.
Builder agent · Claude Code harness
checkout/session.ts rev.03
const cart = restoreGuestCart();
continueCheckout(cart);C1 · Guest cart survives sign-in Session recovery is covered Implementation and checks stay together.
Objects / store Preview · rev.03
After signing in 1 item
Studio mugFrom guest cart $24 Current total $24
Build Review Check Evidence Current step 01 / 04 Updating rule
Record Alex’s decision in revision 04.
Planning agent · Claude Code harness
Alex’s decision Merge the guest cart with the saved cart after sign-in.
checkout/behavior.md rev.04
+ Keep both carts after sign-in.
+ Verify guest and saved items.C1 · Guest cart survives sign-in C2 · Guest + saved items retained Alex’s feedback stays linked to this revision.
Objects / store Preview · rev.03
After signing in 1 of 2 items
Studio mugFrom guest cart $24 Field notesSaved cart · missing $12 Current total $24
Rule Test Code Verify AL Humans validate Alex · Engineering
Does the result meet the need? People review the preview and evidence, then decide what happens next.
C1 Guest cart survives sign-in
AL Alex · Human reviewValidate the outcome · request a revision
Current step 01 / 02 Awaiting decision
Inspect the missing saved-cart item.
Alex · Human · Engineering
Objects / store Preview · rev.03
After signing in 1 of 2 items
Studio mugFrom guest cart $24 Field notesSaved cart · missing $12 Current total $24
Alex’s comment · checkout preview / rev.03
“My saved item is missing after sign-in.” See Alex’s feedback The checks passed. The business rule needs a decision.
Inspect preview Request change SA Human validation Sam · Platform
Cloud sandbox 02 Independent work
Payment recovery Builder agent · Codex harness
Safe retry work continues separately.
The execution loop stays inside the cloud sandbox.Agents share a machine and files. Separate work gets its own sandbox.
People shape it. Agents carry it forward. Follow one checkout change from a team decision to working software.
01 / Humans verify Keep the cart. Mia and Alex agree the expected behavior.
03 / Humans validate Show it working. A preview and checks, back to Alex.
02 / Agents execute Cart persistence Builder → reviewer → test agent ↶
SA Sandbox 02 · Sam validates Payment recovery runs independently.
Alex’s decision → revision 04 → check C2 → accepted result Original work. Complete review record.
01 / 06
People and agents, in the loop. People verify the plan. Agents execute in a cloud sandbox. People validate the outcome.
Verify → execute → validate Decisions, execution and review stay linked.
SA Sandbox 02 / Payment recovery · Sam validates Builder agent implements safe payment retries.
01 Factory 02 Shape 03 Build 04 Decide 05 Refine 06 Accept
People and agents, in the loop.
Illustrative workflow