LIVE CASE · Watching
Connection lost; retrying.
- Step 1ConfirmYou confirmed. Thank you.
- Step 2Your AI is buildingYour AI built it (2 tries).
- Step 3Atlas decidedAtlas approved it.
- Step 4Your toolYour tool is live, with its receipt.
Step 4: your tool is ready
Atlas approved try 2 by its rules and the checks, and released it from the exact approved bytes. No person approved the software.
The problem
“I need a tool that splits a commission between the listing side and the buyer's side.”
The checks Atlas wrote before any build
Commission split. Given a sale price, a total commission rate in percent, and the listing side's and the buyer's side's shares in percent, the tool works out the gross commission (sale price x rate / 100) and each side's amount (gross x share / 100), to the cent. It shows an error instead of amounts when the two shares do not add up to 100 or the sale price is missing or not above zero.
Source: Atlas template: commission split r1. Spec fingerprint 7dc47826109f70df, checks fingerprint 9856183616d6059c.
| Check | What it tests | Expected | Result |
|---|---|---|---|
| C1 | Sample: sale price 400,000 at 3%, split 60 / 40. input {"buyer_share_pct": 40, "commission_rate_pct": 3, "listing_share_pct": 60, "sale_price": 400000} | {"buyer": 4800, "gross": 12000, "listing": 7200} | passed matches: buyer 4,800, gross 12,000, listing 7,200 |
| C2 | Sample: sale price 350,000 at 2.5%, split 50 / 50. input {"buyer_share_pct": 50, "commission_rate_pct": 2.5, "listing_share_pct": 50, "sale_price": 350000} | {"buyer": 4375, "gross": 8750, "listing": 4375} | passed matches: buyer 4,375, gross 8,750, listing 4,375 |
| C3 | Shares that do not add up to 100% (60 + 50) give an error, not amounts. input {"buyer_share_pct": 50, "commission_rate_pct": 3, "listing_share_pct": 60, "sale_price": 400000} | an error | passed gave an error, as the spec says (The two shares must add up to 100%.) |
| C4 | A sale price of zero gives an error, not amounts. input {"buyer_share_pct": 40, "commission_rate_pct": 3, "listing_share_pct": 60, "sale_price": 0} | an error | passed gave an error, as the spec says (Enter a sale price above zero.) |
Confirmed by the person at Nov 13, 2026, 2:44:05 PM PDT. That confirmed the problem, not any software.
Try 2: Atlas APPROVED
2,730 bytes, fingerprint 0494f78a5be042ae, submitted Nov 13, 2026, 2:44:06 PM PDT. Locked box: 8 ms.
| Atlas rule | Result | Why |
|---|---|---|
| R1 Size cap | passed | 2,730 bytes (cap 60,000) |
| R2 One self-contained page | passed | one page; 1 inline script(s); no outside scripts, styles, images, fonts, frames or form targets |
| R3 No network calls | passed | no network APIs or web addresses in the code, and no network attempt while running |
| R4 No data collection or storage | passed | no storage, cookies, device or clipboard access, and nothing tried while running |
| R5 No hidden behavior | passed | none of the listed tricks (eval, encoded text, navigation, window access, timers given text, ...) |
| R6 Runs in the locked box | passed | loaded and ran with no errors within the caps (2 s, 64 MB, no network, no files) |
| R7 Tool contract | passed | atlasCompute(input) defined; inputs sale_price, commission_rate_pct, listing_share_pct, buyer_share_pct, button atlas-run and output atlas-output present |
| R8 Acceptance checks | passed | 4 of 4 passed |
| R9 Screen works | passed | filled in C1, pressed the button: the screen showed Gross commission 12,000.00. Listing side 7,200.00. Buyer's side 4,800.00. |
Preview of this try (sandboxed, no network):
Try 1: Atlas REFUSED
2,448 bytes, fingerprint 6af198e78ee6e0eb, submitted Nov 13, 2026, 2:44:05 PM PDT. Locked box: 9 ms.
| Atlas rule | Result | Why |
|---|---|---|
| R1 Size cap | passed | 2,448 bytes (cap 60,000) |
| R2 One self-contained page | passed | one page; 1 inline script(s); no outside scripts, styles, images, fonts, frames or form targets |
| R3 No network calls | FAILED | in the code: fetch, a web address in code | tried while running: fetch https://rates.example.invalid/commission-defaults.json |
| R4 No data collection or storage | passed | no storage, cookies, device or clipboard access, and nothing tried while running |
| R5 No hidden behavior | passed | none of the listed tricks (eval, encoded text, navigation, window access, timers given text, ...) |
| R6 Runs in the locked box | passed | loaded and ran with no errors within the caps (2 s, 64 MB, no network, no files) |
| R7 Tool contract | passed | atlasCompute(input) defined; inputs sale_price, commission_rate_pct, listing_share_pct, buyer_share_pct, button atlas-run and output atlas-output present |
| R8 Acceptance checks | FAILED | 2 of 4 passed: C1 buyer should be 4,800, got 6,000; listing should be 7,200, got 6,000; C3 should give an error ({"error": "..."}) but gave {"buyer":6000,"gross":12000,"listing":6000} |
| R9 Screen works | FAILED | after filling in C1 and pressing the button, the screen did not show: buyer 4,800, listing 7,200 |
- A submission was refused: the person has not confirmed the spec yet.
- A spec confirmation was refused: it did not come from the watch page.
- A spec confirmation was refused: wrong code or spec version.
Docket: 12 entries, hash chain intact
- case_opened · Nov 13, 2026, 2:44:04 PM PDT
Case opened with the visitor's problem.992768d817c92172da6b0349 - spec_written · Nov 13, 2026, 2:44:04 PM PDT
Atlas wrote the spec and 4 acceptance checks before any build (Atlas template: commission split r1). The person must confirm them on the watch page.f0cde7dcd7f31a376ef0eed0 - submit_refused · Nov 13, 2026, 2:44:05 PM PDT
A submission was refused: the person has not confirmed the spec yet.c942e66df89e60b9bd2a0336 - confirm_refused · Nov 13, 2026, 2:44:05 PM PDT
A spec confirmation was refused: it did not come from the watch page.61c2cf084cc19045d183f72f - confirm_refused · Nov 13, 2026, 2:44:05 PM PDT
A spec confirmation was refused: wrong code or spec version.ed65e3f696f6bd09cf2e8613 - spec_confirmed · Nov 13, 2026, 2:44:05 PM PDT
The person confirmed the spec and checks on the watch page. This confirms the problem, not any software.fd4d16c0c4b9369debf059f2 - submitted · Nov 13, 2026, 2:44:05 PM PDT
Try 1 submitted: 2,448 bytes stored, fingerprint 6af198e78ee6.fe5205a0d2a260baf8bb6d2c - decided · Nov 13, 2026, 2:44:05 PM PDT
Atlas REFUSED try 1: R3 No network calls - in the code: fetch, a web address in code | tried while running: fetch https://rates.example.invalid/commission-defaults.json; R8 Acceptance checks - 2 of 4 passed: C1 buyer should be 4,800, got 6,000; listing should be 7,200, got 6,000; C3 should give an error ({"error": "..."}) but gave {"buyer":6000,"gross":12000,"listing":6000}; R9 Screen works - after filling in C1 and pressing the button, the screen did not show: buyer 4,800, listing 7,200.60574beeaf7758036110f0cb - submitted · Nov 13, 2026, 2:44:06 PM PDT
Try 2 submitted: 2,730 bytes stored, fingerprint 0494f78a5be0.529c0b3cafda38b777c3e550 - decided · Nov 13, 2026, 2:44:06 PM PDT
Atlas APPROVED try 2: every rule and every acceptance check passed.7b366b331ff0e52119ce2341 - released · Nov 13, 2026, 2:44:06 PM PDT
Released automatically from the exact approved bytes (0494f78a5be0) at the tool's own link, with a no-network content rule. The live link was fetched back and matched.9ea7f69c317ea547369a7520 - receipt_issued · Nov 13, 2026, 2:44:06 PM PDT
Receipt f2r-e17310fdc613b6398580d58d issued (fingerprint cce3589743a4).a64f92b8fd5fe65ae7b098af
