Experimental demo on a sample page. Not production-certified. Visitors never cause a paid AI call on our side.
Experimental · Atlas decides

Atlas decides. No approve button.

Your AI builds a small tool. Atlas runs it in a locked box against checks written before the build, and approves or refuses it with a reason for every rule. An approved tool goes live from the exact bytes Atlas checked.

What this proves

  1. The checks come first. Atlas writes the spec and the acceptance checks before anything is built. You confirm them on the watch page. You are confirming the problem, not the software.
  2. Atlas decides, not a person and not the AI. Your AI has no approve tool, and there is no approve button. Atlas runs the page in a locked box (pinned JavaScript engine, no network, no files, time and memory caps) and returns APPROVED or REFUSED, with a reason for every rule.
  3. Refusals are real. A page that tries to call the network, loads an outside image, stores data, runs forever, or gets a check wrong is refused, and the reason says which.
  4. What ships is what was checked. An approved page is released at once from the exact bytes, with a browser policy that blocks all network calls. The receipt page fetches the live page fresh and re-hashes it, so anyone can see the bytes still match. If anything changed afterward, the check fails.

Bottom line: a written standard decides, the decision has reasons, and the result carries proof.

This is an experimental demo of small, single-page tools (a commission split, or a calculator, form or checklist you describe with worked examples). APPROVED means the page passed these written checks and rules. It does not prove the page has no defects. Not production-certified. Visitors never cause a paid AI call on our side.

Atlas, the AtlasClose Magistrate, a fluffy coastal dog by the beach
Atlas · The Magistrate

Try it: 3 steps

You don't need an account, a sign-in, or a key.

  1. Add the connector. In your AI app, add a connector with this address.
    https://demo.atlasclose.com/factory2/mcp
  2. Paste this line into your AI.
    Use atlas.factory2 to build me a commission split tool (tool_type commission_split). Give me the watch link, then keep going on your own, without waiting for me, until you have the live tool and receipt links.
  3. Press Confirm on the watch link. Your AI gives you a watch link. Open it and press the big Confirm button. That's all. Your AI keeps going on its own and comes back with your tool and its receipt. You don't need to type anything else.

This is a separate demo from the factory demo with a person's Approve button. Here, Atlas makes the decision on the written checks.

Optional: your own small calculator

Instead of the commission split, you can describe your own calculator, form or checklist. Paste a line like this one (sample numbers):

Use atlas.factory2 to build me a tip calculator (tool_type calculator; fields bill and tip_pct; examples: bill 80 at tip_pct 20 gives tip 16 and total 96; bill 0 gives an error). Give me the watch link, then keep going on your own, without waiting for me, until you have the live tool and receipt links.

Sample numbers only. Give 1 to 8 fields and 2 to 6 worked examples. You still press Confirm once on the watch link; your AI does the rest.

What happens, step by step

  1. Spec first. Atlas writes the spec and acceptance checks from your problem. For a commission split it uses its template, for example (sample numbers): a sale price of 400,000 at 3%, split 60 / 40, must give 12,000 gross, 7,200 and 4,800. Shares that don't add up to 100 must give an error.
  2. You press Confirm. On the watch page you confirm that the spec says what you need. That is the only thing you do. Your AI is waiting for it and carries on by itself the moment you press it. A submission before that is refused.
  3. Your AI builds one page. One self-contained HTML file with inline code, at most 60,000 bytes, following a short contract: a function atlasCompute(input), one input per field, a button atlas-run and an output area atlas-output.
  4. Atlas runs it in the locked box. A pinned JavaScript engine with no network, no files, and time and memory caps. Atlas checks nine rules: size, one self-contained page, no network calls, no data collection or storage, no hidden behavior, runs in the box, the contract, the acceptance checks, and that the screen works.
  5. APPROVED or REFUSED, with reasons. Every rule gets a pass or a reason. A refused page can be fixed and resubmitted. Every try and decision goes on a hash-chained docket.
  6. Released from the exact bytes. An approved page goes live at once at its own link, with a policy that blocks network calls. The receipt ties the spec, your confirmation, the bytes, the decision and the release together, and anyone can re-check it.