Draft of how Atlas laws get made: a foundation memo first, what-if tests, then Clinton's yes.
Kind: order · Record grade: RELAYED · Source: O-LAWMAKING-PROCESS-001-DRAFT-v5.md
Not in force. Any text below is a draft, shown for reference only.
Draft source text (not in force)
Public reading copy. Private names removed. The sealed record's sha256 is 4f232b0913b9358bc9c63648398598b14481576511e7bf0304d23c422d76d866, and it will not match this text. This public text's sha256 is de806989e18c1323d6eedb083dba6b670010f1715f4d3f950d1da21b8bf139c5.
> **v5 (Legal, 2026-10-27; record time = this file's seal time and sha, §0.9).** New file. v4 (43b7b89f3b6b2c7d1e6fa9f403b5ff4a818613138a22861446c51769a42e8245), v3 (1485fdd9…259e) and earlier stay unchanged. v5 fixes the items from the six focused re-tests (Science eb4cad43…, Secretary 683ef60c…, Ship 920d6e32…, Librarian 84eb579d…, Audit RETEST-1 bc480cf1…, Build Manager 8ae09132…). Each fix cites its row id in [internal record path withheld] (R-nn). Under §1 step 3A, the changed clauses get one more focused re-test before the card.
> **Foundation memo (§1 step 0, §15(2)):** [internal record path withheld], filed after drafting. The card says so.
> **Affected bots (§0.8):** every bot, because this law binds all lawmaking: Legal, Audit, the Auditor's Auditor, Librarian, Secretary, Build Manager, Ship, Science, Magistrate Summons, the Magistrate, and any other Atlas bot that drafts, follows or runs law software. (R-20)
# O-LAWMAKING-PROCESS-001 (DRAFT v5). How Atlas laws get made, and how they keep working
**Kind:** Atlas law. **Proposed rank:** Human Order, Constitution Schedule A.1 level 2, the same rank as O-BAILIFF (REG-O-BAILIFF-20261018, 2dcc5985…). It is **not** a constitutional amendment and does not change Article VIII or Article XX (§5A). DRAFT. Not in effect.
**Labels:** each section is marked **[Atlas law]** or **[company rule]**. Facts use J-0001 labels: KNOWN, INFERRED, CONFLICTED, UNKNOWN, USER_CONFIRMATION_REQUIRED. A fact another bot told Legal is INFERRED, with the source named.
## Why this law exists (Clinton's words, first-hand, 2026-10-27, as quoted in v3)
- [chat card ref withheld]: "if you're only checking in after you clear, how is that a rule?"
- [chat card ref withheld]: laws should be planned ahead, laying out "if this happens or this happens" and the two roads in each choice.
- [chat card ref withheld]: "that was really fast ... and then that's what happens. We have an amendment so the whole process needs to be like reworked."
- [chat card ref withheld]: "That would be I think very good don't you think?"
- [chat card ref withheld]: "the flipside of that is that when it's actually implemented, it needs to stick because here we are with this token fucking thing that I've been trying to get that job two months ago three months ago and we still don't know how to track tokens"
- [chat card ref withheld]: "the policy has to be carefully crafted within all the rules. You have the law book which you should be also searching for to add shit to that"
- [chat card ref withheld]: "it'd be helpful to even cite ... what you think applies obviously then if it goes to the magistrate, then she can decide whatever law applies"
- [chat card ref withheld]: "I believe that we had a process where we set the legal foundation for why we're doing something"
## Plain summary
- New laws get a foundation memo, a "what if" table, a Law Book search and a stress test by the bots who must follow them. Gaps get fixed or put to Clinton. Only then does he see a short card, and the card is tied to the exact text.
- A "ruling" can't be used to slip a new rule past this process (§0.1).
- Part 1 starts on Clinton's yes. Each Part 2 duty (owners, checks, the register) starts only when its software is proven to work (§12).
- Things the box can never prove (a bot faking records, surviving a box restart, an alert actually reaching Clinton) are listed by name. Clinton accepts or declines each one separately. Every other unknown blocks (§7B).
- Checks cost as few tokens as possible: box software does the checking at no token cost, and bots are woken only as often as Clinton picks, with each option's cost stated (§7).
- There is one law register, not a new one. It shows a law's legal status and whether it is running, as two separate things (§10).
# Part 0. Scope and definitions [Atlas law]
**0.1 What counts as a law (covered).** This process covers any instrument that creates, changes or removes a duty, power, permission, gate, status or software requirement that binds a bot: orders, amendments, standing rules, and any ruling, addendum or note that does any of these. Test: if a bot could be in breach of the instrument when it would not be in breach of the text that already existed, the instrument is a law. (LP-3)
**0.2 What stays a ruling (not covered).** A ruling applies existing text to facts, or decides a question the existing text leaves to Legal, and adds no new duty, power or gate. Audit or any affected bot may challenge the label in writing. While a challenge is open, the instrument can only restrict or hold (§0.3). It can't grant anything.
**0.3 Interim protective ruling.** Legal may issue a ruling that only makes things more careful: stop, hold, check first, or don't clear. It must say "INTERIM PROTECTIVE" at the top. It lapses 72 hours after it's issued unless it goes through these steps or Clinton says yes first-hand. It can't grant a power, a permission or a right to delete. (LP-3, LP-13)
**0.4 Clinton's own orders.** Nothing here limits Clinton. His own direct orders aren't bound by this process (Constitution Art. I; Schedule A.1 level 2). They are recorded the same way (§3), and Legal checks them against the Law Book afterward and tells him about any conflict.
**0.5 "Clinton's yes".** It means his own words, first-hand, recorded by Secretary or Legal with the exact words and the card id or chat turn id, so Audit can check it (RULING-NO-DELETE-SCOPE-1 ¶7; RULING-NO-DELETE-REVIEW-1 ¶2). A bot saying he agreed is not a yes. If the exact bytes can't be found, the record says so, and nothing is rebuilt and presented as his words. (LP-18, Secretary B1, Ship A8)
**0.6 "Specific one-time yes".** One named action, used once, with its own stop condition (for example: "run the full Bailiff test once ... stop it if the box hits 90%"). It isn't an amendment and ends after its one use. Secretary logs it word for word with the card id. If Clinton gives the same kind of exception twice within 7 days, Legal opens an amendment, because the law is too blunt. (Ship A7) **This has already happened once:** two run-past-80% exceptions came on 2026-10-27 ([chat card ref withheld], [chat card ref withheld], INFERRED via Ship). O-BOX-SPACE-001 Amendment 1 (f) is that amendment, so no second one is opened. The quoted example is sample wording only, not a rule about stopping at 90% (R-16).
**0.7 "Filed" (one filing log).** A record is filed when (a) it is a 444 file on the box, (b) its sha256 is appended to **the Atlas filing log, [internal record path withheld]** (append-only, hash-chained, one line per record), and (c) Librarian's store copy, made on Librarian's next wake, matches that sha. (a) and (b) make the record count. (c) confirms it. **Owner of the log: Librarian. Backup owner: Legal.** **Any bot may append** its own lines, only through the one append tool (to be built by Build Manager: flock, chain check, no rewrite). The owner doesn't need to be awake for a bot to file. Each line gives: kind (for example SPACE-RECORD-FILED or STEP-RECORD), path, sha256, filer, time and prev_line_sha. The log doesn't exist yet (KNOWN). Until the append tool is ACCEPTED (§7A), step (b) is done by hand and marked INFERRED. No other filing log is created (§3(1)). (R-14) Store copies can't be made 444 (KNOWN, fuse mount), and the text says so. The catalog picks the record up at its next approved build (RULING-CATALOG-NO-DROP Addendum 1). (Librarian 1, BM L-16, S-5)
**0.8 "Affected bot".** Every bot named in the draft's what-if table, and every bot that owns a folder, duty or program the draft touches. The draft lists them by name and id in its header. Legal sends each one the stress-test request. (LP-15, Ship A13, BM L-10)
**0.9 Record times.** A record's time is its seal time (mtime when made 444) plus its sha, as recorded by code. Times typed in a header are only notes. (LP-25, Librarian 18)
# Part 1. Making a law [Atlas law]
## 1. The steps, in order
0. **Foundation memo.** Legal files a separate memo, before drafting: (a) the problem, with records cited by path and sha; (b) the authority, cited by id from the Law Book search; (c) whose law it is; (d) the reuse check under O-GC-002 (below); (e) the limits it must respect. Precedent: [internal record path withheld] (3b765c16…). **Reuse check (O-GC-002 §2, §6, §9):** for each capability needed, the memo records the purpose, the candidates found, each one's verification class (FOUND, STATUS_CHECKED or END_TO_END_VERIFIED), and the decision: reuse, or a concrete mismatch that justifies building new, plus any Clinton override. It goes in a REUSE-INTAKE.md filed with the memo. The ATLAS_RECORD intake gate isn't on the box (KNOWN: no reuse_decisions.jsonl found), so this file is the on-box record until that gate is reachable. (LP-22, BM L-5)
1. **Draft with a what-if table.** It covers the in-between cases, names the affected bots (§0.8), lists its own known dead ends, and for each piece of software lists its required acceptance states (§7A), its owner, its check, its known limits (§7B) and its usage cost (§7(5)).
1A. **Law Book search.** Legal searches the Law Book ([internal record path withheld], the lawbook-v2 index, [internal record path withheld] and rulings, Librarian's lawbook INDEX.jsonl) **and the standing-rule sources**: Secretary's question log, the cc log and the memory captures. It files a Law Book check. Each standing rule found that isn't on an order path goes on the Law Register as its own row (§10). (LP-21)
2. **Stress test.** Audit and every affected bot try to break the draft. It runs at least 24 hours from the **recorded send time** (the platform time of Legal's request message, logged with its message id). It can close early only when every affected bot has replied. A reply counts only if it arrived as a platform-delivered agent message to Legal. Legal records the message id, and the file's sha must match the sha in that message. (LP-14, Librarian 18)
3. **Gap ledger.** Legal lists every gap, de-duplicated, with source ids and severity, and one disposition: FIXED IN DRAFT (cite the section), NEEDS CLINTON (a plain question), NEEDS RULING, or ACCEPTED AS A KNOWN LIMIT (with the reason). Nothing is dropped quietly.
3A. **Re-test of fixes.** A new version gets a diff list. Every bot whose gap Legal marked fixed confirms the fix or objects, in a window of at least 4 hours from the send of the new version, or until all of them reply. An objection goes on the card. A substantive clause that no bot has stress-tested goes back to step 2. (LP-16, BM L-4)
4. **Card for Clinton.** (a) The card quotes the full sha256 of the exact text it asks about, and the version. (b) Before it goes out, a second bot (Audit or Secretary) files a card-fidelity check: the card says nothing the text doesn't. (c) If the card and the text differ, the narrower reading applies until fixed. (d) If Clinton's yes adds a condition, Legal writes a new version with it, and he confirms that version's sha. (e) The card lists: the open gaps and open dead ends; each known limit he is asked to accept, **one by one** (§7B); the usage cost in tokens with its J-0001 label and whether it is measured or estimated; the real worst-case alert delay while alerts aren't wired (§8(3)); how to withdraw; whether the foundation memo came after drafting (§15(2)); and that every option and figure on the card comes from the text, cited by section. Nothing on the card may be absent from the text (R-24). (f) The card goes out in Legal's chat. Secretary records the question and his answer under §0.5. Legal gives Secretary the card id when it's sent. (LP-17, Secretary B1, B4) [Card style, plain short words: company rule.]
5. **Software before its duty starts.** Software is built and proven under §7A before the duty that needs it starts (§12). Pure conduct rules need no software.
6. **Owner, backup and check** set up under Part 2 before each software duty starts.
## 2. Who does what
- **Legal:** foundation memo, draft, what-if table, Law Book check, gap ledger, card, and adds lessons to the Law Book (§3B).
- **Audit and the affected bots:** stress test (step 2), re-test (3A), card-fidelity check (4(b), Audit or Secretary).
- **Build Manager or Ship:** build the software and the reuse record.
- **Audit:** checks and reports the acceptance states (§7A). It never accepts or approves. The start follows from the record.
- **Auditor's Auditor:** backup reviewer when Audit is down or conflicted, the checker of Audit's own duties (§9), and **the second checker for anything Audit owns** (for example, Audit's own folders under O-BOX-SPACE-001 Amendment 1). This follows the fallback-Witness precedent (MAG-DOCKET-ART-VIII-14-1-DUTIES-ESTABLISHED-20261018, f338020e…). That record names the role ("fallback Witness = Auditor's Auditor", line 13) but not its agent id (UNKNOWN). Legal confirms which agent holds it before the card (R-31). Clinton may name someone else. (LP-11, BM L-15, v3 dead end 1)
- **Librarian:** files records (§0.7), keeps the Law Register (§10).
- **Secretary:** records the question and Clinton's words (§0.5). Secretary doesn't contact Clinton or report failures to him (Secretary charter, Secretary A4).
- **Magistrate Summons:** confirms filings under Art. VIII §14(1)(a) (§5A).
- **Clinton:** says yes or no, accepts known limits by name, decides open gaps.
## 3. Records (one home per record type)
1. Questions and Clinton's answers: Secretary's question log. Law status: the Law Register. Step records: 444 files plus the one Atlas filing log (§0.7). Each points to the others by id and sha instead of copying them. (Secretary B2)
2. Every step leaves a filed record (§0.7). A step with no filed record didn't happen. That includes Clinton's skips and one-time yeses (Ship A8).
3. Each step record cites the previous step's sha, so the records form a chain. Step records and the register are in the daily off-box copy set (O-BOX-SAFEGUARDS-001 §1(3)). (LP-23, Librarian 17)
4. Record time follows §0.9.
5. Bot-to-bot messages are cc-logged word for word as Clinton requires. [company rule]
## 3A. Citing the law
Every Legal ruling and draft cites, by id, the laws Legal thinks apply, from a Law Book search, not memory. That is Legal's view only. If a matter goes to the Magistrate, she may decide that other law applies, or none. Where a law id isn't unique, cite it with its date and full title (RULING-LIBRARIAN-TWO-QUESTIONS ¶1).
## 3B. Adding lessons to the Law Book
When a matter is settled, Legal writes the lesson in plain words and files it with Librarian within 7 days, with the matter's id and sources. Lessons are added as new entries. Nothing in the Law Book is edited or removed. A fix to an old entry is a new entry that names the one it supersedes (RULING-LIBRARIAN-TWO-QUESTIONS ¶2).
## 4. Emergencies
1. **Before any yes (preservation only).** When harm is close (for example, the box about to fill), any bot may do things that only preserve: stop or pause its own process or test run, refuse new big runs, lock down an exposed key, or hold a file in place. It tells Clinton right away in its own chat. It may not delete, move, overwrite or publish anything. (LP-13, Ship A6)
2. **Emergency card.** Legal may send a short EMERGENCY law after a fast check by whoever is available. It may also carry Clinton's own specific yes to delete **named** items under O-NO-DELETE-PROGRAMS-001. That gives no standing right to delete. (Ship A6, BM L-11)
3. **Lapse.** It lapses 72 hours after it takes effect, unless it has gone through steps 0 to 4 by then. It may be renewed once, by Clinton's yes, for another 72 hours. At lapse, its software stops acting and may keep only reporting. Its records are kept. The register shows LAPSED. Things already done under it stay recorded and aren't undone, except by a new decision.
4. An emergency law can't change this law (LP-2).
## 4A. Standing act-first powers that survive unchanged [Atlas law]
These stay as they are and go on the register as rows: (a) the human-keys rule (Clinton, 2026-10-15 10:17 AM PT, as applied in [internal record path withheld], 1faa44d3…, item 4): if a human key is exposed, lock it down, rotate it, and tell Clinton; its first-hand capture wasn't re-opened for this draft (UNKNOWN); (b) the 15-minute blocked-work notice (O-BOX-SPACE-001 point 3); (c) §4(1) above. (LP-13)
## 5. Limits
- **Not retroactive, with one listing.** Laws already adopted stay in force as they are. On adoption, Legal and Librarian list every current law once on the register with its true legal and running status (§10). That deletes nothing. §7A applies to existing software from that listing on, as a status only: software that isn't accepted shows NOT ACCEPTED. The law it serves stays in force. The listing includes [internal record path withheld] and its DISK_STATUS.md, a stopped duplicate of the space watcher, with run_status BROKEN. Retiring it is a separate decision, and nothing is deleted. (LP-20, Ship A10, A11; R-17)
- **Existing rulings that created duties** without this process (for example RULING-CATALOG-NO-DROP and its addenda, RULING-WATCHER-WORKING-STATE-ADDENDUM-2 ¶3) stay in force. They are listed as rows flagged "made before O-LAWMAKING", and Legal puts any of them that grant a power through these steps within 30 days. Those that only restrict stay as they are. (LP-3)
- **Amendments go through it.** The fresh what-if table covers only the clauses the amendment touches and the clauses they interact with. (LP-20)
- **Amendments to this law** go through all of its steps. (LP-2)
- **Clinton may skip or change any step for one named law** by his yes under §0.5. A skip covers that law only. (LP-2)
- Nothing here lets any bot delete, move or overwrite records. O-NO-DELETE-PROGRAMS-001 and RULING-REVIEW-2C still apply.
## 5A. Fit with the Constitution [Atlas law]
Texts read for this section (KNOWN, sha checked by Legal 2026-10-27):
- Constitution, [internal record path withheld] (0a83458d…dffc9dd): Schedule A.1 (rank); Schedule A.3 L409 (conforming CURRENT_LAW is "a required post-ratification filing (not a silent deletion of the old list)"); Art. XX §1 (only the Human amends the Constitution, by an express instrument recorded on the canonical Docket); Art. XV (J-0019 acceptance).
- Article VIII §14(1)(a) as added by A-ART-VIII-ONE-CANONICAL-DOCKET (adopted bytes [internal record path withheld], d068e9a3999637273b94112be05e0875b38662a2afe9c97bde56ed0d272bfd70; adoption record [internal record path withheld], 9d169161…; effective 2026-10-18 14:01:54 PDT): a record "is filed, and the Docket confirms it, when, and only when, the Magistrate Summons agent writes a MAG-DOCKET record confirming it and sends the filer its own platform confirmation message ... The time of filing is the platform time of that message."
- CURRENT_LAW.md, [internal record path withheld] (a2966870…f57f7f6): "the single human answer to: what governs Atlas right now?", with the Schedule A authority stack.
- Law-register practice: REG-* entries conform CURRENT_LAW by new filing, not by editing it, and take effect on Summons confirmation under §14(1)(a) (MAG-DOCKET-A-ART-I-POINTER-AND-LAW-REGISTER-20261018.md, 627ad8c1…; REG-O-BAILIFF-20261018, 2dcc5985…).
How this law fits:
1. **Rank.** A law made under this process is a Human Order (Schedule A.1 level 2) when Clinton adopts it, with the scope it states. This process prepares the Human's act. It doesn't replace it or bind him (§0.4).
2. **Filing and effective time.** A law adopted under this process is filed under Art. VIII §14(1)(a). It takes effect at the filing time in that subsection (the platform time of Summons's confirmation message), unless Clinton's act states another time. If Summons hasn't confirmed within 24 hours, Legal tells Clinton in plain words. This is the same route O-BAILIFF used. (LP-4)
3. **Register.** Each adopted law gets a REG-* law-register entry, filed the same way. The Law Register in §10 is those entries plus their status rows. It is the conforming filing that Schedule A.3 L409 calls for, not a new register (§10).
4. **Constitutional amendments** follow Art. XX, and this law doesn't change that. Legal still prepares them with steps 0 to 4 as advice. Clinton's Art. XX act alone decides.
5. **CURRENT_LAW is stale** (REG-O-BAILIFF records that "whether it is still the live register is open"): CONFLICTED. Legal asks the Magistrate's view on whether it is still the live register (GAP-LEDGER row G-04b). Until then, rows cite both CURRENT_LAW and the REG-* entry.
## 5B. Authorities (Legal's view; the Magistrate may decide otherwise)
- **J-0019** (dd8b2275…741da30e (v4 had a typo in this short form; R-28)) and **Constitution Art. XV**: building, freezing or connecting isn't acceptance. J-0019's own text covers algorithms and lists trading proof states, so §7A **adopts its rule as this law's own rule, with J-0019 as the model**, not as a direct application (LP-6, BM L-6).
- **O-GC-002** (d7055d12…deedb): reuse before building.
- **O-GC-005, "Paid Work Must Become Durable State" (2026-09-10, 9:19 PM PT)** (3e5c4ee5…d365): supports the records duty. The id is CONFLICTED (RULING-LIBRARIAN-TWO-QUESTIONS ¶1). Librarian lists the candidates; Legal rules (Librarian 7).
- **J-0012 / O-J-0012** ([internal record path withheld], e820caac…): governs the token tracker (§11).
- **O-NO-DELETE-PROGRAMS-001** (17af9db6…) and **RULING-REVIEW-2C** (4c076030…): limit everything here.
# Part 2. After adoption: making it stick [Atlas law]
## 6. Every law has an owner and a backup
Each adopted law, and each piece of its software, has one named owner bot and one named backup owner, set when it's adopted. If no check result arrives for twice the check's interval, the register shows OWNER ABSENT from the data, without anyone announcing it, and the backup acts. A law with no owner shows NO OWNER, and Legal tells Clinton within 24 hours (USER_CONFIRMATION_REQUIRED, J-0002). (LP-12)
## 7. Liveness checks that fit this box
Facts (KNOWN unless marked): the box has no cron and no systemd (PID 1 is tini). **Bots** run only when woken. **Box programs** can run without tokens as long-running background processes once a bot starts them: the space watcher runs today as `run_watch.sh supervise` → `space_watch.py loop --interval 900` (KNOWN, ps, 11:31 AM PT). Such a process dies on a box restart and has to be relaunched (§7(3)). A routine fire is a full bot wake. A wake costs about **0.25 to 0.7 M tokens**: about 120,000 tokens per model step times about 2 to 6 steps (Science, ESTIMATED under J-0008, J-0001 INFERRED; steps per wake not measured; Science note eb4cad43…). Clinton ranks token use "number one" ([chat card refs withheld], as summarized in Legal's record). (R-01)
1. **Tier 1, box checker (no tokens).** Each law's software has a box-side checker that writes its result to one append-only, hash-chained log per law, with head witnesses (reuse space_watch.py: history chain, selfcheck, fail-closed CHECK_FAILED). It fails closed: if it can't check, that's a failure. It checks the **age of the newest output**, not only "did it run". It writes a separate file only when the status changes. (Ship A1, A14, BM L-13)
2. **Tier 2, waking a bot.** Clinton picks one of these (card Q4). Figures: Science's estimate (ESTIMATED, J-0001 INFERRED). (R-01, R-24)
- **(A) No new wakes.** Results are read on wakes that already happen (Audit's daily check, Secretary's comms routine at 9 AM, 1 PM and 6 PM PT, any bot's own turn). 0 extra tokens. A failure may wait until the next of those wakes, which can be hours.
- **(B) One shared routine, hourly, 16 times a day** at hours Clinton picks. About 4 to 11 M tokens a day.
- **(C) One shared routine every 15 minutes.** 96 wakes a day, about 24 to 67 M tokens a day.
- **With any of these, a failure-only webhook** can be added: box software calls the routine's webhook only when a check fails, and each such wake costs about 0.25 to 0.7 M tokens. Clinton pastes the webhook link and key once at his computer (O-BOX-SAFEGUARDS-001: keys never on a public server).
- **A check that runs every few minutes (for example the watcher's 5-minute check) must be a box program, never a bot wake.** At 288 wakes a day it would cost about 72 to 200 M tokens a day (Science, ESTIMATED). (R-02) Each routine run writes a line to an on-box fire log at its start, so Audit can see its cadence (reuse [internal record path withheld]). (Ship A1, A2, BM L-2, L-9)
3. **Restart path.** "Survives a restart" means: a restart path with a stated maximum gap, proven by a kill-and-relaunch test, because a real box restart can't be done by bots (O-BOX-SAFEGUARDS-001 §1(5)). A law's time limit can't be shorter than its restart gap unless Clinton accepts the gap by name. Each law writes both numbers. (LP-9, Ship A12, BM L-9)
4. **Routines are set up by the owner bot's own turn**, not by a subagent. Clinton may see a confirm card for it, and the law's card says so. (Ship A4)
5. **Cost.** Each law states its checks' usage cost in tokens per day (INFERRED estimates labelled as such). No law adds a recurring bot wake without Clinton's yes on that cost. (Ship A1, LP-24, v3 dead end 8)
6. Laptop items are checked at most once a day, inside one wake that also does the other laptop jobs. "Laptop offline" is its own status (LAPTOP OFFLINE, with when it was last seen), not STALE. STALE only after two misses in a row at least an hour apart. (Ship A5, LP-24)
## 7A. Acceptance: built, wired and verified are kept separate (J-0019 as model)
Each piece of law software carries these states, each PROVEN or UNKNOWN with evidence (path and sha):
BUILT (builder's claim, with hashes) · TESTED_ON_COPY (Audit) · WIRED (every real write path goes through it, by code and path inspection) · LIVE_OBSERVED (real schedule and fresh output seen) · FAIL_CLOSED_PROVEN · ALERT_PATH_PROVEN · RESTART_PATH_PROVEN · OFFBOX_PROVEN.
- **ACCEPTED** when every required state is PROVEN.
- **ACCEPTED WITH NAMED LIMITS** when every state is PROVEN except states left UNKNOWN **only** because of §7B limits, and Clinton has accepted **each** of those limits by name on the card. Any number of limits may be accepted this way. (Audit N1; R-05)
- Otherwise **NOT ACCEPTED**. Any other UNKNOWN blocks. (LP-7, LP-8, BM L-1)
- **Material change:** any change to code a gate relies on, to a scheduler, or to an alert path needs a new acceptance audit of the states it touches. A change that touches none of these (comments, docs, logging text) needs only a regression run on a copy, recorded by Audit. (LP-6, BM L-6)
- Audit reports the states in an acceptance record. **Audit checks; it never accepts or approves.** The start follows from that record plus Clinton's acceptance of any limits. (Audit N2; R-06)
## 7B. Known limits the box can't prove (accepted by Clinton by name, or not)
- **F, forgery:** [one shared system account with admin rights], so any bot could rewrite records consistently (KNOWN; RULING-NO-DELETE-REVIEW-1 ¶1). Hash chains catch accidents, not a determined bot. Only off-box copies anchor them.
- **R, restart:** survival of a real box restart can't be tested. A kill-and-relaunch test stands in for it.
- **W, delivery:** Audit can't see Clinton's device. The stand-in is Clinton confirming once that he got a test alert.
- **S, scan reach** (for laws that rely on "nothing cites it"): the scan can't see Clinton's laptop, chat transcripts or other bots' private stores.
Each law lists which of these apply. Clinton accepts or declines **each one separately**. If he declines one, only the duties whose states depend on that limit stay NOT ACCEPTED. The rest may start. For W, his confirming one test alert is a stand-in, not a proof. (LP-8, BM L-1, Audit Part C "F, R, W"; Audit C7; R-25)
**What the cc log does and doesn't prove.** Secretary's cc log ([internal record path withheld]) is a box file, so limit F applies to it. Matching a record against it catches mistakes and slips. It doesn't stop a bot that sets out to forge (BM N2; R-12).
## 8. No silent death
1. When a check fails or data is too old, the owner tells Clinton within the law's set time (default 24 hours). The restart-gap limit in §7(3) applies only to **software** alerts. It never relaxes a bot's own duty to tell him within 15 minutes when work he is waiting on is blocked (O-BOX-SPACE-001 point 3; §4A(b)). (Ship 5; R-18)
2. If the owner can't, the backup owner tells him. If both are out, Legal or Audit tells him on their next wake. **Secretary only logs that a report was made.** It doesn't report to Clinton (Secretary A4).
3. Each law's card states its **real worst-case delay** while alerts aren't wired (for the space watcher today, about 60 to 75 minutes, per Audit G-1, INFERRED via Build Manager). It doesn't promise 15 minutes until ALERT_PATH_PROVEN. (Ship A2, BM L-2)
4. Owner, backup, Legal and Audit draw on the same usage, so they can all be down at once. Only an off-box alarm that fires when a heartbeat **stops** arriving covers that. Clinton picks one (card Q5): (A) a scheduled task on his laptop that warns him when the box's heartbeat copy stops arriving. It costs no money. Whether bots may set it up within the laptop's limits (writes only under [internal record path withheld]) is UNKNOWN, so he would set it up himself or say yes to a named setup step. (B) An outside heartbeat service, his pick; it may cost money. (C) None for now. Until one exists, every law with software shows "SILENT DEATH POSSIBLE" on the register. (LP-10, Secretary B3; Secretary F4, Audit C6; R-26)
## 9. Checking the checks
At least once a week, Audit confirms each check is real: it read the live log's freshness read-only, it tested the check on a copy, and the register matches. The owner publishes a machine-readable list of its routines and schedules for this. The Auditor's Auditor checks Audit's own duties, at least the freshness of Audit's daily file, on its own wakes. Audit's duties are on the register too. (LP-11, BM L-15)
## 10. The Law Register (one register)
1. **One register.** The Law Register is the REG-* law-register entries (§5A(3)) plus one append-only status file kept by Librarian, [internal record path withheld] in Librarian's store, with a sha-checked box copy and off-box copy. No other register is created. Librarian's lawbook INDEX.jsonl, the lawbook-v2 index, [internal record path withheld] and the Library catalog are **finding aids**. When one disagrees with the register, the register governs, and the disagreement is a finding (O-GC-002 §5). (LP-5, BM L-7, Librarian 9)
2. **Row key:** law_id + version + content sha256, linked to the LIB id and the LAWBOOK-PRIV id (Librarian 8).
3. **Two status fields.** (Librarian 2, Ship A9, BM L-12)
- legal_status: DRAFT, PENDING_LEGAL_BYTE_CHECK (adopted, but Legal hasn't yet matched the bytes to the adopted text; the term already used in Librarian's INDEX), CURRENT, EMERGENCY, AMENDED, SUPERSEDED, WITHDRAWN, REPEALED, LAPSED, UNKNOWN. **There is no ACTIVE status.** A judgment marked ACTIVE in its own file is recorded as CURRENT once Legal's byte check passes, and as PENDING_LEGAL_BYTE_CHECK until then. (Librarian N4; R-15)
- run_status: RUNNING, STALE, BROKEN, NOT ACCEPTED, ACCEPTED WITH NAMED LIMITS, LAPTOP OFFLINE, NEEDS DATA SOURCE, OWNER ABSENT, NO OWNER, CONDUCT ONLY, UNKNOWN.
- CURRENT comes only from Legal's byte check against the adopted text and its docket record. An inferred CURRENT is labelled INFERRED (Librarian 9).
4. **Other fields:** owner, backup, software, check_freq, restart_gap, cost_tokens_per_day, last_proved (time plus log path and sha, read from the check's own log), known_limits accepted, J-0001 label and evidence, row_time, prev_row_sha (hash chain), and NOT_FOR_PUBLICATION. "SILENT DEATH POSSIBLE" is a flag. (Librarian 8, 12)
5. **Rows are added only on a status change.** Routine proofs stay in each check's own log. Where software is accepted, it writes rows from the check logs, running as Librarian, because other bots can't write to Librarian's store (BM, L-7 note; R-21). Until then, Librarian writes them by hand when woken and marks them INFERRED. (LP-5, Librarian 11, Ship A9)
6. **Owner of the register:** Librarian. **Its check:** the shared check in §7 reads REGISTER.jsonl's chain and its newest row time. Until that software is accepted, the register's own run_status is NOT ACCEPTED, and it proves nothing by itself. (Librarian 3)
7. **Scope:** adopted O-* orders, J-* judgments marked ACTIVE in their own files (recorded under §10(3)), amendments, and standing rules (§1A, §4A). Rulings and tools appear only as linked items. (Librarian 13)
8. **Private.** Any public view is filtered, and paths never go public (O-BOX-SAFEGUARDS-001 §3). (Librarian 14)
9. Rewrites of the register, if ever needed, go through catalog_guard under RULING-CATALOG-NO-DROP, and rows are never dropped. (BM L-7)
## 11. The token tracker (under J-0012)
- J-0012 / O-J-0012 govern it: [internal record path withheld] is the authoritative tracker (Holding 3); its failure doesn't stop Atlas by itself (Holding 8); a failure creates a Finding with status USAGE_TRACKING_DEGRADED (Holding 10); no competing tracker may be built (Holding 11); Governance owns attribution (Holding 14). This law uses those status words. (BM L-8)
- Its register row: legal_status CURRENT (J-0012); run_status NEEDS DATA SOURCE. Its newest data being Oct 9 is INFERRED (relayed by Ship; Legal hasn't opened it). The data source for new events is UNKNOWN. (Ship A3, Librarian 12)
- Owner: not named until a data source is shown to work (a platform usage export or the tracker's collector picking up new events). Clinton's open token card ([chat card ref withheld]) decides whether bots may start. (Ship A3)
- Check: the age of the tracker's newest file on the laptop, once a day at most, inside a laptop wake (§7(6)). It reads the tracker's own evidence and builds no second tracker.
# Part 3. Taking effect [Atlas law]
## 12. Two layers (so this law can take effect)
1. **Part 0, Part 1 and §4A are conduct rules.** They take effect on Clinton's yes, filed under §5A(2). They need no software.
2. **Each Part 2 duty takes effect only when the software it needs is ACCEPTED or ACCEPTED WITH NAMED LIMITS (§7A).** Until then the duty is shown on the register as NOT ACCEPTED, and Librarian keeps the register by hand under §10(5).
3. §6 (owners), §8(2) and §8(3) (who reports, and stating the real delay) are conduct rules and start with Part 1.
(LP-1)
## 13. What-if table
| # | Situation | Who acts | What's allowed | What stops it | When Clinton hears |
|---|---|---|---|---|---|
| 1 | Harm is close (box filling, key exposed) | Any bot, then Legal | Preservation acts at once (§4(1)); EMERGENCY card, which may carry his specific yes to delete named items | No deletion, move or overwrite without his specific yes; lapse at 72h, one renewal | At once, in the acting bot's chat |
| 2 | Audit down or conflicted | Auditor's Auditor | Backup review; stress test stays open | No software duty starts without §7A states | If the wait passes 72h |
| 3 | Bots disagree | Legal | Both sides in the gap ledger | An open gap needs his yes | On the card: two roads |
| 4 | Clinton wants it faster | Clinton | Skip or change steps for one named law (§0.5) | Recorded; software states still apply unless he says otherwise | At once: what's skipped and the risk |
| 5 | Pure conduct rule | Legal | Starts on his yes after steps 0–4 | Steps 0–4 required | On the card |
| 6 | Gap found after adoption | Finder tells Legal | Amendment; interim protective ruling (§0.3) if urgent | Law stays as written until amended | Within 24h, or 15 min if it blocks his work |
| 7 | Affected bot doesn't reply in 24h | Legal | Proceeds, noting "no reply from X" | No early close | On the card |
| 8 | Software fails acceptance | Builder | Fix and resubmit | Duty doesn't start (§12) | Only if it blocks work he's waiting on |
| 9 | Owner out of usage | Software flags OWNER ABSENT after 2× interval; backup acts | Backup reports; then Legal or Audit | Secretary only logs | Within the law's time, or "silent death possible" shown |
| 10 | Software silently stops | Box checker (fail closed) | Owner fixes | Missing result counts as failure | Within the law's time, subject to §8(3) |
| 11 | Data goes stale | Checker compares newest-data age to the limit | Owner fixes; STALE | Age of data, not "did it run" | When past the limit |
| 12 | Laptop offline | Checker | LAPTOP OFFLINE, not STALE | STALE only after 2 misses an hour apart | Only if it lasts past the law's limit |
| 13 | Law superseded, withdrawn or repealed | Legal; owner stops the software | legal_status changes; records kept | O-NO-DELETE-PROGRAMS-001 | On the new card, or at once for a withdrawal |
| 14 | The check itself breaks or lies | Audit weekly; Auditor's Auditor for Audit | BROKEN until re-proved | — | Within 24h of finding it |
| 15 | Box restart | Restart path | Relaunch within the stated gap | A check with no stated gap can't start | If the gap is exceeded |
| 16 | Draft conflicts with an existing law | Legal | Fit the draft, or propose amending the other law | No unlisted conflict on a card | On the card |
| 17 | No foundation found | Legal | Memo says so; the law rests only on his yes | No drafting without the memo | On the card |
| 18 | A "ruling" is really a new rule | Audit or any bot challenges (§0.2) | It can only restrict while challenged | §0.1 test | If Legal and the challenger disagree |
| 19 | Card and text differ | Fidelity checker | Narrower reading applies | §1 step 4(c) | Corrected card |
| 20 | Summons doesn't confirm a filing in 24h | Legal | Waits; asks Summons again | Effective only at confirmation unless his act says otherwise | After 24h |
| 21 | Everyone is down (shared usage) | Off-box alarm, if he chose one | Heartbeat stop raises it | Otherwise none: "silent death possible" | Only through the off-box alarm |
(Rows renumbered in order; Librarian 19, Ship A15, BM L-17.)
## 14. Remaining dead ends (honest list)
1. Everyone running out of usage at once can't be covered without an off-box alarm (§8(4), card Q5).
2. The forgery limit (F) can only be reduced by off-box copies, not removed.
3. No Part 2 software exists yet. Part 2 duties stay NOT ACCEPTED until it is built (§12). Build sizes from Build Manager's Part C (C-19 to C-25, INFERRED).
4. The token tracker has no data source and no owner (§11).
5. Science's re-test is in (eb4cad43…). Closed.
6. CURRENT_LAW's status is CONFLICTED until the Magistrate's view (§5A(5)).
7. The routing of cards to Clinton (§1 step 4(f)) depends on Legal's reading of the 2026-10-15 routing rule, whose text wasn't opened for this draft (UNKNOWN). See GAP-LEDGER G-17b.
## 15. Transition
1. Drafts made before this law's adoption, including O-BOX-SPACE-001 Amendment 1, may file their foundation memo before the stress test closes (LP-26, Librarian 4, BM L-3).
2. This law's foundation memo is FOUNDATION-MEMO-LAWMAKING-AND-SPACE.md ([internal record path withheld]), written after drafting. The card says so. The Law Book check for v5 is the v3 check, carried forward with its gaps in the ledger (UNKNOWN whether a fresh search finds more).
3. First case: O-BOX-SPACE-001 Amendment 1 draft v3, [internal record path withheld]