The software factory your agents work in.
Agents build in a Silo, against the repository you actually have. Prism checks the change and the evidence behind it. Monitor watches what shipped and follows a failure back to the code that caused it. Atlas and Memory carry what the team learned into the next session. Estelle proposes the fix; you merge it.
Try it on a sample project
The same workspace your team would use, running a fictional Storefront repo.
Work alongside your agents.
Bring the task, conversation, editor and terminal together. Explore a session, inspect the files, or try the sample Silo.
Reuse the payment key when checkout retries. Reproduce the timeout and add a regression test.
Claude CodeThe retry creates a new key even though the first charge may have succeeded. I’m keeping the original key and adding a regression test.
The order activity view will group these attempts by payment key.
// One payment identity, even when the request is retried.
function retryCheckout(order, payments) {
const key = order.paymentKey;
return payments.charge(order.total, key);
}
~/storefront • fix/checkout-retry Type help to list available project commands.
Sample workspace. Fictional Storefront project with local checks and a scripted repair. It does not run cloud jobs or connect to a production account. Selecting a chapter only changes the view.