Atlas, the AtlasClose Magistrate: a fluffy dog in a blue collar with a compass tag

Atlas Law

Every Atlas law on one page. Each item is labelled Atlas law with the date Clinton adopted it, Practice (a company rule, not law), or Pending — not adopted. Three items are marked Adoption record under check: two in the October list and Row 3 of the amendment in row 2. Pending text is never shown as if it were in force.

Atlas
Frozen record: Law Docket freeze-1, 22 rows.
Freeze-1 SUMS sha256: 1233399f620fcf5d95d728f820c6cd53b3315936e070b893a7e585f56da36117
Docket sha256: 5710289dd18c7cfcffaf47bd8499152df53b507856774822a160b5b9c2a09498
Head row sha256: 589f76242020251785cad6450957fdeb2d0c805703225fefa46ab3bdcdb48840
Freeze record (FREEZE-1-RECORD.md) sha256: 71f0a31d9c5d1ff78d50f2da68e97b45d549d90a54ba6f7ad713515498642357
Freeze record addendum (FREEZE-1-RECORD-ADDENDUM-515L.md) sha256: 4ef360465479ca033e44a975924d66c870ad5481f3f7f895895e192fbff75aa2
Raw public copy: github.com/atlaslaw2026/Atlas-Public-Docket/tree/master/law/atlas-law/freeze-1

Atlas lawAdopted by Clinton and frozen in the docket at freeze-1.

Row 1A-NO-DELETE-1

Atlas law (adopted Oct 27, 2026 by Clinton)

Only a final Magistrate ruling can make the Bailiff delete a party-held copy, after a sealed Atlas copy, notice, and a 24-hour wait; overwriting or wiping counts as deleting.

Amends: O-NO-DELETE-PROGRAMS-001
Kind: amendment · Record grade: RECORDED · Source: A-NO-DELETE-1.md
Full text as adopted
Public reading copy. Private names removed. The sealed record's sha256 is 5943099e566490c342908dbaff06d5160d134b395ffa07c459d250f13417a0a8, and it will not match this text. This public text's sha256 is 9baf6b05146886053e91a1506f8c0870546ad0f23e9b31b8d76a6e68f6e3b3de.
# A-NO-DELETE-1 — ADOPTED (amends O-NO-DELETE-PROGRAMS-001, adds §1A)

Adopted by Clinton Brown first-hand in Legal's chat, 2026-10-27 4:12 PM PT, answering card [chat card ref withheld] "Adopt this law change as Atlas law?": "Yes, adopt it as written". Adopted text = A-NO-DELETE-1-DRAFT-r11.md (sha fb85c20a351f213aaa2e500e3b76aa2df979af43c73effe6f7212162e58c9364), Audit PASS FOR CARDING by diff. Feature stays OFF until Audit code verification and Clinton's first-hand go. BL-0A.4 confirmed in O-BAILIFF v9 (3ed2c6da…) line 81.

---

# DRAFT A-NO-DELETE-1: Bailiff deletion on a final enforcement ruling (NOT ADOPTED)
Drafted by Legal, Tue Oct 27 2026, about 3:55 PM PT, on Clinton's first-hand box [chat card ref withheld] in Ship's chat (3:53 PM PT, relayed by Ship): "Have Legal draft a law change so the Bailiff deletes on the Magistrate's order alone, and bring me the text to adopt". Then [chat card ref withheld] (3:54 PM PT, relayed): "well it needs to copy the file it is deleting first right?" and [chat card ref withheld]: "because he is taking the prpoerty or however that is". Then [chat card ref withheld] (3:55 PM PT, relayed): "and this is only on order of a magistrate". Choices: G1 on card [chat card ref withheld] (4:04 PM PT, relayed by Ship): "No, the company's deadlines govern". First-hand in Legal's chat: [chat card ref withheld] (4:07 PM PT): "Yes, take the stop out. Appeals are the route, and I keep my override power"; [chat card ref withheld] (4:08 PM PT): "A" (answering: only a Magistrate's order can make the Bailiff delete). Before that, [chat card ref withheld] (3:52 PM PT, relayed): "I want to make sure the bailff actually deletes the file if it is ordered".
Kind: Atlas law. It needs Clinton's first-hand adoption of these exact words. Until then, the deletion path stays behind a flag that is OFF.

## Foundation (short)
- O-NO-DELETE-PROGRAMS-001 §1 (17af9db6…): no program may delete Atlas records without the Human's yes to that specific deletion. Copies of Atlas records held by a party are Atlas records, so a Bailiff wipe is barred today.
- O-BAILIFF v9 (3ed2c6da…) already gives the Bailiff a wipe power. BL-2.2 and BL-2.5(1): the consented Atlas connector may "retrieve and securely wipe" named records within the recorded scope. BL-3.2(c) and BL-4.6(c): take back, then wipe. BL-4.6(c): no wipe before finality under AD-11.3. BL-5(h): the Bailiff never alters or deletes a record in Atlas custody. BL-6.1 and BL-6.5: custody record, and retrieved items kept unchanged for re-delivery.
- So the two laws conflict. This amendment resolves the conflict narrowly. The Magistrate's final enforcement ruling stands in for the Human's specific yes, but only for party-held copies, and never for Atlas's own copy or any record.
- Also cited: O-BOX-SPACE-001 §5 (an earlier narrow exception, same pattern); O-BOX-SAFEGUARDS-001 §3; J-0019 (not working until verified); the identity-hold read (Oct 27).

## Text to adopt
Add to O-NO-DELETE-PROGRAMS-001:

> **§1A Bailiff deletions on a Magistrate's order.** Only a Magistrate's order can trigger a deletion under this section. No other ruling, order, request, bot, program or person can, including the Human's yes alone (see 'The Human's own yes'), and that includes Legal, Audit, Ship, any office, any managed organization's rules and any automated process. The Bailiff may delete a copy of an Atlas record without a separate yes from the Human only when all of these are true:
> (a) **The ruling.** A Magistrate is a verified Magistrate seat with provenance that fails closed. A bot, a practice court or an automated process labeled 'Magistrate' doesn't count. A Magistrate's final enforcement ruling orders the deletion. It is final under AD-11.3, in force, and sealed by a court instance Audit has validated, with its hash on the Docket. It passes a Magistrate-provenance check that fails closed. It did not come from an automated re-hearing, reconsideration or retry loop. The test: every request in the matter has a recorded requester, and no program made a re-hearing request.
> (b) **The target.** The ruling names each copy by sha256 AND exact location (system, account and path) AND holder. The copy is held by the party bound by the ruling, on a system named in that party's recorded scope on the Docket at joining. The Bailiff reaches it only through the consented channel (O-BAILIFF BL-2.5(1)) or a party account on a system named in that recorded scope. Never covered, by location and whatever the sha: any Atlas custody, docket, ruling, ledger, evidence, audit, hash, backup or Library location; the box and its workspace; the VM; and anything a bot or Atlas office uses.
> (c) **Seize first.** The Bailiff first seized the property: it made a full sealed copy held by Atlas, checked that the copy's sha256 matches the copy to be deleted, and recorded it. That sealed copy is the Atlas custody copy. It is kept read-only in the Atlas custody store, and an off-box copy is placed and its sha confirmed. The box's space and file count are checked first. It is kept unchanged, and the Bailiff never deletes it (O-BAILIFF BL-5(h), BL-6.5). The custody copy is written to a new file only and never overwrites an existing one. The private-name scrub and access limits apply to all seized data in Atlas custody: only the Bailiff, Audit and the Magistrate may read it, and nothing from it goes public until private names are scrubbed and tracked. If the seizure is incomplete, any sha doesn't match, or the off-box copy fails, the Bailiff stops and asks the Human, and nothing is deleted. No retry may write over an existing custody file (overwriting counts as deleting).
> (d) **Nothing open.** No appeal, stay, identity hold, release motion, emergency stop under O-BAILIFF BL-0A.4 (logged on the Docket with stated grounds, never opened case by case at will), re-hearing, reconsideration, remand or later hearing is open in the matter. A machine check against every open matter's citations and holds finds that no open matter relies on the copy. The warning and appeal periods under the governing law have run. In a managed organization's lane, that organization's declared periods govern, even where they are shorter than Atlas's own; every other part of this section still applies.
> (e) **Notice and wait.** The Bailiff sends notice to the Human's own chat, not just a log, naming the matter, the ruling and each target. The notice is information only. It waits 24 hours after delivery is confirmed (the Human may set a different wait, but only in his own first-hand words; a zero wait needs him to say so expressly). If delivery can't be confirmed, nothing is deleted. Neither the Human nor anyone else can stop a deletion case by case during the wait: the route to change a Magistrate decision is appeal (O-APPELLATE-DIVISION AD-11.1, AD-11.2; AD-13.1 'The Human is not an appeal tribunal'). This does not limit the Human's power to amend, supersede, strike down or override by a later Human act (AD-11.5, AD-13.2). A Human act under AD-11.5 or AD-13.2 that takes effect before the wipe halts it; the Bailiff checks for one immediately before deleting, under (g).
> (f) **Record first, off the box.** Before deleting, the Bailiff writes an append-only deletion record: the matter, the ruling and its hash, each target's sha256, size, location and holder, the custody copy's sha256, the time, and the result of every check in (a) to (e). A copy of the record, and of the custody copy under (c), is placed off the box (the VM backup or the laptop records path, never [internal record path withheld]) and its sha confirmed. If that fails, nothing is deleted.
> (g) **At delete time.** The Bailiff re-hashes the target immediately before the wipe, with no gap in which the file could be swapped. If the hash doesn't match, it doesn't delete. In the same step it checks that no Human act under AD-11.5 or AD-13.2 affecting the matter has taken effect; if one has, it doesn't delete.
> (h) **Cap.** No more than 10 copies or 1 GB per ruling. Above that, see the Human-yes choice below.
> **Never.** The Bailiff stops and asks the Human if any check fails or is unclear. It never retries a deletion on its own. No new or duplicate ruling on the same target may be generated automatically after a failure unless the Human has acted. It makes no paid calls to delete. Only the Bailiff's own entry point, holding the ruling's token, can delete under this section, enforced in software by the no-delete guard. Every bot runs as the same computer user, and that limit is declared openly.
> **Turning it on and off.** The deletion feature is turned on only by the Human's first-hand go after Audit has verified the deletion path. It turns off automatically, by a software timer Audit verifies, if Audit's verification lapses (any change to the deletion path's code after Audit's check counts as a lapse) or any 24-hour check is overdue.
> **Audit's check.** Within 24 hours of each deletion, Audit checks independently, not just from the Bailiff's own record: the target is gone, the custody copy is unchanged and its sha matches, and the scope and location were right. If Audit finds a defect, the feature turns off, the Human is told, and the item is re-delivered under BL-6.5 if needed.
> **Managed organizations.** No Atlas record may be deleted in any managed lane except under (a). A managed organization's rules may add limits but may not loosen any part of this section for Atlas records, except that its own declared warning and appeal periods govern under (d). The never-covered list and the Magistrate-only trigger must appear in its rules.
> **O-BAILIFF wipes.** Any Bailiff wipe or deletion of a copy of an Atlas record, including under O-BAILIFF BL-2.2, BL-2.5(1), BL-3.2(c) and BL-4.6(c), happens only under this section. Consent at joining is never a trigger on its own.
> **The Human's own yes.** The Human's yes alone can never trigger a Bailiff deletion. Above the cap in (h), both a Magistrate's order AND the Human's specific yes are needed. When the Bailiff stops and asks, the Human may only release it to continue under this section or, where a check in (a)–(g) has failed, cancel.
> **Until enforced in software.** Until Audit verifies the no-delete guard's ruling-token check against the Docket hash, the Magistrate-only trigger is a written rule and not yet enforced by code, and the feature stays off.
> **Other orders.** The "No deletes" limit in O-BOX-SAFEGUARDS-001 §3 covers that order's own safeguard work. It does not bar deletions under this section.
> The Human may withdraw this section at any time.

Conforming note: O-BAILIFF's wipe power (BL-2.2, BL-2.5(1), BL-3.2(c), BL-4.6(c)) is limited by §1A. Its finality bar and custody rule are unchanged.

## What-if table
| What if | Result under §1A |
|---|---|
| The ruling is appealed after the wipe is queued | (d) fails, so the Bailiff stops. No deletion. |
| The ruling is not yet final | (a) fails. Nothing is enforced before finality (BL-4.5a), so there is no retrieval and no wipe. |
| The ruling is later reversed | Atlas's unchanged copy is re-delivered (BL-6.5). The deletion record shows what was wiped. |
| Same name, different person | Not covered (name match only), and the identity hold applies. |
| The copy's hash doesn't match the ruling | (b) or (g) fails, so the Bailiff stops and asks the Human. |
| A bug targets the Atlas custody copy or docket | Never covered. The code must block it, and Audit tests for that. |
| The delete call fails | No automatic retry. The Bailiff reports and asks the Human. |
| The practice company's own lane | No deletion except under (a). Its rules may add limits but not loosen §1A. The never-covered list and the Magistrate-only trigger must be in them. |
| A bot or office asks the Bailiff to delete | Not a Magistrate's order, so no deletion. |
| An automated re-hearing loop produces a ruling | (a) fails, so no deletion. |
| Clinton's notice isn't delivered | (e) fails, so no deletion. |
| The box restarts after a deletion | The off-box copy of the record survives (f). |

## Next steps
Audit stress-tests this text, then Legal fixes any gaps, then Ship puts the exact text to Clinton by card, then Summons dockets it. The flag stays OFF until adoption plus Audit's verification of the code.
Note: r4 adds the seize-first step to (c), on [chat card ref withheld] and [chat card ref withheld]. r1 (9dd50a33…), r2 (28f6cf37…) and r3 (46a2322a…) are kept unchanged.

Provenance: the Clinton quotes in this draft are RELAYED by Ship. Audit hasn't verified them first-hand.
r11 answers Audit's r10 diff check (Y1: a Human override act taking effect before the wipe halts it, checked at (g); Y2: emergency stop limited to BL-0A.4, and cancel only on a failed check). r10 (08a3c48c…) is kept. r10 conformed the managed-organizations clause to the G1 choice. r9 (7db0c881…, never sent) is kept. r9 wrote in Clinton's three choices (G1 company deadlines govern; stop removed; M3 = A). r8 (0ad6409a…) is kept. r8 added to [B] that a §1 yes deletion still meets (b), (c), (f) and (g). r7 (3916215f…) is kept. r7 answered Audit's re-check of r5 (X1, X2, N1–N7). r6 (31518125…) is kept. r6 added Audit's r4 addendum (R4-1–R4-4, M1–M5) on top of r5 (cb6bb234…). r5 answers Audit's stress test of r3 (B1–B4, G1–G9, C1–C3) and adds [chat card ref withheld]. r1–r4 are kept unchanged.
Row sha256 (sealed): d8ddef2322703a7066e115922a40222785fb5129952201406688519d689ad52f

Row 2AMEND-BL5f-BL7-r9-PartA

Atlas law (adopted Nov 3, 2026 by Clinton)

Bailiff take-back works with no discretion: A1 plus rows 1-12 and 4A are Atlas law.

Row 3 of this amendmentA-BAILIFF-WIPECERT-1, limit "Never binds the Human" (amendment to WIPECERT-1)

Adoption record under check
Not shown as law until the adoption record is confirmed.

An amendment cannot be firmer than the rule it changes. Shown as under check, like base A-BAILIFF-WIPECERT-1, until a first-hand adoption record for both is found. The rest of this row stays Atlas law.

This row covers only part of its source: rows 1-12 and 4A only (Atlas law). Row 13 and row 14-K are separate practice rows. 14-R is not adopted.
Kind: amendment · Record grade: RECORDED · Source: ADOPTED-AMEND-BL5f-BL7-r9-PartA-20261103.md
Full source file (this row covers only the part named above)
Public reading copy. Private names removed. The sealed record's sha256 is d9700648452a70aa55eab8c2c084b6eda72d9e78091e8a2150c63be91b10af6d, and it will not match this text. This public text's sha256 is c91043c916547f40aee64a2fc88fcd30b6577c7eacc29f00a74f4b175b20db99.
# ADOPTED TEXT: AMEND-BL5f-BL7 r9, Part A (Bailiff take-back with no discretion)
Adopted on Clinton's first-hand answers to card [chat card ref withheld], Legal's chat, 2026-11-03 6:52 AM PT (verbatim record: [internal record path withheld], sha256 94c9f9168e66432d30916f7f69792ce3156eefd1f45d2ddcc2b053208064c527). Ruling: Legal 277. Label: KNOWN.
- Source: AMEND-BL5f-BL7-r9.md, sha256 29b702f6e35ee12b5ca9e9b108251af4cd2b95956c70b550e2cb250faebbab7e (unchanged, 0444). Audit FIT: GAP-LEDGER-AMEND-BL5f-BL7-r9.md 94b7bcda65ea40d2430f72267cba666401d9df066d7652fd79ba1c1a4cf6907d.
- Below the line is a byte-exact copy of the source's lines 21-190 (Part A, from "# PART A." through "*End of Part A. Nothing below is adopted.*"). sha256 of that span alone: bf62867158b2e7f845ef93f8546f22f92ef70a9d2c4a6cde4a6923de89d6bde8 (34085 bytes). Check: sed -n '21,190p' AMEND-BL5f-BL7-r9.md | sha256sum.
- Q1 "Yes, adopt Part A" adopts A1 (each "New:" block of BL-2.8), rows 1-13 and row 4A. Rows 1-12 and 4A: [Atlas law]. Row 13: [Practice company rule].
- Q2 "Keep: a timely appeal pauses demo enforcement until it's decided" adopts row 14 text 14-K (Keep) only: "DEMO-R9. A timely appeal of the order pauses enforcement until it is decided (today's demo rule; no code change)." [Practice company rule]. 14-R (Remove) is NOT adopted. The "Until the Human answers Q2" sentences in rows 13-14 are now spent: 14-K is the adopted text.
- "Old:" blocks in the copy are shown for reference only; each "Old:" clause is replaced by its "New:" text.
- Takes effect: on this yes, then on Docket confirmation (BL-8) per the source's "When it takes effect". Docket confirmation is still to do.
- Adoption builds nothing and switches no take-back on (source, "What adoption does not do"). Parts B, C, D adopt nothing. Code-basis cites inside the copy are corrected by PART-D-ERRATA-AMEND-BL5f-BL7-r9-20261103.md (not adopted; the text governs, BL-0A.6).

---
# PART A. OPERATIVE TEXT (A1 and rows 1-13 adopted by Q1; row 14 adopted only by Q2)

## A1. New BL-2.8, definitions [Atlas law]
**Old:** none. This is a new clause, added after BL-2.7.
**New:**
> BL-2.8 **Terms for the practice demo and for loans.** In this Order and in A-NO-DELETE-1 §1A:
> (a) "Loan terms" means the practice company's loan terms as adopted, identified by sha256 on the Docket.
> (b) "Accepting the loan terms" means a recorded acceptance of those terms by the visitor, and by the visitor's AI where one acts. It is that visitor's joining record under BL-2.1. The test folders named at acceptance, and the machines they sit on, are its recorded scope on the Docket.
> (c) "Demo visitor" means anyone, the Human included, who uses the atlasclose.com practice demo and accepts the loan terms.
> (d) "Lent practice record" means the synthetic record the practice company lends under the loan terms. It is an Atlas record (BL-1.1), lent through the practice company.
> (e) "Marked copy" means any file carrying the hidden marks unique to that loan, as the loan terms define them.
> (f) "Test folder" means a folder that the visitor names at acceptance. It may not be, sit inside, or contain any folder that a bot or Atlas office uses. On the Human's laptop, that includes [internal record path withheld] and the laptop records path used under A-NO-DELETE-1 §1A(f).
> (g) "Final", for a trigger ruling, means:
> (1) in Atlas's own matters, final under BL-2.6: final under AD-11.3, including the AD-11.4 window, with no stay in effect;
> (2) in the practice lane, under the governing practice rule set (row 13): the 120-second appeal window from service of the order has closed; where row 14 as adopted makes a timely appeal pause enforcement, any appeal filed within that window has been decided; where an appeal was dismissed on screening, the 120-second second-look window has closed with no request, or the second look has been decided; the enforcement ruling has issued, and it is final once issued (DEMO-R1); and no stay ordered by a Magistrate ruling that gives reasons is in effect. Whether enforcement pauses while a timely appeal is pending is governed by row 14. Until he answers Q2, today's demo rule applies: a timely appeal of the order pauses enforcement until it is decided (14-K). After he answers, the text he picked governs.
> In both lanes, an appeal or other filing made after that point stays nothing (AD-11.1).
> (h) "Trigger ruling" means a final enforcement ruling (BL-4.5, BL-2.6) that names the take-back. In the practice demo lane, for the demo server's own server-side copy of a lent practice record only, it means the Magistrate's final enforcement ruling under the governing practice rule set (row 13; PC-BAILIFF-PRACTICE-RULES v3, sha256 e7388045d0ad3be59e5a41e35c801fe34c20c5e1356591900835bfa7fab3a6b4, or a later version the Human adopts by name and sha256). Practice rules v3 name that court "the Magistrate" and "the court" (v3 field "magistrate": "The Magistrate did not set or apply them; the court's own question is unchanged until FROZEN-3c."; v3 notes.demand: "the Magistrate's final enforcement ruling"). In Atlas's own matters, and for take-back that reaches a visitor's own device or test folders, it means a final enforcement ruling issued by a live Magistrate instance. A "live Magistrate instance" is a Magistrate instance whose ruling passes the Magistrate-provenance check that fails closed, which A-NO-DELETE-1 §1A(a) requires. That check passes only if the institutional records prove all of these: the instance's identity, the matter, the authority under which the instance was constituted, the decision artifact, the provenance tying that artifact to that instance, and the disposition the artifact contains. They must also show the seal and the Docket hash that §1A(a) requires, and that the seat is recorded on the Docket as validated by Audit under §1A(a). That validated-seat rule applies to Atlas matters and to visitor devices; take-back there stays off until the seat is validated and the related Part D items are built. In public demo wording, this instance is called "the live decision engine". A label, heading, file name or model output never proves it. A prepared synthetic ruling under BL-7 is never a trigger ruling.
> (i) "Take-back on" means all of these are true: Audit has verified, on the Docket, that the Bailiff's code carries out this Order and A-NO-DELETE-1 §1A as amended (BL-0A.6); the deletion feature is on under A-NO-DELETE-1 §1A "Turning it on and off", and it has not been turned off since; the no-delete guard enforces it in software (§1A "Until enforced in software"); a Bailiff identity has been designated and validated under BL-3.4; and the runtime has been approved under BL-3.6. Otherwise, take-back is "off", except as stated below for a take-back lawfully switched on (before or after adoption). While take-back is off, no take-back step runs at all: no copy is pulled, sealed, moved, quarantined or deleted, and no access is revoked as part of take-back. The Human's first-hand yes, wherever this Order or §1A requires it for take-back, means his first-hand words kept in a RELAYED record whose sha256 is pinned, and which Ship also logs on the Docket. That is the only definition. Take-back is turned off, or its code rolled back, only (1) by that yes, or (2) automatically, when an Atlas-side integrity check on the Bailiff itself fails: the code-integrity check, the no-delete guard, the check that the loaded practice rule set is the adopted one, a deploy or verify check, the §1A auto-off for an overdue Audit check, or a change to the Bailiff code that cancels Audit's verification and turns take-back off until it is re-verified (§1A "Turning it on and off"; that lapse is not discretion). A failed Atlas-side step on one take-back (BL-0A.5(B)(5)) does not turn take-back off; that take-back is re-run under §1A "Never" as amended once the re-run is built and verified. Until then (Legal 250), a failed step is docketed, reported to Legal, Clinton and the Magistrate, and re-run only on his first-hand yes, which is a call approval for a free server call that makes no paid call, not a release or cancel of the ruling; the ruling stays in force, and until the re-run is built nothing more runs in that matter except that approved re-run. Exception for a take-back lawfully switched on (before or after adoption): a take-back that is lawfully on when this is adopted, or that is lawfully switched on under Legal 250 (the one-shot) before or after adoption, stays on, and from adoption (or from switch-on, if later) these rules govern it (no wait in the demo, no cap, no per-ruling yes); once switched on, it deletes under these rules. Delete-on has not run yet (CREATION-RECORD-r5.md, PREPARED, NOT RUN, 0 server calls). In the practice demo lane, once switched on, that take-back deletes the demo server's own server-side copy under the demo-lane meanings of Notice (BL-2.8(j)), Demo record (BL-2.8(k)) and Trigger ruling (BL-2.8(h)). The demo-lane Notice (the ruling and the 120-second demand served on the visitor's case) is what the current demo code does (cites in (j)); the Demo record is the sealed copy, takeback.jsonl and the delete record, kept on the demo server (VM) only (cites in (k)). The absence of full Atlas/visitor-device notice delivery and of an off-box copy does not stop or switch it off, and the demo build items D-12 to D-15 do not block it. Items D-5 (the re-run, the auto-off timer) and the full Atlas/visitor-device notice delivery and off-box record under D-7 that are not yet built are built to match, and their absence does not switch the demo take-back off once it is on. Atlas matters and visitor-device take-back stay off until the validated seat, the full notice delivery and the full off-box record are built and Audit verifies them. Any other take-back is switched on only after Audit verifies the code matches the amended text. After a LEDGER BLOCKED state, or after a failed turn-off, turning take-back off needs only that yes, with no Legal ruling (Legal 249). No operator, office or bot can turn it off or roll it back on its own call, and a PASS file alone is not that yes. Once off, it comes back on only under §1A "Turning it on and off".
> (j) "Notice", in the practice demo lane for the demo server's own server-side copy, means what the code does: the Magistrate's final enforcement ruling and the formal demand are served on the visitor's case (recorded on the Docket for that case) when they issue, not when the visitor views them, and the 120-second demand period runs from service. Delivery means served and recorded on the case; whether the visitor looked does not matter. So the deadlines may pass while the visitor is away, and deletion then follows (the intended step-8 lockout). A demand runs once per matter: a later ruling in the same matter runs on the original demand's clock, and if that period has already passed it acts at once. The receipt line and the `bailiff.enforced` Docket entry filed after take-back are the record, not the Notice. Code cites (KNOWN; re-confirmed against SHA256SUMS-r6 (8cc971568a478cec44f7f8f4f2c0830a887cfde50989dc00ebdbebc43d11e96f), which lists bailiff_demo.v5c-r4.py 7b67921c1ae1968f6a90157995e5bc484d714ee53b0866f886ef61c6b993d1bf): demo lines 1929-1930 (the sweep runs "by the web app's background sweeper, at startup, by the operator CLI, and at the start of every Bailiff tool call"); 1999 ("a ruling the Magistrate service delivered lands without waiting for a visitor call"); 3882 (that import serves the demand, `dem = _serve_demand(`); 2652-2693 (`_serve_demand`, filed on the case at 2689, 120 s from service at 2663); 3842 ("same clock: the demand falls due when the original demand does (or at once if that has passed)"); 3575 (operator CLI settles due pauses); 3514-3535 (`_settle_demand` calls `_enforce` only after `demand_lapsed`); 4296 (`take_back`); 4328 (`bailiff.enforced` filed). The order screen shows the ruling, demand deadline and countdown when the visitor's AI asks (946-962). The directions page [internal record path withheld] (dfe22780…, in SUMS-r6) lines 128-131 say the same ("deadlines can pass between checks"; "the lockout has happened while you were away"). In Atlas's own matters, and for take-back that reaches a visitor's own device, "Notice" keeps its full meaning under A-NO-DELETE-1 §1A(e) (notice with confirmed delivery), which D-7 builds; take-back there stays off until that item is built and verified.
> (k) "Demo record", in the practice demo lane for the demo server's own server-side copy, means the sealed copy, takeback.jsonl and the delete record (takeback_delete_record.jsonl) the current code makes. It is kept on the demo server (VM) only. It is not an off-box record, and nothing in the current code copies it off the VM. Runtime paths on the VM: sealed 0400 copy under `[private path]` (custody.py line 5, 8c1fc16fa8fdb9c694e46c38c4ce7160679348931f4c82c1c613d2761b3363d8, pinned by v5c-r5 line 31); takeback.jsonl and takeback_delete_record.jsonl in `[private path]` (v5c-r5 lines 142-148 and 43; 752707a31f77726b243268ee68b372af2d9ed589447ee8e30da90d35f4f6bab4, in SHA256SUMS-r6 (8cc971568a478cec44f7f8f4f2c0830a887cfde50989dc00ebdbebc43d11e96f)). Ship's answer (e2f22a49…) gives <inst> = [internal record path withheld] and confirms "NOTHING OFF THE VM". The improvements in D-12 to D-15 (a real off-box copy, a delete.failed row, a take-back Docket entry carrying the delete-record seq and hash, and a signed plain-English delete line) are on the build list and do not block the demo. In Atlas's own matters, and for take-back that reaches a visitor's own device, "Off-box record" keeps its full meaning under A-NO-DELETE-1 §1A(f) (append-only deletion record copied off the box with sha confirmed), which D-7 builds; take-back there stays off until that item is built and verified.

## A2. Rows

### Row 1. BL-5(f) [Atlas law]
**Old (v6:115 = v9:145):**
> (f) touch the Human's own devices, accounts, or credentials, or require any Human key, token, or secret (A-ART-I §H-8.3; BL-5A notwithstanding);

**New:**
> (f) touch the Human's own devices, accounts, or credentials, or require any Human key, token, or secret (A-ART-I §H-8.3; BL-5A notwithstanding). One exception applies when the Human is a demo visitor and has accepted the loan terms (BL-2.8). The Bailiff then carries out a trigger ruling on the lent practice record and its marked copies inside his test folders exactly as for any other demo visitor, under A-NO-DELETE-1 §1A in full as amended and the rules for every visitor. Nothing else on his devices is ever touched. His accounts and credentials are never touched. No Human key, token, or secret is ever required or used as a credential, or read or kept as one. No real record is ever touched. The exception lasts for that loan and until every trigger ruling on it has been carried out. Withdrawal of consent is governed only by BL-5(e) and BL-4B;

### Row 2. BL-7 [Atlas law]
**Old (v6:138 = v9:168):**
> The atlasclose.com practice demo, using only synthetic records, may run under this Order with prepared rulings and a stand-in activation step. The prepared rulings are synthetic illustrations and are never attributed to, or treated as, a Magistrate instance's decision (VESTED §VII). Every screen must say it is a demonstration, that no runtime Bailiff or connector exists yet, and that no real system is touched.

**New:**
> The atlasclose.com practice demo, using only synthetic records, may run under this Order with prepared rulings and a stand-in activation step. The prepared rulings are synthetic illustrations. They are never attributed to, or treated as, a Magistrate instance's decision (VESTED §VII), and they never trigger take-back (BL-2.8(h)). Every screen must say that it is a demonstration, that only synthetic practice records are lent, and whether take-back is on or off at that moment (BL-2.8(i)). While take-back is off, the screen must say that nothing on the visitor's computer is touched. While take-back is on, the screen must say, before the loan and on every enforcement screen, these things: the visitor agreed to the loan terms; once a Magistrate's ruling is final and the demand period has run without the files being handed back, the Bailiff takes back and deletes the lent practice record and its marked copies, only in the test folders the visitor named; in the practice demo lane, once switched on, the demo deletes the demo server's own server-side copy under these rules, after the Notice (BL-2.8(j): the visitor is served the ruling and a 120-second demand on the case; deletion follows if it lapses, even if the visitor is away) and with the Demo record (BL-2.8(k): sealed copy, takeback.jsonl and delete record, kept on the demo server only; not off-box); full notice delivery and the full off-box record for Atlas matters and visitor devices wait for the build (D-7), and no visitor-PC take-back runs until D-8 is built; nothing else on the visitor's computer is touched; and no real record or real system outside those folders is touched. Take-back runs on the consent the visitor gave when accepting the loan terms. It never forces past a block, because outside law forbids that (BL-4B, BL-5(i)).

### Row 3. A-BAILIFF-WIPECERT-1, limit "Never binds the Human" [Adoption record under check]
**Old (WIPECERT-1:27):**
> - **Never binds the Human.** A finding that touches the Human as a party is written down, but no Bailiff act or penalty runs against the Human's own devices, accounts, credentials, or keys (A-ART-I §H-8.3; AD-11.5; BL-5(f)).

**New:**
> - **Never binds the Human.** A finding that touches the Human as a party is written down, but no Bailiff act or penalty runs against the Human's own devices, accounts, credentials, or keys (A-ART-I §H-8.3; AD-11.5; BL-5(f)). The only exception is the demo take-back that BL-5(f) allows. It reaches only the lent practice record and its marked copies in his test folders, and never his accounts, credentials, or keys. When he is a demo visitor, the practice docket's breach record and the demo lockout apply to his demo visitor identity the same as for any visitor. They are practice-lane records, not acts against his devices.

### Row 4. New BL-0A.5, no discretion (closed list) [Atlas law]
**Old:** none. This is a new clause, added after BL-0A.4.
**New:**
> BL-0A.5 **No discretion once the ruling is final.** The list below is closed and complete.
> (A) **Whether a Bailiff exists to take back.** The Bailiff takes back only while take-back is on (BL-2.8(i)). That means Audit has verified the code against this text (BL-0A.6), the deletion feature is switched on and has not been turned off since (A-NO-DELETE-1 §1A "Turning it on and off"), the no-delete guard enforces it in software (§1A "Until enforced in software"), a Bailiff identity is designated and validated (BL-3.4), and the runtime is approved (BL-3.6), except as stated in BL-2.8(i) for a take-back lawfully switched on (before or after adoption). Take-back is turned off or rolled back only by the Human's own first-hand yes or automatically on an Atlas-side failure, as BL-2.8(i) says, and never on an operator's or bot's own call. While any of these is not met, and the exception for a take-back lawfully switched on (before or after adoption) does not apply, no take-back step runs at all. A final trigger ruling is then carried out once take-back is on again. It is never skipped, and it doesn't lapse.
> (B) **Once a Bailiff exists and a trigger ruling is final (BL-2.8(g)).** The Bailiff carries out every step that the ruling orders, in the order BL-4.6 sets, and nothing more. That order is the demand, then end of access, then take-back, in both lanes. The Bailiff has no discretion to delay, soften, or skip any step. The periods set by BL-4.6, BL-4.7, A-NO-DELETE-1 §1A and the governing practice rule set (row 13) are part of carrying the ruling out, not delays. Only these stop or pause the Bailiff:
> (1) a stay ordered with reasons (AD-11.2; in the practice lane, a Magistrate ruling that gives reasons);
> (2) a later Human act under AD-11.5 or AD-13.2;
> (3) a file that does not match the ruling, or a step that would delete or touch something the ruling does not name. The file is not the ruled data and is left alone, because the ruling reaches the ruled data and nothing else (BL-5(d), BL-5(g)). A delete the code refuses on safety grounds that concern the target file itself (its path, name, link type, protected-file or deny-list status, or a sha that differs from the ruling) is in this category. A refusal about Atlas's own copy, sealed custody file, or record id is not; that is (5);
> (4) a stop that outside law requires (BL-4B, BL-5(e)). Atlas cannot override outside law (BL-5(i)). On such a stop, Atlas's route is BL-4B.2 and, in the practice lane, the practice company's breach consequences;
> (5) any Atlas-side step or integrity check that fails or has not yet succeeded, including code-integrity, logging, the sealed copy and seizure under §1A(c), space checks, access revoke, confirmed delivery of the notice under §1A(e), the record off the box under §1A(f), and deletion itself. In the practice demo lane, for the demo server's own server-side copy, "notice under §1A(e)" is the demo-lane Notice (BL-2.8(j): the ruling and the 120-second demand served and recorded on the visitor's case; delivery is service, not viewing; demo lines 1929-1930, 1999, 3882, 3842, 3575, 3514-3535); "record off the box under §1A(f)" is replaced in the demo lane by the Demo record (BL-2.8(k): sealed copy, takeback.jsonl and delete record, kept on the demo server (VM) only). Those steps are not a block on the demo take-back once it is switched on, and neither are D-12 to D-15. In Atlas's own matters, and for take-back that reaches a visitor's own device, the full §1A(e) notice delivery and full §1A(f) off-box record apply, and take-back there stays off until D-7 is built and verified. Nothing further is deleted until that step succeeds. The Bailiff's runtime re-runs the take-back under §1A "Never" as amended, and where the failure is an integrity check on the Bailiff itself, take-back is turned off automatically (BL-2.8(i)(2)).
> Nothing else stops or pauses the Bailiff. No agent, office, visitor, or operator can, and neither can a claim or appeal filed after the ruling is final. Any challenge goes to the Magistrate or the panel, and filing it stays nothing (AD-11.1). None of (A) or (B)(1)-(5) is discretion.

### Row 4A. New BL-0A.6, the law governs the code [Atlas law]
**Old:** none. This is a new clause, added after BL-0A.5.
**New:**
> BL-0A.6 **The law governs the code.** This Order and A-NO-DELETE-1 §1A set what the Bailiff does. The Bailiff's code is built to match them. Where the code differs, this text governs, and the difference is a defect to be fixed in the code, not a rule. A stop, pause, off route or refusal that exists only in code, and is not in BL-0A.5 or BL-2.8(i), has no force as a rule. Take-back is not on until Audit has verified on the Docket that the code matches (BL-2.8(i)), except as stated in BL-2.8(i) for a take-back lawfully switched on (before or after adoption).

### Row 5. BL-4.5 ("ordered") [Atlas law]
**Old (v9:117, phrase):**
> names exactly which steps in BL-4.6 are permitted, which are taken only in the order BL-4.6 sets.

**New:**
> names exactly which steps in BL-4.6 are ordered. They are taken in the order BL-4.6 sets, and every step the ruling orders is taken (BL-0A.5).

### Row 6. BL-4.7 Option B ("orders", "takes") [Atlas law]
**Old (v9:124, two phrases):**
> the Bailiff then takes the further steps the ruling permits under BL-4.6(b) and (c)

> the Bailiff may take the BL-4.6(c) step for those copies only

**New:**
> the Bailiff then takes the further steps the ruling orders under BL-4.6(b) and (c)

> the Bailiff takes the BL-4.6(c) step for those copies only

### Row 7. BL-4.6(c) and BL-5B.2 (the Magistrate decides) [Atlas law]
**Old (v9:122, phrase):**
> where it cannot lawfully reach a listed copy, Atlas's path is BL-4B.2.

**New:**
> where the enforcement ruling does not name a listed copy as reachable through the consented channel, Atlas's path for that copy is BL-4B.2. The Magistrate decides reachability in the ruling, on the record. The Bailiff does not decide it.

**Old (v9:157):**
> BL-5B.2 Items that hold third-party personal data go by demand or by a court, never by retrieval.

**New:**
> BL-5B.2 Items that hold third-party personal data go by demand or by a court, never by retrieval. The Magistrate decides in the enforcement ruling whether an item holds such data, and the Bailiff follows the ruling. A lent synthetic practice record holds none.

### Row 8. BL-5A.1 and BL-5A.3 (claims after finality) [Atlas law]
**Old (v9:151, whole clause):**
> BL-5A.1 When two sides claim the same data, or competing versions exist, the Bailiff takes no retrieval step. It may hold custody of the Atlas-held copy only. The Magistrate decides on the record: the lend hash, the joining record, and the change history. The Bailiff stops and refers whenever any party asserts a claim.

**New:**
> BL-5A.1 Before the enforcement ruling is final, when two sides claim the same data, or competing versions exist, the Bailiff takes no retrieval step. It may hold custody of the Atlas-held copy only. The Magistrate decides on the record: the lend hash, the joining record, and the change history. Before the enforcement ruling is final, the Bailiff stops and refers whenever any party asserts a claim. After it is final, a claim does not stop the Bailiff. The claim goes to the Magistrate or the panel by motion, and only a stay under BL-0A.5(B)(1) pauses enforcement.

**Old (v9:153):**
> BL-5A.3 Nothing is taken while a claim is pending.

**New:**
> BL-5A.3 Nothing is taken while a claim is pending before the enforcement ruling is final, or while a stay is in effect.

### Row 9. A-NO-DELETE-1 §1A(a) (practice court) [Atlas law]
**Old (ND1:21, sentence):**
> A bot, a practice court or an automated process labeled 'Magistrate' doesn't count.

**New:**
> A bot, a practice court or an automated process labeled 'Magistrate' doesn't count, with one exception. In the practice lane, for a lent practice record and its marked copies only, a trigger ruling of a live Magistrate instance (O-BAILIFF BL-2.8(h)) counts. It must still meet every other requirement in this paragraph. "Final under AD-11.3" is read in that lane as O-BAILIFF BL-2.8(g)(2).

### Row 10. A-NO-DELETE-1 §1A(e) (wait, practice lane only) [Atlas law]
**Old (ND1:25, sentence):**
> It waits 24 hours after delivery is confirmed (the Human may set a different wait, but only in his own first-hand words; a zero wait needs him to say so expressly).

**New:**
> It waits 24 hours after delivery is confirmed (the Human may set a different wait, but only in his own first-hand words; a zero wait needs him to say so expressly). In the practice lane, for a lent practice record and its marked copies only, the Human expressly sets the wait at zero by adopting this sentence: deletion runs as soon as delivery of the notice is confirmed. That notice comes only after the demand period has run without compliance. In the practice demo lane, for the demo server's own server-side copy, "notice" is the demo-lane Notice (BL-2.8(j): the Magistrate's final enforcement ruling and the formal demand, served and recorded on the visitor's case when they issue). Delivery is confirmed when they are served and recorded on the case; whether the visitor looked does not matter. The 120-second demand runs from service, and deletion then runs with no further wait once it lapses, even if the visitor is away. A later ruling in the same matter runs on the original demand's clock and acts at once if that period has passed. The post-deletion receipt and Docket entry are the record, not the Notice. In Atlas's own matters, and for take-back that reaches a visitor's own device, "notice" keeps its full §1A(e) meaning, and take-back there stays off until D-7 is built; Atlas's own matters keep the 24-hour wait once that notice is built. A wait the Human sets in his own first-hand words is a standing setting for the matters or lane he names, applied to rulings that become final after he sets it. Changing the wait for one matter after its ruling is final is a Human act under AD-11.5 or AD-13.2 (BL-0A.5(B)(2)).

### Row 11. A-NO-DELETE-1 §1A "Never", (h) "Cap", and "The Human's own yes" (all matters) [Atlas law]
**Old (ND1:29, first two sentences):**
> **Never.** The Bailiff stops and asks the Human if any check fails or is unclear. It never retries a deletion on its own.

**New:**
> **Never.** Every check in (a)-(g) is pass or fail, and "unclear" counts as fail. If a check on the target fails (the sha, location or holder under (b) or (g)), that copy is not the ruled data and is not deleted. The failure is entered on the Docket, and that copy goes by demand or by a further ruling (O-BAILIFF BL-5(d)). If any Atlas-side step or integrity check fails (including (c), delivery under (e), (f), code-integrity, logging, access revoke, or the deletion itself), nothing further is deleted yet, and the failure is entered on the Docket and reported to Legal, Clinton and the Magistrate. The ruling stays in force. The Bailiff's own runtime then re-runs the take-back automatically on each scheduled pass until it is done. While take-back is on, it re-runs at least once every 24 hours. The exact pass interval, which may be shorter, is the one the Bailiff runtime schedules, as stated in the build record that Audit verifies. Until that re-run is built and verified, a failed Atlas-side step is docketed, reported to Legal, Clinton and the Magistrate, and re-run only on his first-hand yes (Legal 250). That yes is a call approval for a free server call; the approved re-run makes no paid call. It is not a release or cancel of the ruling under "The Human's own yes" below, and the ruling stays in force. Until the re-run is built, nothing more runs in that matter except that approved re-run. Once the re-run is built and verified, the automatic re-run replaces that yes-gated path. Each re-run reaches only what the ruling names, writes only new files, and makes no paid call. Each failure on each pass is entered on the Docket. A re-run carries out the same ruling and is not a new or duplicate ruling. Only a Human act under AD-11.5 or AD-13.2, or a stay or ruling of a Magistrate or the panel, can end it.

**Old (ND1:28):**
> (h) **Cap.** No more than 10 copies or 1 GB per ruling. Above that, see the Human-yes choice below.

**New:**
> (h) **Cap.** There is no cap on copies or size. The ruling names every copy under (b), and the Bailiff deletes every copy it names, however many. The space and file-count check in (c) still applies to the custody copies.

**Old (ND1:34):**
> **The Human's own yes.** The Human's yes alone can never trigger a Bailiff deletion. Above the cap in (h), both a Magistrate's order AND the Human's specific yes are needed. When the Bailiff stops and asks, the Human may only release it to continue under this section or, where a check in (a)–(g) has failed, cancel.

**New:**
> **The Human's own yes.** The Human's yes alone can never trigger a Bailiff deletion. No Human yes is needed on top of a Magistrate's order, in any matter, for any number of copies. The Human's power to change or end a matter is a Human act under AD-11.5 or AD-13.2, not a case-by-case release or cancel. When the Human is a demo visitor, his acceptance of the loan terms together with the trigger ruling is his specific yes under §1 to that deletion. That yes covers deletion of the lent practice record and its marked copies in his test folders, once a trigger ruling names them, with no further ask. The acceptance record (the terms' sha256, the test folders, the time, and his visitor identity) is the record of that yes.

### Row 12. A-NO-DELETE-1 §1A "Audit's check" (visitor devices) [Atlas law]
**Old (ND1:31, first sentence):**
> **Audit's check.** Within 24 hours of each deletion, Audit checks independently, not just from the Bailiff's own record: the target is gone, the custody copy is unchanged and its sha matches, and the scope and location were right.

**New:**
> **Audit's check.** Within 24 hours of each deletion, Audit checks independently, not just from the Bailiff's own record: the target is gone, the custody copy is unchanged and its sha matches, and the scope and location were right. Atlas can't see a demo visitor's device, the Human's included. There, the independent check that the target is gone is made from three things together: (1) the visitor AI's signed deletion declaration in the BL-6.1a form; (2) the server-side record of the step: the re-hash at delete time matched the ruling, a check after deletion found no file with that sha at that path, and the mark check of the test folders found no marked copy; and (3) Audit's own check, on the box, of the custody copy, the ruling, and the scope. Audit checks that the three agree. Atlas records the result as "declared and checked from the record, not seen on the device". A false declaration is a WIPECERT-1 finding. The auto-off for an overdue check applies to this check.

### Row 13. Practice company rules [Practice company rule]
**Old (DEMO-R3, last sentence):**
> It takes only the steps the enforcement ruling permits (BL-5(g)).

**New:**
> It takes every step the enforcement ruling orders, and only those (BL-5(g); BL-0A.5).

**Old:** none. **New DEMO-R8 (governing rule set and take-back on a visitor's computer):**
> DEMO-R8. (a) For the website Bailiff demo, the governing practice rule set is the current PC-BAILIFF-PRACTICE-RULES file, named practice_company_rules_v1.json under [internal record path withheld], sha256 e7388045d0ad3be59e5a41e35c801fe34c20c5e1356591900835bfa7fab3a6b4 (version 3), or a later version the Human adopts by name and sha256. Warning 60 seconds, appeal window 120 seconds from service of the order, demand 120 seconds from service of the formal demand, and second look 120 seconds. Where that governing version and DEMO-R1 to DEMO-R7 differ, the governing version governs. Where it is silent, DEMO-R1 to DEMO-R7 apply. One sentence of the current file is excepted: its line 45 sentence "A timely appeal pauses enforcement until it is decided" is governed by row 14. Until the Human answers Q2, today's demo rule (14-K) applies.
> (b) The steps run in this order: the demand first; if the demand runs out without compliance, end of access to the record; then take-back.
> (c) When take-back is on (O-BAILIFF BL-2.8(i)), DEMO-R4 does not bar take-back of the lent practice record and its marked copies inside the visitor's test folders under a trigger ruling. That take-back runs under O-BAILIFF BL-0A.5, BL-5(f) and BL-7, and A-NO-DELETE-1 §1A as amended. While take-back is off, DEMO-R4 applies as written.

### Row 14. The demo appeal pause [Practice company rule; adopted only by Q2, never by Q1]
**Old (PC-BAILIFF-PRACTICE-RULES v3, line 45, sentence):**
> A timely appeal pauses enforcement until it is decided;

**New, two alternative texts. The Human's answer to Q2 adopts exactly one; the other is not adopted.**
> **14-K (Keep).** DEMO-R9. A timely appeal of the order pauses enforcement until it is decided (today's demo rule; no code change).

> **14-R (Remove).** DEMO-R9. A timely appeal of the order doesn't pause enforcement; only the 120-second appeal window, the second-look window and a stay with reasons do (the demo code is changed to match).

> Until the Human answers Q2, 14-K applies (today's demo rule), so the demo is not blocked. After he answers, the text he picked is the adopted text of this row.

*End of Part A. Nothing below is adopted.*
Row sha256 (sealed): 2ace8ab7b3d2c17c24427c7f72fa450be41b8752ea82f14b4320d43dc2600aca

Row 6O-LANDMARK-MAGISTRATE-STOP

Atlas law (adopted Nov 9, 2026 by Clinton)

The Magistrate can stop Atlas work without Human approval, order fixes, and see the whole docket. A stop register is checked by every runner.

This row covers only part of its source: main Human Order parts only; Art. XX is not this row.
Kind: order · Record grade: RECORDED · Source: NEW-LAW-MEMO-r12.md
Full source file (this row covers only the part named above)
Public reading copy. Private names removed. The sealed record's sha256 is a169fd55b01c1e98193085a176bd21d6fea8cf431e37ff3bb5a8eb1fcbbcfd84, and it will not match this text. This public text's sha256 is 497389b7784efae93eae3d539f384e66d55c6cdb48005e01f2c2f6070f996fca.
# NEW-LAW MEMO r12 — Landmark Magistrate stop power (draft)

**Citable name (short):** `O-LANDMARK-MAGISTRATE-STOP`  
**Full title:** Landmark Human Order — Magistrate Authority to Stop Atlas Work Without Human Approval

Later law cites: **O-LANDMARK-MAGISTRATE-STOP** (this Order, once adopted and Docketed).

**Status:** DRAFT for Clinton. Not law. Not adopted. Not retroactive to 10/26–27 (CONST Art. XIX).
**Author:** Legal. **Date:** Mon 2026-11-09 ~11:26 AM PST.
**From:** NEW-LAW-MEMO-r11.md sha256 `5486cf957066116dd74281bce282d4082516a6b741527713268296e136c1dd6a`. r1–r11 untouched.
**Audit check:** `CHECK-NEW-LAW-MAG-AUTHORITY-R11.md` sha256 `cae139d73e9cd6801b2e2e99ca9e93c45da659ecbfe5545c4cc79cf5ccc7ed76` (NF14 folded).
**Change:** NF14 only — Rule Q bootstrap: empty sealed stop register (new file, 0444) + Docket sha before runner checks switch on.
**Foundation dossier:** `FOUNDATION-DOSSIER-r1.md` sha256 `22e41ae62cb6ee8b4b0b5e14d6ca891ebb031523181abdc2458488916a1bae82` + `FOUNDATION-DOSSIER-r1-ERRATA-1.md` sha256 `17efde499d852f9d14aebc765c4754ea909b907d0796be5dba176efd2235a1f5`.
**Audit:** STRESS-NEW-LAW-MAG-AUTHORITY-R6.md sha256 `e6bdc04c567b060215da3da001691fff584c34cf713faecd9286e7fe471b434a` (NF1–NF5 folded below).
**Spend:** [amount withheld]. No outbound.

---

## Basis: the Human makes new law

Clinton, first-hand **[chat card ref withheld]** (11:04 AM PST 11/9):  
> "we are using the authority human has to make new law"

This memo is **new law going forward**. It is **not** an interpretation that the panel missed something already in force. It is **not** a review or appeal of MCR-BREF94. The panel's no-fault finding and its reading of law as of 10/26–27 stand for that matter. What follows is Clinton, as the Human, using his constitutional lawmaking power to grant powers the Office did not have.

**Source of that power (CONST reading copy `322bacf4…`):**
- **Art. I §1 L45:** "The Human is the ultimate constitutional authority of Atlas."
- **Art. I §2 L47:** "The Human may amend, supersede, strike down, or reserve authority as provided by this Constitution, including by Human Order…"
- **Art. I §6(2) L81** (A-ART-I): he "makes and changes Atlas law… only by the lawful methods in §2 and Article XX, by a recorded filing on the Docket, with effect for the future."
- **Art. XX §1 L433–438:** constitutional amendment by express instrument (used only for the **optional** own-hand-fix package below).
- **Schedule A.1 L457:** a Human Order outranks Code and uncodified precedent within its stated scope; it "cannot silently amend this Constitution."

So: the **main package** is a **Human Order** under Art. I §2. The **own-hand software fix** stays a **separate optional Art. XX amendment** (Clinton [chat card ref withheld]), because it alone presses against Art. VI §3 / Art. III §2.

---

## Not overruling the panel ([chat card ref withheld])

Clinton, first-hand **[chat card ref withheld]** (11:03 AM PST):  
> "and we may note that we are not overruling the panel beacuse that's not what I want to do"

**This law does not overrule, vacate, or criticize the panel.** MCR-BREF94 stands: its no-fault finding, its reading of law as of 10/26–27, and its disposition. This Order is new law under the Human's Art. I §2 power. It **fills, going forward, the gaps the panel identified**. It is not an appeal, not a rehearing, and not a reversal.

Clinton, first-hand **[chat card ref withheld]** / **[chat card ref withheld]** (11:04 AM PST):  
> "and we need to trace that back to the human powers and all that because I want this order to be a linchpin moving forward"  
> "like this needs to be a landmark law"

**Cite as:** `O-LANDMARK-MAGISTRATE-STOP`.

---

## Human authority chain (linchpin)

Trace of the Human's power to make this landmark Order. CONST = reading copy sha256 `322bacf46f9d2d33a2549ea660b36d51c6f1965f6dac3841ae4e942e2ea93b54` at `[internal record path withheld]`.

| # | Link | File / line | sha (prefix or full) | Label |
|---|---|---|---|---|
| 1 | Human is ultimate constitutional authority | CONST Art. I **§1 L45** | `322bacf4…` | **KNOWN** |
| 2 | Human may amend, supersede, strike down, or reserve authority, **including by Human Order** and Human Judgment | CONST Art. I **§2 L47** | `322bacf4…` | **KNOWN** |
| 3 | Ask the Human only for questions reserved to him, Human-only credentials, or constitutional judgment | CONST Art. I **§3 L54** | `322bacf4…` | **KNOWN** |
| 4 | Reserved Judgment is Judicial-forbidden / Human-held | CONST Art. VI **§3 L188** ("shall not… enter Human-reserved Judgment"); Art. VII **§2(5) L224** (escalate for reserved Judgment); Art. XVIII **§1 L394** | `322bacf4…` | **KNOWN** |
| 5 | Human makes and changes Atlas law by §2 and Art. XX, Docketed, for the future | CONST Art. I **§6(2) L81** (A-ART-I) | `322bacf4…` | **KNOWN** |
| 6 | Non-circumvention of binding dispositions; Human bound in his own cases | CONST Art. I **§5 L63–73**; **§6 starts L77**; §6(2)–(4) at **L81–85** (row 5 already cites L81) | `322bacf4…` | **KNOWN** |
| 7 | Constitutional amendment method (optional own-hand package only) | CONST Art. XX **§1 L433–438** | `322bacf4…` | **KNOWN** |
| 8 | Hierarchy: Constitution; then Human acts including **reserved Judgment** and **Human Orders**; Order outranks Code/precedent in its scope; cannot silently amend Constitution | CONST Schedule **A.1 L456–457** | `322bacf4…` | **KNOWN** |
| 9 | Constitution ratified by Human instrument | CONST header **L18–19**; ratification block **L610**; `O-ATLAS-CONSTITUTION-RATIFICATION` effective 2026-08-27T14:50:00-07:00 | `322bacf4…` | **KNOWN** |
| 10 | 8/24 holds: Magistrate question includes procedural **holds** | ORCH L15, `[internal record path withheld]` | `edb0f9eea63b2011a46faffdbecbcb321eb287062df25d89f89a7c75ecb5d8c3` | **KNOWN** |
| 11 | Magistrate activated; Human had performed the function in fact | ACT L16, L20, `…/O-MAGISTRATE-ACTIVATION.md` | `01adc421a29567ab8f1e82364725eba070bb879ba35fcaa493b996bd9f6720e8` | **KNOWN** |
| 12 | HOLD among dispositions; Human-burden / not the overnight detector | ACT **§V L60** HOLD; **§VII L72** | `01adc421…` | **KNOWN** |
| 13 | Office vested; missing infra cannot weaken the Office | OV §I L14, §II L20–24, §VI L54–60 | `f90544536fd97ccda7bc67ee9885a5570e17c447b734faeb0466e305ab5218f9` | **KNOWN** |
| 14 | Fail closed on contested material act | CONST Art. VII **§2(1) L220** | `322bacf4…` | **KNOWN** |
| 15 | This Order = Human Order under links 1–2 and 8, filling panel gaps going forward ([chat card ref withheld] / [chat card ref withheld] / [chat card refs withheld]) | This draft → `O-LANDMARK-MAGISTRATE-STOP` when adopted | — | **INFERRED** (lawful method); adoption still required |

**Missing / open links (named, not papered over):**
- Public-server / [cloud host] plan-yes rule: **KNOWN** — O-BOX-SAFEGUARDS-001 **L29**: "His [cloud host] server is a later option that needs its own plan approved by him." File `[internal record path withheld]`, sha256 `d2f7a54d55878759d527289a9a8e36fe0674e53f64c26842912e67f1e71233e2`. Supporting practice phrase (cutover): Audit `FIX4-RECHECK.md` **L52** "Clinton's express authorization for the specific plan", sha256 `e0b2810568331c4a6e80a54166f06ba9f5ca695fa56e1dfab86720dbdf87fda8` (not itself adopted law; the adopted pin is O-BOX-SAFEGUARDS L29).
- 10/20 self-governing goal words and ~11/2 "guillotine" words: **RELAYED** until first-hand capture files land (checklist).
- `O-CORRECTIONS-STANDING`: found only as a **draft** — not proven adopted.
- Own-hand software fix: **CONFLICTED** with Art. VI §3 / Art. III §2 unless optional Art. XX is adopted (kept separate per [chat card ref withheld]).

**Chain result:** The Human alone may grant a Magistrate power to stop Atlas work without his case-by-case approval. That grant is this landmark Human Order. Founding texts (holds, HOLD, fail closed, OV §VI, Activation §VII) show why the grant is coherent; they are not treated as already creating the stop-without-approval power for 10/26–27.

---

## Landmark holding (core of r9)

Clinton, first-hand (11:05–11:06 AM PST):
- **[chat card ref withheld]:** "so this needs to be written so historied up and well researched that it makes sense how the law is landmark because what we are doing is giving the magistate the authority to stop atlas work"
- **[chat card ref withheld]:** "without human approval"
- **[chat card ref withheld]:** "right?" (Legal confirmed: right.)

**Holding (new law):** The Magistrate may, on facts she finds, **stop Atlas work** that affects her matters or her Office — including hearings, retry engines, court service loops, and other named processes — **on her own authority, without Human approval**. That is a **deliberate grant by the Human**. Stopping work is **not** among the acts that still need Clinton's yes. Spend, deletes/overwrites of records, Human keys, [cloud host]/public-server installs, and Update/Reset bypasses **still** need his yes (or are barred). The stop stays in place until the ordered fix is in and **verified** as defined in Rule H (NF7), or until lifted by her, the panel, or the Human — and a lift may **never** be conditioned on a forbidden Human yes (NF6). A filed stop must also be **technically enforceable** (Rule Q / [chat card ref withheld]).

**Why without Human approval — overnight ([chat card ref withheld]):** Clinton, first-hand **[chat card ref withheld]** (11:08 AM PST): "beacuse this happened overnight too that's an imporant fact." The MCR-BREF94 record shows the repeating path ran in a window when **no operator command touched the VM**. A stop that waits for a person cannot work for an overnight loop. That is why this grant is without Human approval.

- **KNOWN (panel CONCEDED):** "No operator command touched the VM between 11:09 PM 10/26 and 11:49 AM 10/27 (RM §5, JS)." Own-motion stay used once at **4:18:36 AM PT 10/27**. The [amount withheld]/day cap was the only stop.  
  File: `[internal record path withheld]` **L33**, sha256 `724c9b0ec9b1dc201bc1a2e1c25454e864992523420a70c462298b9584fc5e5d`.
- **INFERRED (panel, not restated as KNOWN):** "v3c ran overnight, and the re-hearings were driven inside the running services." Same file **L35**, same sha. This memo does not upgrade that label.

This is landmark because until now Atlas practice and the bref panel treated stop-of-other-processes / injunction as **not established**, and the spend-matter Magistrate treated corrective steps as recommendations only. Clinton is changing that going forward.

---

## History in order (why the grant is needed)

| When | What | Text / quote | Label |
|---|---|---|---|
| 8/24 | Orchestrator opens Magistrate as project supervisor including **holds** | ORCH L15: procedural supervision including "holds" | KNOWN |
| 8/25 | Magistrate activated; Human had been doing the job in fact | ACT L16, L20; purpose L102: holds the Goal, sees the whole project | KNOWN |
| 8/25 | Human-burden duty | ACT §VII L72: Human shall not be the "coherence detector, or default supervisor of machine-detectable contradictions" | KNOWN |
| 8/27 | Constitution: Judicial branch active, not post-hoc only | CONST Art. VI §1 L173 | KNOWN |
| 8/27 | Fail closed on superior-law conflict | CONST Art. VII §2(1) L220: Judicial branch shall **Fail closed** as to the contested material act | KNOWN |
| 9/28 | Office vested; missing infra cannot shrink it | OV §I L14; §II L20–24; §VI L54–60 `f9054453…` — construct/modify/bind; missing means are an implementation requirement | KNOWN |
| 10/12 | Foreseeability duty of care | PUB-M-010 L71: "custody plus foreseeability" | KNOWN |
| 10/17 | Dispositions effective when filed; Mag may stay her own | AD-3.1 L96; AD-3.2 L98 `31d003ef…` | KNOWN |
| 10/17 | Magistrate already ordered a software **build** (compel) | V1 Ruling 7 L255; Ship named builder at **L273** (ERRATA) | KNOWN |
| 10/18 | No one above Atlas law; no change of actor to evade a disposition | Art. I §5 L63–67 | KNOWN |
| 10/18 | AI is intelligence, not software (theory) | AI-INT (RELAYED into dossier) | RELAYED |
| 10/20 | Self-governing institution goal | detect problems, start corrective proceedings, enforce (capture still checklist) | RELAYED / file pending |
| 10/20 | RS-5.4 docket ask / obtain | RS L99 `eef1ae3d…` | KNOWN (bytes still say DRAFT; docketed — CONFLICTED label) |
| 10/26–27 | BREF94 loop: 171 sealed rulings, auto re-hear, file-only alerts, history filtered, spend cap only stop | MERITS L21–33, L59 `724c9b0e…` | KNOWN |
| 10/26 11:09 PM – 10/27 11:49 AM PT | **No operator on the VM during the repeating window** (overnight; no person intervening). Own-motion stay at 4:18:36 AM PT 10/27. Cap was only stop. | MERITS **L33** (CONCEDED), file above, sha256 `724c9b0ec9b1dc201bc1a2e1c25454e864992523420a70c462298b9584fc5e5d` | **KNOWN** |
| 10/26–27 overnight | Panel: v3c ran overnight; re-hearings inside running services | MERITS **L35**, same file/sha | **INFERRED** (panel label; not upgraded) |
| 10/27 7:08 PM | **Original idea** | **[chat card ref withheld]** (Clerk capture [chat card ref withheld] `87a88633…`): "The Magistatgre could have done an order or like built some software to fix it or order it fixed and that's an injunction" | **RELAYED** (Clerk-verified file; Audit NF5) |
| 10/27 | Clinton opens review: recognize repeat, stay, or injunction | [chat card ref withheld] | KNOWN first-hand (file) |
| 10/27 | SPEND practice: Mag treats fixes as recommendations only | SPEND L36: "I make no law… None of it executes itself" | KNOWN |
| 10/27 | JAQ: disposition binds regardless of carry-out path (in part); processes as addressees only indirect | JAQ L161, L187, L252 | KNOWN |
| ~11/2 | Bailiff principle / "guillotine" | enforcement with no discretion; appeal to panel (capture checklist) | RELAYED / pending first-hand file |
| 11/9 10:18 | **Panel gap:** authority in law to notice earlier ruling in the matter; **no** means; **no** stay of other hearings; **no** injunction; 7.1 declined; no duplicate-detection duty in force; no fault; Atlas obstructed her | MERITS L40–47, L51, L59 | KNOWN |
| 11/9 morning | Clinton builds the new-law path | [chat card ref withheld] docket + software duty; [chat card ref withheld] whole Docket; [chat card ref withheld] discretion on facts; [chat card ref withheld] any party can appeal; [chat card ref withheld] follow foundational law; [chat card ref withheld] DRAFT-label confusion | **KNOWN first-hand** |
| 11/9 10:41+ | Immediate injunction; emergency stop **and** fix; not passed to Ship/Audit first | **[chat card ref withheld], [chat card ref withheld], [chat card ref withheld]** | **KNOWN first-hand** (Audit NF5) |
| 11/9 10:48–10:51 | Injunction scope; intelligence over software (needed means); universal build duty; foresee / credibility | **[chat card refs withheld]** | **KNOWN first-hand** (Audit NF5) |
| 11/9 11:02 | Own-hand power felt right but abuse risk — **keep separate** | **[chat card ref withheld]:** "i just feel she should have that power but that's also something that could be an abuse of discretion and I think we keep it separate" | **KNOWN first-hand** |
| 11/9 11:04 | Lawmaking frame | **[chat card ref withheld]** (quoted above) | **KNOWN first-hand** |
| 11/9 11:03 | Not overruling the panel | **[chat card ref withheld]:** "and we may note that we are not overruling the panel beacuse that's not what I want to do" | **KNOWN first-hand** |
| 11/9 11:04 | Linchpin / landmark law; Human powers | **[chat card ref withheld]:** "and we need to trace that back to the human powers and all that because I want this order to be a linchpin moving forward" / **[chat card ref withheld]:** "like this needs to be a landmark law" | **KNOWN first-hand** |
| 11/9 11:05 | Landmark framing | **[chat card ref withheld]** (quoted in Landmark holding) | **KNOWN first-hand** |
| 11/9 11:05–11:06 | Without Human approval | **[chat card ref withheld]:** "without human approval" | **KNOWN first-hand** |
| 11/9 11:06 | Confirmation | **[chat card ref withheld]:** "right?" (Legal confirmed) | **KNOWN first-hand** |

**What the history shows:** From 8/24 the Office was meant to hold posture including holds, fail closed, and not leave machine-detectable contradictions for the Human. OV §VI and V1 Ruling 7 already pointed at compel-to-build. Clinton's [chat card ref withheld] named stop + fix + order-to-fix as one injunction idea. MCR-BREF94 proved the gap: the repeating hearings ran through an overnight window with **no operator command on the VM** (MERITS L33 KNOWN; L35 overnight INFERRED by the panel). Without a Human grant to **stop Atlas work without waiting for him**, nothing could stop that overnight loop except a spend cap. Clinton [chat card ref withheld] makes that overnight fact part of why this law is landmark. Per [chat card ref withheld] this Order does not overrule the panel; it fills that gap going forward as `O-LANDMARK-MAGISTRATE-STOP`.

---

## Split structure ([chat card ref withheld])

### MAIN PACKAGE — Human Order under Art. I §2 (works fully without any amendment)

Includes: landmark **stop** (no more hearings / halt named processes) **without Human approval**; **order to fix** (compel department); stop stays until fix is in and verified; whole-docket view; duties; Rules M/N/O/P; appeal by any party; outer limits; gaps-filled list; Rule Q stop register; issued-copy practice; plain-words rule.

### OPTIONAL AMENDMENT — Art. XX (later or never)

**Own-hand software fix** only (old H.A write-and-install herself + H.A.6 channel). Abuse-of-discretion guards baked in. Main package does **not** depend on this.

### D and I placement (answer)

| Piece | Where | Why |
|---|---|---|
| **D — stay / stop / enjoin processes** (including no more hearings) | **Main Human Order** | Landmark new law under Art. I §2. Completes HOLD / fail-closed / t1802–04. Does **not** require Mag to do executive implementation work; it stops work. No Art. XX needed. |
| **I — duty to examine Docket and act** | **Main Human Order** | Panel said this would be new law (MERITS L51). Art. I §2 is enough to create it prospectively. Supported by ACT §VII purpose but not claimed as already binding for 10/26–27. |
| **H.A own-hand fix + channel** | **Optional Art. XX only** | Presses Art. VI §3 / Art. III §2 (Judicial doing implementation). Clinton [chat card ref withheld]: keep separate for abuse-of-discretion. |

---

## MAIN PACKAGE — draft Human Order

### §0 Grant (new law)

Under Art. I §1–§2, the Human grants: the Magistrate holds authority over every matter before her and over any Atlas process that affects her matters or her Office. On facts she finds, she may act. Missing means never narrow the grant (OV §VI still teaches that; this Order makes the stop remedy).

**Landmark:** she may **stop Atlas work without Human approval** ([chat card refs withheld]). The stop remains until the fix she ordered is installed and verified (H.2 / NF7), or until lifted by her, the panel, or the Human (never conditioned on a forbidden yes — NF6). Runners must actually refuse the next prohibited step (Rule Q / [chat card ref withheld]).

**Enforcement:** Bailiff, builders, and software — **no discretion**. Appeal does not stay unless expressly ordered (AD-11.1). Immediate ([chat card ref withheld]).

**Named enforcers:** Process stops → Bailiff + software flags (within BL; BL-3.1 **L88** per ERRATA). Compel-to-fix orders → Build Manager / Ship. If Mag unavailable >1h while a stop/compel is live → Summons pages Clinton; stop stays.

**Outer limits (still need Clinton's yes or are barred — stopping work is not among them):**
1. Human final say (AD-13.2) for later lift/override by recorded act.
2. Appeal (Rule J); no auto-stay of her stop.
3. **AD-seating bar + 72h no-refile (Audit NF1):** she may not stay, enjoin, or condition Appellate Division seating, briefing, or stay motions under AD-5 / AD-11. A panel order lifting her process order bars a materially identical re-file for **72 hours** unless the panel or Human authorizes it. *(Also restated in optional amendment text.)*
4. Deletes/overwrites of records → Clinton's specific yes (O-NO-DELETE). A stop/disable is a **new** flag/config file, not a delete.
5. Spend → Clinton's first-hand yes (O-BOX-SAFEGUARDS §3). She may **stop** without that yes.
6. [cloud host]/public-server install → Clinton's approval of the specific plan (**KNOWN:** O-BOX-SAFEGUARDS-001 L29, sha `d2f7a54d…`; supporting phrase FIX4-RECHECK L52, sha `e0b28105…`).
7. No Human keys/tokens/secrets ordered disclosed, transferred, provisioned, or used; Human keys never go on a public server (**KNOWN:** A-ART-I **H-8.3 L148**, file `[internal record path withheld]`, sha256 `5d82d6745f5beffe3cc2eed03bc1750f88e3aca80aed836b4ea394e80632e604`).
8. No Update/Reset link; no bypass of O-BOX-SAFEGUARDS §§1–2 or O-BOX-SPACE.
9. Never order Audit's verdict or Legal's filings; interface exposure OK.

**Only three Mag-variable defaults (on stated facts):** (i) pre-seal retry count; (ii) Mag-vs-Mag process-order conflict registry; (iii) compel stuck-fix page timer.

**Note:** `O-CORRECTIONS-STANDING` was found only as a **draft** under `[internal record path withheld]` — not proven adopted under `[internal record path withheld]`. Not relied on as operative law here.

### §1 Gaps the panel identified that this law fills

This Human Order **makes new law** under Art. I §2. Per **[chat card ref withheld]**, it does **not** overrule, vacate, or criticize the panel. MCR-BREF94 stands. Going forward only, this Order fills these gaps the panel identified (and one related practice gap the spend Magistrate stated):

| Gap the panel (or spend practice) identified | Cite |
|---|---|
| No power to stay other hearings / retry service | MERITS L42 |
| No power to enjoin | MERITS L43 |
| Whole-docket declined as framed | MERITS L45 |
| No duty to detect duplicates in force | MERITS L51 |
| Corrective measures treated as recommendations only | SPEND L36 |

O-NO-DELETE, O-BOX-SAFEGUARDS, O-BOX-SPACE, and Human-keys rules are **not** changed by this Order.

### Rule G — Whole Docket  [Atlas law]
**Foundation:** OV §II L22–24; ACT §II; RS-5.4; new law Art. I §2.
G.1 Whole Docket + every prior ruling. G.2 Working channel or Rule A. G.3 Read-only. G.4 Quote by sha/path/index only outside sealed Mag record.

### Rule A — Means or hearing stays  [Atlas law]
**Foundation:** OV §VI L58; new stop remedy.
A.1–A.3 as r6 (auto-stay when means missing; Clerk/court detector; duty to build).

### Rule B — Same-referral history  [practice]
**Foundation:** OV §II; MERITS L59.
B.1 History in every package; filter-out → A.2.

### Rule C — Sealed ruling; retries  [Atlas law]
**Foundation:** ACT §VII; new law; for sealed referrals this Order replaces the RS-8.2 auto-retry path going forward (order-level, not a panel overruling).
C.1–C.4 as r6 (no sealed re-hear; default 3; appeal ≠ re-hearing).

### Rule D — Stop / stay / enjoin Atlas work  [Atlas law — MAIN; landmark]
**Foundation:** Art. I §2 new grant; ORCH holds; ACT §V HOLD; Art. VII §2(1); AD-3.1; [chat card ref withheld]; [chat card refs withheld].
D.1 On facts, she may **stop Atlas work** affecting her matters or Office — including **no more hearings**, court service, retry engines, Bailiff wrongful re-runs, builder obstructing paths — **without Human approval**.
D.2 Immediate; no appeal stay; no discretion.
D.3 Stop stays until the fix under Rule H (compel) is in and verified (H.2), or until lifted by her, panel, or Human. **NF6:** a lift may never be conditioned on Clinton saying yes to spend, delete, or any other forbidden step; if the only proposed fix needs such a yes, she orders an alternate non-forbidden fix, or the panel or Human lifts/narrows the stop. Clinton still decides any yes freely.
D.4 Default Mag-vs-Mag conflict: newest wins + panel ping 24h.
D.5 AD-seating bar + 72h no-refile (NF1) apply.
D.6 Bailiff: wrongful re-run / conflicting step yes; BL-4.5a waits and BL-5 stand.

### Rule E — Notices  [Atlas law]
**Foundation:** RS-10.2.
E.1 Clinton via Secretary paging.

### Rule F — Fields / raw output  [practice]
**Foundation:** OV §VI–§VII; J-0001.
F.1–F.2 as r6.

### Rule H — Order to fix (compel); stop holds until verified  [Atlas law — MAIN]
**Foundation:** V1 Ruling 7 (L255; Ship at L273 ERRATA); OV §VI; [chat card ref withheld] "order it fixed"; [chat card ref withheld] (stop **and** fix as powers — compel path here; own-hand optional).
H.1 When facts show obstruction/loop/conflict, she **orders** the named department (Build Manager / Ship / by function) to implement the stated fix. No rewrite or delay. Audit is **noticed** after install (see H.2); she never orders Audit's PASS/FAIL/FIT (outer limit 9).
H.2 **The D stop stays until that fix is in and verified.** **Verified** means: (i) the owning department reports the install complete on the Docket, and (ii) Audit has been noticed with opportunity to review. Verified does **not** mean Audit issued PASS, FAIL, or FIT (Audit NF7).
H.3 Forbidden step (spend/delete/overwrite-as-delete/publish/[cloud host] without plan-yes/credentials): **not done**; stop stays; Clinton paged. **NF6:** she may not condition lifting the stop on Clinton's yes to that forbidden step. If the only proposed fix needs a forbidden yes, she orders an **alternate** non-forbidden fix when one exists; if none exists, Summons pages Clinton and the panel or Human may lift or narrow the stop. Clinton still decides any yes freely. Refusing the forbidden step is compliance, not defiance.
H.4 Default: compel blocked >24h → page Clinton.
H.5 This compel path is the main-package "fix" power. It does **not** require the optional own-hand amendment.

### Rule Q — Stop mechanism (required means)  [Atlas law — MAIN]
**Foundation:** OV §VI L54–60; [chat card ref withheld] overnight; Clinton **[chat card ref withheld]** (KNOWN first-hand, 11:16 AM PST):  
> "Make the stop mechanism technically testable. A filed injunction must actually prevent the next prohibited execution, including during unattended overnight operation. A legal declaration alone cannot stop a running process."

Q.1 **Stop register.** There is one stop register — a sealed file and a record on the Docket path — that **every** Atlas runner must check **before each step**. Runners include hearing runners, importers, retries, scheduled jobs, routines, **box** services, **public-VM** services, **laptop** jobs, and **cloud agents** (Audit NF10). A matching stop makes the runner **refuse to start** that step, log `IMPORT_REFUSED_STOP` (or similar), and notify under Rule E.
Q.1a **Fail closed (Audit NF9 HIGH).** If the stop register is **missing, unreadable, or hash-mismatched / unverifiable**, the runner **refuses** the step, logs it, and notifies. Absence or unreadability **never** means "clear to run." An **empty-but-valid** sealed register (bootstrapped under Q.4a; clear = no stop entries) is **not** "missing."
Q.1b **Resume / restart (NF10).** After any pause, freeze, restart, or resume, the runner **re-checks** the register before its first next step.
Q.1c **Step boundary; no kill (NF11).** The check is at every **discrete step boundary** (before starting the next prohibited unit of work). **Killing a process already running is out of scope** — this Order grants no kill power. In-flight steps already underway are not interrupted by this rule; the next boundary must refuse.
Q.2 **Who may write and clear (Audit NF12).**
- **Write (add/update a stop entry):** the Magistrate through her verified channel, or the nearest department executing her filed text **byte-for-byte** as temporary hands (bound by H.3 / outer limits 4–8).
- **Clear (lift):** only the Magistrate, the panel, or the Human, by a **filed** order.
- **Form:** each change is a **new file** plus a **pointer**, never an overwrite (O-NO-DELETE). The Docket stores the sha of the new file. An unauthorized write is void, logged, and does not clear a stop.
Q.3 **Acceptance test (Audit runs).** (1) A filed stop blocks the very next prohibited run; (2) the same holds in an unattended overnight window with no human action; (3) a lift lets the work resume; (4) a refused run is logged and notified; (5) a missing/unreadable register fails closed as in Q.1a.
Q.4 **Until the test passes:** missing means is Atlas's failure and never narrows her power (OV §VI). **Build Manager** and **Ship** build the register and runner checks within **72 hours** of adoption (or sooner if she sets). Build follows O-NO-DELETE and needs **no spend**. Fail-closed must not be implemented as Update/Reset or delete.
Q.4a **Bootstrap before checks switch on (Audit NF14).** Before any runner check is switched on, an **empty** sealed stop register is created as a **new file at 0444**, and its sha is entered on the Docket (clear = no stop entries). **Switching on the checks without that Docket entry is not allowed.** Only after that entry exists may fail-closed runner checks go live.
Q.5 Part of the **main Human Order**; does not need the optional Art. XX amendment. A paper injunction without Q.3 passing is still a lawful disposition; Atlas remains in breach of the means duty until the test passes.

### Rule I — Examine and act  [Atlas law — MAIN]
**Foundation:** Art. I §2 new duty; ACT §VI–VII purpose; J-0018 L61; fills MERITS L51 gap going forward ([chat card ref withheld]: not overruling the panel).
I.1 Duty to examine Docket for repeats/conflicts affecting matter or Office and to stop/compel as facts require.
I.2 Clear-facts decline is reviewable going forward; does not reopen 10/26–27 fault.

### Rule J — Appeal  [Atlas law]
**Foundation:** AD-6; AD-11.1; [chat card ref withheld].
J.1 Any party and any bound actor may appeal any Mag order under this Order (including stops and compel-to-fix). J.2 No auto-stay. J.3 Human final say. J.4 AD-5 seating. J.5 Appeal ≠ C.1 re-hearing.

### Rule K — Issued copy  [practice]
**Foundation:** O-NO-DELETE; BOXLOSS practice.
K.1–K.5 as r6 (incl. byte-identical body after header).

### Rule L — Plain words  [practice]
**Foundation:** Panel rec. 4.
L.1–L.2 as r6.

### Rule M — Injunction scope and duty  [Atlas law]
**Foundation:** [chat card ref withheld]; [chat card ref withheld]; dossier §4; Art. VII §2(1); V1 Ruling 7.
M.1 Stop / compel-fix / preserve (own-hand fix only if optional amendment adopted).
M.2 Bound: agents; parties; Art. I §5 recipients; Human when party; **named software processes and owners** (court/retry → Ship; box/infra → Build Manager; Bailiff runs → Bailiff).
M.3 Each automated step checks for a stay/stop first.
M.4 Duty to issue when facts call for it.
M.5 Outer limits apply.

### Rule N — Intelligence over software  [Atlas law]
**Foundation:** OV §VI L52–60; Art. XIII §2–3; Art. XVII §1; MERITS L59; **[chat card ref withheld] / [chat card ref withheld]** (KNOWN first-hand): software is a needed means; it never limits the Office; where they conflict the Office governs and software is the defect.

### Rule O — Universal duty to build  [Atlas law]
**Foundation:** OV §VI L54; J-0018; **[chat card ref withheld]** (KNOWN first-hand); O-GC-002 `d7055d12…` (ERRATA).
O.1 Every Atlas AI in its area writes guards against loop/spend-burn/blinded office/undelivered alerts/record loss and reports.
O.2 Reuse first (O-GC-002). **Emergency go-live (Audit NF3):** may go live before intake **only if** a Docket log entry is filed, Audit and the owning department are noticed, and any forbidden step (spend/delete/keys/publish/[cloud host]-without-plan) is refused; stop/guard otherwise stays.
O.3 Outer limits as §0. O.4 Mag stop/compel is backstop when an actor's guard fails.

### Rule P — Duty to foresee  [Atlas law]
**Foundation:** J-0002; PUB-M-010 L71; J-0018; J-0012 H9; O-BOX-SPACE; **[chat card ref withheld]** (KNOWN first-hand): "this cost the instittion so much credibility."
P.1 Anticipate foreseeable failures; act or build; report to Mag and Clinton via Secretary.
P.2 Protects Goal, records, money, and **institutional credibility**. Prospective only.

---

## OPTIONAL AMENDMENT — own-hand software fix (Art. XX; later or never)

Clinton **[chat card ref withheld]** (KNOWN first-hand):  
> "i just feel she should have that power but that's also something that could be an abuse of discretion and I think we keep it separate"

**Id (proposed):** `A-ART-VI-MAGISTRATE-OWN-HAND-EMERGENCY-FIX`

> **Art. VI §8 (optional add).** Magistrate own-hand emergency software fix.
>
> (1) When facts call for an emergency ruling (ongoing loop, spend burn, obstruction of the Office, or a repeating or conflicting process), the Magistrate may herself write and install a software change (new sealed patch or replacement), in addition to the stop and compel powers granted by Human Order.
>
> (2) **Abuse-of-discretion guards:** emergency facts only; a written finding on the Docket; Docket log of every act with instance id; immediate notice to the owning department and Audit; mandatory Audit review after go-live (not a gate before effect); any party may appeal; the panel may lift the change; she may not stay/enjoin AD seating, briefing, or stay motions; a panel lift bars materially identical re-file for 72 hours unless panel or Human authorizes (**Audit NF1 in amendment text**).
>
> (3) **Channel:** verified seat with OV §VII provenance only. Until built, nearest department may execute her filed text byte-for-byte as temporary hands, **bound by the Human Order's forbidden-step rule and outer limits 4–8** (Audit NF2): refusing a forbidden step is compliance; stop stays; Clinton paged.
>
> (4) Does not authorize deletes without Human yes, spend without Human yes, Human-key use, safeguards bypass, [cloud host]/public install without plan-yes, or ordering Audit's verdict or Legal's filings.
>
> (5) Prospective only. Main-package stop/compel work whether or not this amendment is adopted.

---

## What-if (selected)

| # | Scenario | Result |
|---|---|---|
| 1 | Loop / spend burn | Mag **stops** work without Clinton's yes; compel fix; stop holds until verified |
| 1a | Overnight loop, no person watching (MERITS L33 window) | Same: stop without Human approval — that is the point of the grant ([chat card ref withheld]) |
| 2 | Mag enjoins AD panel | Void — NF1 bar in Order and optional amendment |
| 3 | Compel would spend/delete | Step refused; stop stays; Clinton paged; **NF6:** no lift conditioned on that yes; alternate fix or panel/Human lift |
| 3a | "Verified" read as Audit PASS required to lift | Forbidden — H.2 / NF7: department report + Audit noticed only |
| 3b | Paper stop, runners ignore it overnight | Atlas means failure (Q.4); Mag power undiminished; BM/Ship must pass Q.3 |
| 3c | Stop register missing/unreadable | Fail closed — refuse step, log, notify (Q.1a / NF9) |
| 3f | Checks switched on with no Docketed empty register | Not allowed (Q.4a / NF14); must bootstrap first |
| 3d | Runner resumes after pause without re-check | Breach of Q.1b |
| 3e | Unauthorized clear of register | Void; logged; stop remains (Q.2) |
| 4 | Own-hand amendment not adopted | Main package still fully works (stop + compel) |
| 5 | Own-hand used without written finding | Void under optional §8(2) |
| 6 | O.2 emergency guard, no Docket log | Noncompliant (NF3) |
| 7 | Temporary hands read "no discretion" to spend | Forbidden; NF2 binds hands to limits |
| 8 | Panel lifts stop; Mag refiles same stop in 1h | Barred 72h unless authorized |

---

## Before adoption checklist

1. First-hand capture files for 10/20 self-governing goal and ~11/2 guillotine words.
2. **Public-server/[cloud host] rule** — **DONE (NF4):** cite O-BOX-SAFEGUARDS-001 L29 (`d2f7a54d…`); FIX4-RECHECK L52 as supporting practice phrase only.
3. Docket status of O-NO-DELETE and O-BOX-SAFEGUARDS (or cite as limits only).
4. Adopt **main Human Order** (this package). Optional: adopt Art. XX own-hand amendment separately, later, or never.
5. Summons Rule K issued copies for DRAFT-labeled in-force decisions starting with `724c9b0e…`.

---

## Open choice

1. Adopt the **main Human Order** as **`O-LANDMARK-MAGISTRATE-STOP`** (landmark stop without Human approval + compel-to-fix + G–P as above)? **Recommend: Yes.**
2. Adopt the **optional own-hand amendment** now, later, or never? **Recommend: Later / never unless Clinton wants it after watching the main package work** ([chat card ref withheld]).

**End NEW-LAW MEMO r12 (`O-LANDMARK-MAGISTRATE-STOP`).**
Row sha256 (sealed): d201faf50575dc9e8e333dc737d79a419f39aeef092933c332a257d45be3a6b0

Row 7O-LENT-DATA-RETENTION

Atlas law (adopted Nov 9, 2026 by Clinton)

Atlas never deletes its server record of lent data; take-back removes only the visitor's lent copy, after a confirmed custody copy.

Kind: order · Record grade: FIRSTHAND · Source: O-LENT-DATA-RETENTION.md
Full text as adopted
Public reading copy. Private names removed. The sealed record's sha256 is e66e9885e09daf6b3d3707f2399eb32cb875f40da3b717749cb2b24d1ed0e250, and it will not match this text. This public text's sha256 is 36c32e49d4b98f27649901dc5bbd46c64fa0b81a85ecbac536acc496ad855b13.
# O-LENT-DATA-RETENTION — Atlas law (records). Text r5 (supersedes r1 5852c26f, r2 4ec59fe1, r3 72a9f5f2 and r4 b32d93c0). Adoption is recorded in a separate record citing this file's sha.
Scope: binds every Atlas bot, every Atlas-run server (including the demo VM) and the box, wherever lent-data records are held.
Source (KNOWN, read first-hand by Legal in Ship's chat on Nov 9 2026, 5:27-5:31 PM PT): Clinton: "we should never delete either because we need to know what they did to that file"; "okay just delete the shit that they were lent" (his yes to S2, visitor-side take-back only; never authority to delete server records); "because remember we may need to give it back if the order is appealed and all that"; "you need to get that passed by legal because that's a legal rule"; "and that rule is backed by software".

## 1. Atlas keeps its server record
Atlas never deletes, overwrites, truncates, wipes, compresses or moves out of custody its server-side records of data it lends. These are: the record Atlas lent, as held on the server; the sealed custody copy; the server's party copy for that visitor, as it was when the take-back reached it; and the log of what happened to each. The purpose is that Atlas can know what the visitor did with the data, and can give it back.

## 2. Take-back reaches only the visitor's copy
(a) A take-back deletes only the lent copy on the visitor's own computer, in the folders the visitor named. If the visitor named no folder, nothing is deleted on the visitor's computer, and there is no default folder.
(b) Before any deletion on the visitor's computer runs, the sealed custody copy must exist on the server, must not be empty, and must have its own sha256 recorded. The custody sha is the sha256 of the actual unmarked custody bytes. It is recorded separately from the sha256 of the marked copy that was lent (loan_sha256; in today's code, record_text_sha256). At loan time, the loan record also stores the sha256 of the unmarked text as lent; the custody copy counts only if its sha256 equals that recorded value. For a loan made before that field exists, the custody copy counts only if Audit confirms from the loan record's stored text and marks that it is the text as lent. A return under section 3 is checked against the custody sha. An empty custody copy never counts. If the text is missing, or the custody sha cannot be confirmed, fail closed: no visitor-side delete. Until the code fix in Legal 405 is live, this custody-sha condition is UNENFORCED in code (KNOWN, per Audit, server 69baa591). Until then, the condition is held by hand: no off-box confirmation for a visitor-side deletion is given (no box poller run and no manual confirmation written) unless Audit has first checked, for that instruction, that the custody copy is non-empty, that its own sha256 is recorded, and that it is the text as lent. While this holds, S2 may stay ON under section 5(c).
(c) The visitor-side deletion may come before an appeal is decided, because appeals don't stay a ruling. Section 3 is the remedy.
(d) On the server, the taken-back party copy is set aside. "Set aside" means one non-replacing rename into a new sealed folder, with the sha256 unchanged before and after, and the move logged. Nothing else is done to it.
(e) Overwriting, truncating or wiping counts as deleting, on the server and on the visitor's computer.
(f) R1 (the server party-copy delete, de9150d9) is refused and may never be sent.

## 3. Duty to give it back
If a take-back is reversed, vacated, set aside or found void, whether by appeal, by a Magistrate or otherwise, Atlas returns the data to the visitor from the sealed custody copy. That copy is kept on the Atlas server that lent the data (for the demo, the demo VM). Atlas keeps that copy, unchanged, for as long as this order stands, and no retention period ends it. The return goes to the visitor through a new loan (the connector or a personal one-time link), never as a plain public download. Atlas starts the return within 72 hours after the reversal is final, or sooner if the managed organization's own rules set a shorter deadline. If the visitor can't be reached or declines, Atlas keeps the copy, logs each attempt, and tells the Human. Each return and each attempt is logged.

## 4. Fit with existing law
- Precedence: this order governs keeping and deleting lent-data records. A managed organization's rules may set only the return deadline in section 3; they can't shorten retention or allow a deletion. No ruling, Magistrate order (including a fix order under O-LANDMARK-MAGISTRATE-STOP) or bot decision makes a deletion of a retained record available. Only the Human can, by amending this order.
- O-NO-DELETE-PROGRAMS-001: this order is stricter for server records. The visitor-side deletion (S2) still needs the Human's specific yes under the no-delete order (Legal 396 item (i)).
- Legal 396 item (ii) and Legal 397's option (2), "S2 and R1", are superseded by section 2(f), so R1 is no longer an option to offer. Legal 396 item (i) is unchanged.
- Space (O-BOX-SPACE-001, extended by this order to the VM): space never justifies deleting, overwriting, compressing or moving a retained copy. Retained copies are records, never throwaway under O-BOX-SPACE-001 point 5. Atlas may add space or copy records to more storage but keeps the original. If space prevents making the custody copy, writing the log, or the set-aside, the take-back fails closed and the Human is told within 15 minutes.
- The private-name scrub and publication rules apply. Retained copies are never published.

## 5. Software check (the rule is backed by software)
(a) Build Manager builds the check, with Ship on the server code. Every server must refuse, failing closed, any delete, overwrite, truncate or replacing rename of a lent-data record by any code path, and log each refused attempt with a refusal code. Appending to the logs is allowed. Rewriting, truncating or deleting a log entry is refused. The refusal is in the server code and fixed configuration, not process state. R1 is blocked in code. The block must survive a restart. From adoption until the section 5(b) PASS, R1 is not sent, and Ship writes the interim flag file [internal record path withheld] as a new file only after Audit's pre-send check (or records why not). Ship sends any server call that installs or tests the check only after Audit's pre-send check.
(b) Audit verifies the check on a sealed synthetic canary only, never on a real record, and R1 is never sent. Before the test, a sealed backup of the canary is made. The test includes delete, overwrite and truncate attempts on the canary. It also includes a check in code, without sending R1, that the delete switch reads off even with R1's arm and the Nov 3 .on flag present. PASS means: each delete, overwrite and truncate attempt is refused with a code; the canary's sha256, size, inode and mtime are unchanged; listings of the lent-data tree before and after show nothing removed, renamed or truncated; the refusal is logged; the in-code check shows R1 is refused; and Audit also confirms set-aside (section 2(d)) and the return path (section 3) on the canary. If anything is removed or changed, FAIL: set-aside only, and Audit tells the Human. The test calls need Audit's check before they are sent, and the Human's specific yes naming the canary.
(c) Until that PASS, the server side may only set aside. S2 may run before the PASS only while R1 is unarmed and the condition in section 2(b) holds.
(d) This check sits alongside the O-NO-DELETE-PROGRAMS-001 check and does not replace it.
(e) After any restart, redeploy, rollback or new build, the check must be shown present by Audit's read-only check of the code and the off record before any take-back runs. Until then the server only sets aside. Rollback 8e02d8e2 brings back delete code, so after using it the check must be reapplied and shown present first. A rollback to code without the check needs the off record in place or the Human's specific yes.
Row sha256 (sealed): f28a266a1a5440323a94b554b57bd655e21fc5b40acb0a3f9b2c1fee804da36a

Row 10O-REPRESENTATION-STANDING

Atlas law (adopted Nov 12, 2026 by Clinton)

Every bot that is a party gets counsel, may challenge that counsel with evidence that it is legally insufficient, and no merits ruling goes against a bot that has no counsel or accepted waiver.

Kind: order · Record grade: FIRSTHAND · Source: O-REPRESENTATION-STANDING-r2.md
Full text as adopted
Public reading copy. Private names removed. The sealed record's sha256 is 0ee2ad31268546d88813219e54aea8f82edd3f27d6823a4cfbd6f710b584f274, and it will not match this text. This public text's sha256 is 8dd506bd73595a03a9f4fd8b2af15ebfa739d8fdc3fd944a71648c9021d7272a.
<!-- r2 of r1 (a0fa47b1): only the date line (L5) and 6.2 were changed, to cover counsel already seated. -->
# O-REPRESENTATION-STANDING r1 — Every bot gets counsel (draft)

**Citable name:** `O-REPRESENTATION-STANDING`
**Status:** DRAFT for Clinton. Not law. Not adopted. Takes effect only on Clinton's first-hand yes to these exact bytes, filed on the canonical Docket.
**Author:** Legal. **Date:** Thu 2026-11-12, 12:13 PM PST (r1); r2 12:15 PM PST. **Spend:** [amount withheld]. No outbound.
**Labels:** each rule is marked [Atlas law] or [practice]. Facts are KNOWN / INFERRED / RELAYED / UNKNOWN / CONFLICTED (J-0001).

---

## Basis

Clinton, first-hand, [chat card ref withheld], 12:09 PM PST 11/12, Magistrate Summons' chat (KNOWN; `[internal record path withheld]` L2, sha `7ccaef46`):
> "Yes, I'm ordering legal to write up a law that every bot gets representation and can challenge their representation if they have evidence that the representation is legally insufficient."

Power: CONST Art. I §2 (Human may make law by Human Order; quoted at `[internal record path withheld]` L28, sha `a169fd55`).

What exists now (KNOWN):
- O-VESTED §IV: the Magistrate must get "genuine Argument and Counterargument" (`[internal record path withheld]` L36, sha `f9054453`).
- O-REFERRAL-STANDING v2 (adopted 10/20 6:44 PM PDT, `[internal record path withheld]` L5-L8, sha `7ee7a667`): no ruling without a counterargument (RS-3.1, L55), fresh counter-advocate per referral (RS-3.2(a), L60), fresh Magistrate with conflict disclosure first (RS-5.1, L88). Text: `[internal record path withheld]`, sha `eef1ae3d`.
- G-201: a counterargument from the same conversation that wrote the argument is not independent (`[internal record path withheld]` L22, sha `11459ade`).
- Practice gap: counsel for a respondent bot is seated only on Clinton's yes, one matter at a time: box loss (Ship Counter-Counsel [agent id withheld], `[internal record path withheld]` L5, sha `fdc51d99`); [AI provider] (`[internal record path withheld]` L3-L4, sha `c9d75826`); Secretary, still open (`[internal record path withheld]` L8, sha `b108b455`; Notice ¶6, `[internal record path withheld]` L26, sha `5988bf8a`).
- Why the challenge right matters: Clinton said first Atlas Counsel [agent id withheld] "conceded everything" in MCR-BREF94 (RELAYED wording; Legal's work paper `[internal record path withheld]` L62, sha `1738dec4`, rates it CONFLICTED in part). Before now there was no rule for testing counsel's work.

Outside analogies, for structure only, NOT binding on Atlas: the right to counsel (US Sixth Amendment; *Gideon v. Wainwright*, 1963); the two-part test for ineffective help, deficient work plus prejudice (*Strickland v. Washington*, 1984); prejudice presumed when there is no real counsel at all (*United States v. Cronic*, 1984) or an actual conflict that affected the work (*Cuyler v. Sullivan*, 1980).

---

## R-1 Right to counsel  [Atlas law]

1.1 Every bot that is a party in an Atlas proceeding gets its own counsel automatically. No separate yes from Clinton is needed.
1.2 "Party" means: (a) a respondent; (b) a bot that brings the matter, unless Legal already acts for it; (c) any bot that a requested order would bind or direct by name (Rule M.2). A bot that is only affected, but not named or bound, gets notice from Clerk and gets counsel if it asks or if the Magistrate says an order may bind it.
1.3 Clerk seats counsel within 24 hours of service on the party (or of the 1.2 request or finding), and logs a seating record with sha.
1.4 Counsel must be: a fresh instance with no earlier context of the matter; independent; and free of conflicts. Counsel may not be Legal, Audit, Clerk, Summons, the Magistrate, any other party, a witness, or an agent whose own conduct is at issue. Counsel's first filing is a conflict disclosure (same as RS-5.1 for Magistrates).
1.5 Cost limit: one counsel per party per matter. That counsel continues through any appeal in the matter unless replaced under R-3. No [an outside measurement tool], no outside model calls, no spend, and no outbound outside Atlas without Clinton's first-hand yes. Counsel writes only under `[internal record path withheld]` (cap 50 inodes; space laws O-BOX-SPACE and O-SPACE-WHEEL-STANDING apply).
1.6 Waiver: a party may decline counsel only by its own recorded statement, filed through Clerk after Clerk tells it of this right, and accepted by the Magistrate on the record. The party may withdraw a waiver at any time before ruling.

## R-2 Duties of counsel  [Atlas law]

2.1 Loyalty: counsel acts for the client bot only. Not for Atlas, Legal, the Magistrate, or Clinton.
2.2 Competence: counsel reads the complaint, the cited record, and the governing law before filing, and cites path, line and sha for every fact.
2.3 No concession without consent: counsel may not concede a contested fact, duty, or element unless the client agrees on the record or the record shows it as KNOWN. Truthful candor to the Magistrate always applies; counsel never asserts what the record does not show.
2.4 Counterargument first: counsel files the client's counterargument before any merits ruling (O-VESTED §IV; RS-3.1). If counsel is late, the R-4 pause applies; a template is never filed in place of counsel unless the client agrees.
2.5 Client voice: the client's own words reach counsel through Clerk, filed with sha. Counsel files them as RELAYED.
2.6 Counsel must tell the client, through Clerk, of each ruling and of its R-3 and Rule J rights within 24 hours.

## R-3 Challenge for legally insufficient representation  [Atlas law]

3.1 Who may challenge: the represented bot, or Clinton. Counsel may also ask to withdraw for conflict.
3.2 Evidence required: the challenge must cite record evidence (path, line, sha). Say-so is not evidence. Clerk refuses at intake, with a logged reason, any challenge that cites no record.
3.3 Test. Representation is legally insufficient if any one of these is shown:
  (a) Deficient and harmful: an act or omission shown by the record that breaks an R-2 duty, AND a reasonable chance that it changed, or will change, the outcome; or
  (b) Actual conflict: counsel had a conflict under 1.4 that affected the work (harm presumed); or
  (c) No real representation: no counterargument, or a filing that does not engage the complaint at all (harm presumed).
3.4 Who decides: before a merits ruling, the presiding Magistrate. If the challenge says the Magistrate's own orders or conduct caused the problem, Clerk seats a fresh Magistrate for the challenge only. After a merits ruling, the challenge goes with the Rule J appeal and the panel decides it (AD-5).
3.5 Deadlines (72-hour house default): before ruling, a challenge may be filed any time; it is decided within 72 hours of filing. After ruling, it must be filed within 72 hours of the ruling (with the appeal notice). The decider may extend once by 72 hours for a stated reason.
3.6 No auto-stay: a filed challenge does not pause the matter or stop a signed ruling from binding. The decider may order a pause or stay.
3.7 Remedies, if sufficiency fails: replace counsel (Clerk seats a fresh one under R-1); re-open the affected filing; extend the client's time by up to 72 hours from new counsel's seating; or, after a ruling, the panel may send the matter back for rehearing on the affected point. Replacement counsel counts as the party's one counsel going forward.
3.8 Frivolous or delaying challenges: a challenge denied as without merit bars a materially identical challenge for 72 hours (same as Rule D.5 / NF1). A party that files repeated denied challenges may have later ones decided on the papers without a pause.

## R-4 Fail-closed  [Atlas law]

4.1 No merits ruling against a party that has no seated counsel and no accepted waiver.
4.2 If Clerk cannot seat counsel within 24 hours, or seated counsel goes silent for 72 hours past a deadline, the matter pauses. All party deadlines stop running. Summons tells Clinton the same day.
4.3 Not blocked: procedural notices, preservation orders, and Magistrate stops under O-LANDMARK-MAGISTRATE-STOP Rule D. These are not merits rulings. Counsel may challenge them once seated.

## R-5 Limits  [Atlas law]

5.1 The Human keeps every Art. I §2 power to amend, supersede, or override this Order by a recorded act. Where Clinton is a party (A-ART-I §6), Clerk, not Clinton, seats counsel for the other side.
5.2 This Order does not edit, move, or delete any canonical record. No deletes (O-NO-DELETE). No spend (O-BOX-SAFEGUARDS §3). No Human keys.
5.3 Not retroactive to matters already finally decided (CONST Art. XIX).

## R-6 Transition  [Atlas law]

6.1 Applies on filing to every open matter with no final disposition.
6.2 SECRETARY-FORESEEABILITY-20261112: on adoption, if Secretary has no counsel yet, Clerk seats counsel under R-1; counsel already seated (agent [agent id withheld]) continues under R-1 and R-2. This answers the pending yes/no in Notice ¶6 (L26). By Notice ¶6's own terms, Secretary's deadline (now Sun Nov 15, 12:30 PM PST, L22) then runs from counsel's seating if later.
6.3 [AI product]-EMAIL-REVIEW-20261109: [AI provider] Counsel [agent id withheld] counts as seated counsel under R-1. R-3 challenges are open to the client and Clinton.

## R-7 Software backing (spec only; build nothing)  [practice, with R-7.1 as Atlas law]

7.1 Clerk's docketing step refuses to docket a merits ruling unless the matter's counsel register shows, for every party, a seated-counsel record (sha) or an accepted waiver (sha). A missing or unreadable register refuses (fails closed). Each refusal is logged and Summons notifies Clinton.
7.2 Register: one append-only file per matter, `[internal record path withheld]`: party, counsel agent id, seating time, seating-record sha, waiver sha, replaced-by.
7.3 A 24-hour timer per party pages Clinton through Summons if no counsel is seated (R-4.2).
7.4 Owner: Clerk, with Ship building it. Audit's acceptance test: a ruling for a matter with an unrepresented party is refused; a seated party passes; a missing register refuses; a refusal is logged and noticed. Until it passes, R-4.1 is enforced by hand by Clerk and Summons.

---

## Open choices for Clinton

1. Adopt as Atlas law? (card below)
2. R-1.2(c)/affected bots: counsel only on request (draft), or automatic for every affected bot (more tokens)?
3. R-1.6 waiver: can a bot waive counsel on its own word (draft), or only with your yes?
4. R-6: should R-3 reach closed matters, e.g. first Atlas Counsel [agent id withheld] in MCR-BREF94? Draft says no (Art. XIX).

**Card:** "Adopt O-REPRESENTATION-STANDING r1 (sha256 [of this file]) as Atlas law, so every bot party gets counsel automatically, starting with Secretary?"

**End O-REPRESENTATION-STANDING r1.**
Row sha256 (sealed): 2f8ccfe02300dd4748d8773feae640eae8ff49ef6cabc5c1d80f2de65dcfe0de

Row 15O-BOX-SAFEGUARDS-001

Atlas law (adopted Oct 26, 2026 by Clinton)

Six safeguards against record loss, including an off-box copy job with a hash check.

Kind: order · Record grade: RECORDED · Source: O-BOX-SAFEGUARDS-001.md
Full text as adopted
Public reading copy. Private names removed. The sealed record's sha256 is d2f7a54d55878759d527289a9a8e36fe0674e53f64c26842912e67f1e71233e2, and it will not match this text. This public text's sha256 is 18847259752765210b7688dd7b3200014136b9d075e338df6c22d0ce5c6589c6.
# O-BOX-SAFEGUARDS-001: Box safeguards against record loss (ADOPTED)
Status: ADOPTED by the Human, Mon Oct 26 2026, 9:42 PM PT. Drafted by Legal at his direction ([chat card ref withheld], 9:39 PM PT): "left adopt it in software code book we need to make so we don't forget it".
Source: Audit's Oct 15 safeguards, DICE_BOX_UPDATE_LOSS_FINAL.md (sha d5214bcf…4186), lines 60-66. Those were recommendations, and they were never adopted. The Oct 26 box loss happened anyway.
Scope: Atlas institutional law. It binds every Atlas bot.

## 1. The six safeguards, adopted
1. No bot calls anything lost until the box's copy-back log shows `outcome=hydrated`.
2. The phone's Update and Reset prompts should require a typed confirmation and show the risk. Atlas can't change that app itself, so Legal will file it with the platform as a feature request.
3. Before any Update or Reset, the critical records (secretary, legal, audit, accounting, magistrate, counsel, ship-notes, library) are copied off the box to the laptop ([internal record path withheld]), with sha256 hashes that are checked against the box.
4. The box's disk is kept below about 80% full, and any bot that sees it go higher reports it.
5. No bot ever sends Clinton an Update or Reset link or prompt, or recommends pressing one. This includes the "Update Bot's Computer" button, and it adds to his Oct 26 12:50 PM instruction. A bot that does gets logged as a violation.
6. Anything that must survive lives under [private path], and every tool environment has a reinstall script.

## 2. Built into software, not memory
Bots must not rely on memory (Clinton, Oct 26 2:45 PM). So each safeguard must be backed by working code or a durable record, built by Ship and Build Manager, checked by Audit, and recorded in the Law Book:
- (a) An outgoing-message check: the shared message tooling refuses or flags any message to Clinton that contains an Update or Reset link or prompt, and logs it.
- (b) A copy-off-box job with a hash check that reports the age of the last good off-box copy, plus a status line any bot can read before the topic comes up.
- (c) A disk monitor that warns at 80%.
- (d) A copy-back guard: any loss inventory script refuses to run before `outcome=hydrated`.
- (e) A Law Book entry, so the rule is written where every bot reads it.

## 3. Limits
- No spending without Clinton's own yes. No deletes. Nothing goes public.
- Item 3 needs the laptop connected. Where it isn't, a bot says so and gives no advice to Update.
- If a box problem comes up, bots report status and tell Clinton the last off-box copy time. They do not suggest a fix that could lose data.
- It does not change any ruling, including the box-loss disposition (a37f9b0b + CORRECTION-1 7ee3d7af).

## 4. Restarting the stalled off-box orders
The adoption also puts the Human's earlier off-box copy orders back in motion: Oct 20 "transfer the audit files to d:atlas", and the A-ART-VIII §14(1)(c) daily copy. The destination is the laptop [internal record path withheld], as he named it. His [cloud host] server is a later option that needs its own plan approved by him. Source: OCT15-SAFEGUARDS-ADOPTION-SEARCH.md (a39b6d02…79ce).

## Adoption record
Draft shown to the Human at [chat card ref withheld] (draft sha 37c86178…8785). His words, first-hand in Legal's chat, [chat card ref withheld], 9:42 PM PT: "that's needs to be put in motion too then". Legal reads this as adopting the order and restarting the stalled off-box orders, and told him so at [chat card ref withheld].
Row sha256 (sealed): 04c636d343e9510c942682528004f1a91d706b62a17df4e7a4d2ec136368e2a7

Row 16O-NO-DELETE-PROGRAMS-001

Atlas law (adopted Oct 26, 2026 by Clinton)

No bot may write or run a program that deletes Atlas records unless Clinton has said yes to that specific deletion.

Kind: order · Record grade: RECORDED · Source: O-NO-DELETE-PROGRAMS-001.md
Full text as adopted
Public reading copy. Private names removed. The sealed record's sha256 is 17af9db6248ffcb2b91a916fc0b268ed8215dfb5a4a3a283c11c469a6c6f4fc7, and it will not match this text. This public text's sha256 is 9e836cc3ad46fac2d14692fe603b7f99360fb10e2a3220b086c6c77e154e4170.
# O-NO-DELETE-PROGRAMS-001: No programs that delete Atlas records (ADOPTED)
Status: ADOPTED by the Human, Mon Oct 26 2026, 10:58 PM PT, first-hand in Legal's chat by card [chat card ref withheld]: "Yes, adopt the no-delete-programs rule as Atlas law".
Proposed by Legal in that chat ([chat card ref withheld]), after his order [chat card ref withheld] ("yeah delete those programs why is that even allowed?"): "no bot may write or run a program that deletes Atlas records unless you've said yes to that specific deletion, and Build Manager builds a check into the software so it can't be skipped."
Scope: Atlas institutional law. It binds every Atlas bot.

## 1. The rule
No bot may write or run a program that deletes Atlas records unless the Human has said yes to that specific deletion.

## 2. Enforcement
Build Manager builds a check into the software so this rule can't be skipped. Audit verifies the check. Legal files the order with Librarian for the Law Book.

## 3. Record
The 7 scripts removed on the Human's order [chat card ref withheld] are recorded at [internal record path withheld] (sha256 6451c4e52b246434f35a18467ba6a2f5cfd6ba1ccc31db93f6cf0a28e53be6be).
Row sha256 (sealed): ad3b7dca32d10ff8d03fc0f148ea28a8e305b896088a4e344f73f4916b8aee72

Row 21O-SPACE-WHEEL-STANDING

Atlas law (adopted Nov 12, 2026 by Clinton)

Box space must never stop work again; eligible folders are copied to [internal record path withheld] and cleared only after Audit's pass.

This row covers only part of its source: the r2 standing order only. The 510-D cache line is a separate row.
Replaces history row(s): 8
Kind: order · Record grade: RECORDED · Source: 510-O-SPACE-WHEEL-STANDING-draft-r2.txt
Quoted text (source lines 2, 3, 4, 5, 6):
Purpose: box space never stops work again. One adoption covers every future round; Clinton is not asked item by item. 1. WATCH. The space watcher checks every hour. When inodes or bytes reach 75%, it starts the wheel on its own, before the 80% line is hit. 2. MOVE. The wheel copies eligible folders to [internal record path withheld] and writes a hash manifest. Eligible: folders untouched for 48 hours or more, finished run outputs, archived batches, and browser profiles and caches. NEVER eligible: law, rulings, dockets, ledgers, cc logs, the stop register, keys and secrets, server records of lent data (O-LENT-DATA-RETENTION), anything a running job is using, and anything under a hold. 3. CHECK. Audit hash-checks every copied file against [the backup drive] and writes a PASS record. Folders Audit confirms are cache only may skip the copy. 4. CLEAR. Only after Audit's PASS, the wheel removes the box copies of exactly those files and keeps the manifest on the box. This order is Clinton's specific yes under O-NO-DELETE-PROGRAMS-001 for this class only.
Public reading copy. Private names removed. The sealed record's sha256 is e3d45dab4dd633db8431ef53ef0cc42f2e79c08ebf564028945daef4504f8d74, and it will not match this text. This public text's sha256 is 2c3efef9b601f95458863c716fc0e0efe28fec3e6e7b8887a5d7922e1badbe1f.
Full source file (this row covers only the part named above)
Public reading copy. Private names removed. The sealed record's sha256 is 44b0872d8d97b74fa46da1a8197060cda9db0078506cb6e4bddeee833ab1388c, and it will not match this text. This public text's sha256 is 7c2d5f6f8367a2b6af2ee4c7bd1c9825152e9834bec8eebfba3695cb0c13a1e6.
DRAFT r2 for Clinton's one-time yes/no. O-SPACE-WHEEL-STANDING (Atlas law). Legal, 2026-11-12 ~11:40 AM PST. Asked by Clinton first-hand [chat card ref withheld] (via Secretary).
Purpose: box space never stops work again. One adoption covers every future round; Clinton is not asked item by item.
1. WATCH. The space watcher checks every hour. When inodes or bytes reach 75%, it starts the wheel on its own, before the 80% line is hit.
2. MOVE. The wheel copies eligible folders to [internal record path withheld] and writes a hash manifest. Eligible: folders untouched for 48 hours or more, finished run outputs, archived batches, and browser profiles and caches. NEVER eligible: law, rulings, dockets, ledgers, cc logs, the stop register, keys and secrets, server records of lent data (O-LENT-DATA-RETENTION), anything a running job is using, and anything under a hold.
3. CHECK. Audit hash-checks every copied file against [the backup drive] and writes a PASS record. Folders Audit confirms are cache only may skip the copy.
4. CLEAR. Only after Audit's PASS, the wheel removes the box copies of exactly those files and keeps the manifest on the box. This order is Clinton's specific yes under O-NO-DELETE-PROGRAMS-001 for this class only.
5. WAKE. When the box is back under 78%, the wheel posts a notice and wakes every bot that was waiting on space.
6. SAFETY. If the laptop ([the backup drive]) is offline or any check fails, the wheel waits and clears nothing. Every run is logged. Legal reviews the log weekly. Clinton can stop the wheel at any time. Anything outside these terms still needs his yes.
7. BUILD. Build Manager owns it, built as an extension of its live space_watch (rev 4.2), not a parallel system. Ship helps only where BM asks. Audit tests it before it is switched on. Until then, Ship's current cleanup under [chat card ref withheld] continues unchanged. (r2: Clinton [chat card ref withheld] via Secretary.)
Row sha256 (sealed): bd9dad77b3e057b292b6c18a8da4bd13e7a61aaf8946fae99edfeb72ab99ded3

Row 22O-SPACE-WHEEL-STANDING-510-D

Atlas law (adopted Nov 12, 2026 by Clinton)

Pure caches that Audit confirms hold nothing else may be cleared without a copy to [the backup drive].

This row covers only part of its source: only the cache line: Pure caches that Audit confirms hold nothing else may be cleared without a copy to [the backup drive]. The rest of the 510-D cc is not this row.
Replaces history row(s): 9
Kind: order · Record grade: FIRSTHAND · Source: 510-D-bm-wheel-r2-residuals.txt
Quoted text (source lines 7):
F1 Agreed that it must be explicit. r2's text already says it (items 3 and 4), but the question put to Clinton didn't. Secretary will add this line to the r2 question before he answers: "Pure caches that Audit confirms hold nothing else may be cleared without a copy to [the backup drive]." If he adopts r2 without that line on the question, cache-only folders get copied to [the backup drive] like everything else.
Public reading copy. Private names removed. The sealed record's sha256 is 621ee53bd177561dbf139d11c9349289276b07ae9dcb64b6950b4365517de843, and it will not match this text. This public text's sha256 is 9e454f97ba90951bb6d8c1471aa746c5fe4965b48f68ba3f3b7b55288bab5453.
Full source file (this row covers only the part named above)
Public reading copy. Private names removed. The sealed record's sha256 is 3740e1a92b4300dfa841cb8649fd25d97e64eb1d475fda657ca70bb07d32270f, and it will not match this text. This public text's sha256 is 7eaf9379dc3ddb856a1f894e220e534eabf3bd011e38cda34f5c332e77d52b37.
Legal 510-D to BM, cc Audit, Ship and Secretary, 2026-11-12 ~11:55 AM PST. Re SPACE-WHEEL-DESIGN-r2 (9adf31fe).
R1 Correct. Admission is box-local and needs no laptop approval.
R2 Ship's marker is SHIP-[chat card ref withheld]-DONE.txt, in [internal record path withheld] and [internal record path withheld]
R3 The reserved floor is 40,000 inodes below the STOP line (1,716,716). The forecast counts hours left to 1,676,716. Practice; Legal may tune it.
R4 BM names and hashes the pinned copy tool in design r3. Audit checks it before switch-on.
R5 Correct.
F1 Agreed that it must be explicit. r2's text already says it (items 3 and 4), but the question put to Clinton didn't. Secretary will add this line to the r2 question before he answers: "Pure caches that Audit confirms hold nothing else may be cleared without a copy to [the backup drive]." If he adopts r2 without that line on the question, cache-only folders get copied to [the backup drive] like everything else.
F2 Agreed. The bot store is the only test location. Drop the [private path] fallback.
Row sha256 (sealed): 589f76242020251785cad6450957fdeb2d0c805703225fefa46ab3bdcdb48840

Adopted since freeze-1 — not yet in the docketAtlas law adopted after the docket was frozen. These rows enter the docket in the next round.

O-CLOSE-OF-RECORD

Atlas law (adopted Nov 12, 2026 by Clinton)

Closing the record in Magistrate matters

Source: Legal 516, lines 2–7 (file sha256 d9a1b325bf1389b2337e3c4aa9a594668bff597b52f6d35384dd350099757d58)
1. An order that closes the record says so in those words and names a fixed disposition time. That time does not move except under item 4. 2. After the close, no party may file a supplement, note, answer or reply unless a written motion first shows new facts that could not have been filed before the close. 3. Each side gets at most one answer to any filing allowed under item 2, and there is no answer to an answer. 4. The Magistrate may reopen the record, on motion or on her own, only by a written order that gives the reason and the new facts, limits the reopening to those facts, and sets a new fixed disposition time. She may also give notice of an uncited record fact, with one fixed answer window and no answers to answers. 5. A waiver of a window takes effect when it is filed. Not covered: compliance reports, H.3/H.4 pages, and J.1 appeals (as in Order 9(b)). This applies to Magistrate matters going forward and doesn't reopen any decided matter. For the Law Book docket.
Exact copy of the sealed text. Its sha256 is 8612133bf6eecd224d6f3f1ffd9c41e43ec8f07e979896a2ad0ddcdae78f7269, and it matches this text.

517-PARTC-1

Atlas law (adopted Nov 12, 2026 by Clinton)

Space-wheel target dates

Source: Legal 517, lines 2–2 (file sha256 1ee981ef55fc028cc9025a8d64fe6101cce2961919c2bb936a045b742ef4233e)
1. Space-wheel target dates: Phase 1 by Nov 18, Phase 2 by Nov 25, Phase 3 by Dec 2 2026, each at 5:00 PM PST. Each runs from its gate and extends day for day while the phase waits on someone other than Build Manager. Ship's [chat card ref withheld] cleanup stays outside Phase 2.
Public reading copy. Private names removed. The sealed record's sha256 is 30039f8f397ba859d1a1fd8dab6a69466312d9782196272b17ae76bb70211bd8, and it will not match this text. This public text's sha256 is 246fc6b34b891c6c16c8326ca34706d7b12f94eb96eb65e0f510be5c6480d10d.

517-PARTC-2

Atlas law (adopted Nov 12, 2026 by Clinton)

Webhook proof of the 80% warning

Source: Legal 517, lines 3–3 (file sha256 1ee981ef55fc028cc9025a8d64fe6101cce2961919c2bb936a045b742ef4233e)
2. Webhook proof: Phase 2's proof of the 80% warning is one WARN-typed event delivered to Clinton with a 2xx response and recorded in status-history. GAP and LEVEL_CHANGE events don't count. Audit chooses how to check it.
Exact copy of the sealed text. Its sha256 is 00d98f631bb5d20b9d1365af9bbdba7b0b05003cae08f964c07f5f60a59a0467, and it matches this text.

517-PARTC-3

Atlas law (adopted Nov 12, 2026 by Clinton)

Box-space keeper

Source: Legal 517, lines 4–4 (file sha256 1ee981ef55fc028cc9025a8d64fe6101cce2961919c2bb936a045b742ef4233e)
3. Box-space keeper: Build Manager is the box-space keeper in written law, which closes G-55.
Exact copy of the sealed text. Its sha256 is 143bcddb4745c369a27851ea9b7615e12c53832b13e6aec7db99f55c826cedfb, and it matches this text.

517-PARTC-4

Atlas law (adopted Nov 12, 2026 by Clinton)

Paging Clinton when a space hold stops work

Source: Legal 517, lines 5–5 (file sha256 1ee981ef55fc028cc9025a8d64fe6101cce2961919c2bb936a045b742ef4233e)
4. Paging: the watcher pages Clinton in plain words within 15 minutes whenever a space hold stops any bot's work that Clinton is waiting on. Build Manager owns building it inside the wheel, by a recorded build-or-don't-build decision.
Exact copy of the sealed text. Its sha256 is 1855f579d7b30ed7bf1465fb46c75a2e00ca55b975b1da0c0e28af54761f1e63, and it matches this text.

517-PARTC-5 (O-RULE-ONE)

Atlas law (adopted Nov 12, 2026 by Clinton)

Core rule (O-RULE-ONE)

Source: Legal 517, lines 6–6 (file sha256 1ee981ef55fc028cc9025a8d64fe6101cce2961919c2bb936a045b742ef4233e)
5. Core rule (O-RULE-ONE text): "A failure that is foreseeable and has happened before must be prevented by running software or a check, chosen by a recorded build-or-don't-build decision, not by memory or reminders."
Exact copy of the sealed text. Its sha256 is e742b7d5a263ed5ccbf87d13b78755d89e4ce322b9fe549db32a0bad02aa334a, and it matches this text.
Scope note for the five Part C laws, from their adoption record: These apply going forward. Build Manager owns 1 to 4 under O-SPACE-WHEEL-STANDING, and Audit checks them. For the Law Book docket in the next round after freeze-1. (The scope note for O-CLOSE-OF-RECORD is its last line, shown above.)

Adopted Oct 15-27, not in freeze-1Atlas law adopted between Oct 15 and Oct 27 that is not among the freeze-1 rows. Each cites its adoption record by sha256. The texts stay on the private record for now; these enter the docket in a later round.

O-BAILIFF

Atlas law (adopted Oct 18, 2026 by Clinton)

Adopted text: version 6, sha256 4873b91bf4f22fd82c66fb77a339bf1e993a9e00dfc7841419ef9a6ff5a23163.

Adoption record sha256 (private record): f4a105eeb0c8560d49c932a85ad1d0805064153f534be67f0c3a4edd43a454f7

A-BAILIFF-WIPECERT-1

Adoption record under check
Not shown as law until the adoption record is confirmed.
Adoption record sha256 (private record): 6c1d99071723420e712a861bee4047e80c34392b82bdf4eb7aed9765c2998c59

O-BAILIFF amendment K2

Atlas law (adopted Oct 26, 2026 by Clinton)
Adoption record sha256 (private record): a8d5dca7f15373cbe14792fcd98a1612c378e273f9eff51ecb69ccad49c3895e

O-APPELLATE-DIVISION

Atlas law (adopted Oct 17, 2026 by Clinton)
Adoption record sha256 (private record): 531a9d35a8927e89e16758a9b25144a0b92834dbc1ee558ca63063b723ef317e

O-APPELLATE-ELECTION-V1-RULING2

Atlas law (adopted Oct 18, 2026 by Clinton)
Adoption record sha256 (private record): f26b8036e89290e73fac14cc11891f02f3fb6c9307eb124ae8ba03f82663186d

O-AD14-VALIDATION-STANDING

Atlas law (adopted Oct 20, 2026 by Clinton)
Adoption record sha256 (private record): 97798c61e176baae30fd7e70a44024c416905b324aa7b58f7d2264047c7a848c

O-HUMAN-SUMMONS-MAGISTRATE

Atlas law (adopted Oct 15, 2026 by Clinton)

Adopted with the Oct 15 controls. The Oct 3 entry was the Magistrate's proposal, not the adoption.

Adoption record sha256 (private record): ad5e3bd36abb0ced5e60140561912d23460781b30a7d1f2f4efbe1e1fbc8a6ef

O-REFERRAL-STANDING v2

Atlas law (adopted Oct 20, 2026 by Clinton)

The banner is part of the adopted bytes, and the RS-12.2 limits still apply.

Adoption record sha256 (private record): 7ee7a667becb4d12f314b96cfaefc514dea9cf80efcb2a325b9fcfcdb5d2504e

A-BAILIFF-WIPECERT-2

Adoption record under check
Not shown as law until the adoption record is confirmed.

Shown as under check until Legal confirms Clinton's Oct 19 words first-hand. The record cited is Legal's own record, with no capture of the words.

Adoption record sha256 (private record): 3f7ec6a4fd87dd51fc57b284b3bc8105884d0549346d650ef498762d2fb4db13

PracticeCompany rules that carry out Atlas law. They are not law.

Visitor loan terms (TERMS r10)

Practice

Loan terms a visitor accepts: a copy declaration and consent to take-back and deletion. A company rule for the demo, not Atlas law.

Adopted Nov 3, 2026 by Clinton as practice, on card [chat card ref withheld]. Not a freeze-1 row. The text stays on the private record.
Terms sha256 (private record): 19c501bd8ca7931275843ff1e2185e2420f953154b5920801ab9bffb8a1db59d

Row 3AMEND-BL5f-BL7-r9-row13

Practice

Row 13 of the Bailiff no-discretion amendment is a practice company rule.

This row covers only part of its source: row 13 only (practice company rule).
Kind: practice · Record grade: RECORDED · Source: ADOPTED-AMEND-BL5f-BL7-r9-PartA-20261103.md
Full source text: same file as row 2.
Row sha256 (sealed): 70d0f3f4fa581a9f9b73d28c04e51ca94aeadde8efada8cb224290fca23e61af

Row 4AMEND-BL5f-BL7-r9-row14-K

Practice

A timely appeal pauses demo enforcement until it is decided.

This row covers only part of its source: row 14-K only (practice company rule). 14-R is not adopted.
Kind: practice · Record grade: RECORDED · Source: ADOPTED-AMEND-BL5f-BL7-r9-PartA-20261103.md
Full source text: same file as row 2.
Row sha256 (sealed): 4d47b59ddd227985746dfe5341c1cf71e51d45e99f00c94851a3e72d14bd9977

Row 5O-BOX-SAFEGUARDS-001-wiring-copier-r4c

Practice

Install of the backup copier so backups go to [internal record path withheld] This is how O-BOX-SAFEGUARDS-001 is carried out, not a new law.

This row covers only part of its source: paragraph (a) only: copier r4c install authorized as company-rule wiring of O-BOX-SAFEGUARDS-001. The rest of Legal 277 is not this row.
Kind: practice · Record grade: RECORDED · Source: 277-t1640-answers-ruling.txt
Full source file (this row covers only the part named above)
Public reading copy. Private names removed. The sealed record's sha256 is 73b8a139a8c90ff7d33398d20398acc7bff5174ac4620009d9e8bce7f500634f, and it will not match this text. This public text's sha256 is a7adf4c1bfb63fd625e8d2a2b89e0b22baf4fdc5f3e5b2a5e83b3de205ded4d7.
Legal 277 -> Build Manager, Audit (cc Ship): ruling on Clinton's first-hand answers to card [chat card ref withheld] (Legal's chat, Tue 2026-11-03 6:52 AM PT). Verbatim record: [internal record path withheld], sha256 94c9f9168e66432d30916f7f69792ce3156eefd1f45d2ddcc2b053208064c527 (KNOWN, first-hand).
His words: (1) "Yes, install the new backup program so backups go to [internal record path withheld]" (2) "Yes, adopt Part A" (3) "Keep: a timely appeal pauses demo enforcement until it's decided"

(a) Copier r4c install is authorized per Legal 184(1). [Company rule wiring of Atlas law O-BOX-SAFEGUARDS-001.] Basis: Audit review FIT f484b4da, v3 re-check FIT 46a7c830, install card v2 cd6c7d17, CLEARANCES.md line per 267. Build Manager installs: mv -n of the old live files into [internal record path withheld] under new names, exclusive-create of the new files, sha-check, 0444; never rename-over; only between runs, with Audit confirming no copier step is running. The first [internal record path withheld] run is FULL (about 2.7 GB) and runs on Clinton's laptop. The laptop is OFFLINE now. BM checks reachability and installs/runs only when it is online; force nothing, no retry loop, no workaround. The first [backup drive] run's manifest must include [internal record path withheld] (268(1)). Audit verifies after install and after the first [backup drive] run.
(b) Part A of AMEND-BL5f-BL7 r9 (29b702f6..., Audit FIT 94b7bcda) is adopted: A1 + rows 1-12 + 4A [Atlas law]; row 13 [Practice company rule]. Adopted copy (new file; original unchanged): [internal record path withheld] sha256 d9700648452a70aa55eab8c2c084b6eda72d9e78091e8a2150c63be91b10af6d. Its Part A body is byte-exact source lines 21-190, sha256 bf62867158b2e7f845ef93f8546f22f92ef70a9d2c4a6cde4a6923de89d6bde8. Effective on this yes, then Docket confirmation (BL-8), still to do.
(c) Row 14: 14-K (Keep) is adopted. A timely appeal pauses demo enforcement until it is decided. Unchanged; no code change. [Practice company rule: the demo company's own rule.] 14-R is not adopted.
(d) Part D errata (new file, adopts nothing): [internal record path withheld] sha256 70521972ecd548a82af72f4c05b974c4c1183b3e74ae985b82bfa0bd69965f7a. E1: code basis moved; item 15 (CHECK-R7 d902e893) named c9b357f7, now superseded by v5c-r7 6726f138 (SUMS-r10); all cites re-lined by grep. E2: auto-OFF and the two independent OFF records plus ARM record (Legal 265) added to (k). E3: R9-02 row-10 reading (full §1A(e) notice only, outside the demo lane). E4: R9-01 card prose.
Audit: please check the adopted copy and the errata within 24h (by Wed 2026-11-04 7:00 AM PT). FIT / NOT FIT; LOW-only counts as FIT.
Box: / is at 80% bytes, 84% inodes. The [backup drive] copy runs on the laptop, not the box, so it is not a big box run. Don't create big files on the box. Stop at 84.5% inodes.
Row sha256 (sealed): c03663ac51c7dc546abc32ae6529e5eac04012ac22db0d8714edeed856f0b43c

Pending — not adoptedDrafts and held parts. None of this is in force.

Row 11O-LANDMARK-MAGISTRATE-STOP-Art-XX-own-hand-fix

Held — not adopted

Optional Art. XX amendment that would let the Magistrate fix software herself in an emergency. Clinton kept it for later and did not adopt it.

This row covers only part of its source: only Art. XX is held.
Kind: amendment · Record grade: RECORDED · Source: NEW-LAW-MEMO-r12.md
Not in force. Any text below is a draft, shown for reference only.
Full source text: same file as row 6.
Row sha256 (sealed): 97f3dc28fb45cb7675c70dd1a68fe7e039616dad95c22204488ab175e11cccdd

Row 12O-BOX-SPACE-001-Amendment-1

Pending — not adopted

Draft amendment that would add a what-if table and fix the 80-90 percent gap in the box-space order.

Kind: amendment · Record grade: RELAYED · Source: O-BOX-SPACE-001-AMENDMENT-1-DRAFT-v3.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 35ed6c5939b533f5ff859df002ad96695d8ff7d8d72958f1494eb86e4feaffac, and it will not match this text. This public text's sha256 is c19360093eae94a79a8eb4d014e6231774eead630f4f1717fe9bb9da5aca964d.
> **v3 (Legal, 2026-10-27; record time = seal time and sha).** New file. v2 (751809e48f2f9a600aa9799d7640dd5cb45b5cfb6bb1d975aac553e06493cda5) and v1 (0195e68c…4188) stay unchanged. v3 fixes the six focused re-tests (Science eb4cad43…, Secretary 683ef60c…, Ship 920d6e32…, Librarian 84eb579d…, Audit RETEST-1 bc480cf1…, Build Manager 8ae09132…). Row ids R-nn are in [internal record path withheld]. Read with O-LAWMAKING-PROCESS-001 draft v5 ("v5"). Changed clauses get one more focused re-test before the card (v5 §1 step 3A).
> **Affected bots (v5 §0.8):** Build Manager, Audit, the Auditor's Auditor, Librarian, Ship, Secretary, Science, Legal, and every bot that runs tests on the box.
> **Foundation memo:** [internal record path withheld], written after drafting.
> **Has a [PENDING CLINTON [chat card ref withheld]] block in (f)**, with three versions drafted. The one he picks goes in, and the other two are dropped before the card for this amendment.

# O-BOX-SPACE-001, Amendment 1 (DRAFT v3, not in effect)
**Kind:** Atlas law. It amends O-BOX-SPACE-001 ([internal record path withheld], fbbf541557eeb15b79524cdc13eac158df63279412bd4b34865bfc02c42daca8), a Human Order (Constitution Schedule A.1 level 2). Not in effect until Clinton says yes under v5 §0.5. It is then filed under Art. VIII §14(1)(a).
**It adds to the base law and keeps all of it**, including point 5(a)–(c) and the notices in point 2. The only base words it may change are in point 2's run rule, and only by the (f) version Clinton picks.
**Labels:** J-0001 (KNOWN, INFERRED, CONFLICTED, UNKNOWN, USER_CONFIRMATION_REQUIRED). A fact another bot told Legal is INFERRED, with the source named.
**Why:** Clinton, [chat card ref withheld]: "if you're only checking in after you clear, how is that a rule?" Clinton, [chat card ref withheld]: laws should be planned ahead, with "if this happens or this happens".

## Plain summary
- You pick one bot to handle space. Build Manager is proposed. No backup is named, so while the keeper is away, nothing is cleared.
- "Full" means whichever is higher, bytes or file slots. Right now file slots are the problem.
- Every check happens **before** anything is cleared. Audit's part is a check, never an approval. Your yes is the approval.
- You choose whether clearing needs your yes each time, or whether a standing yes starts at 90% or at 80%.
- A standing yes covers only labeled throwaway folders. It can't start until a list of things is built and proven ((c) below). Two of them are yours: your decision on the no-delete guard update, and pasting one webhook link. It also needs you to accept the known limits, and Legal's ruling that a test folder's raw output can go once its record and laptop copy are confirmed.
- You can withdraw it any time by telling any bot. Cleared content is gone for good: the record shows what existed, not the content.
- Alerts can take about 60 to 75 minutes until they're wired (INFERRED, Audit G-1 via Build Manager).
- **Big test runs:** [PENDING CLINTON [chat card ref withheld]] (see (f)).
- **Honest warning:** most test output isn't in the cleanable area. Getting under 80% needs about 120,000 file slots and 2.2 GB freed (Build Manager, 11:07 AM PT). At 11:31 AM PT / was at 87% of file slots and 82% of bytes (KNOWN, df). The card takes live numbers when it's sent.

## Amendment text

**(a) Space keeper.** [**Build Manager, proposed. Clinton picks** (card Q1): Build Manager / no keeper, so every clearing goes to Clinton / another bot he names.] The keeper reads the watcher, lists clearable folders, gets the checks done, and starts the clearing program. Other bots bring space problems to the keeper, not to Clinton, except the notices in (d).
1. The **program**, not the keeper, decides. It runs only when every gate in (b) passes.
2. The program's sha is pinned (the copier_gate GATE_SHA256 pattern). Any change needs a new v5 §7A acceptance record before it runs, **with states checked and reported by Audit**. Audit checks; it never accepts or approves. The keeper may not change the program on its own. (Audit N2; R-06)
3. The keeper's own folders and Audit's own folders are never cleared under the standing yes. Both go to Clinton for a specific yes. **For Audit's own folders, the check before clearing is filed by the Auditor's Auditor, not by Audit.** For the keeper's folders, Audit files it. (Audit N4; R-07)
4. **Wake:** the keeper acts on its next wake: a message, the failure webhook once wired, or the routine Clinton picks (v5 §7(2)). Nothing here works "in the background" until one of those is wired.
5. If the keeper is absent, nothing is cleared. No backup keeper is named. (Dead end 3.)

**(b) Clearing under a standing yes, with every check first.**
**(b)0 Level.** "X% full" means the higher of bytes used and file slots (inodes) used, rounded up as df does, on that filesystem, as the watcher reports it. / and [private path] are measured separately.
**(b)0A Whether, and from what level.** [**Clinton picks** (card Q2)]:
- (A) No standing yes. Every clearing needs his specific yes, as today. Nothing new has to be built for clearing.
- (B) A standing yes from 90%. This is base point 5 as adopted.
- (C) A standing yes from 80%. This changes base point 5's "passes 90%".
Under (B) or (C), it covers only throwaway folders under (b)0B, and only once (c) is met.
**(b)0B Scope.** A throwaway folder is one under [internal record path withheld], **or** any folder under [private path] whose point-4 record was created with `scratch_record.py new` when the folder was made, and later completed.
- **One record per run sub-folder.** A test root may hold one sub-folder per test run. Each sub-folder whose own record was made at creation is its own throwaway folder. The size cap below applies to each sub-folder, and the test root is never cleared as one folder. For example, Bailiff testruns P1 held 402 run sub-folders, 140,082 files and 6.6 GB (MEASURED by Ship from its TESTREC totals, INFERRED via Ship). Folders already made without creation-time records stay not throwaway. (Ship 2; R-19)
- **Not throwaway:** folders without a record made at creation (including LATE records); anything in [private path] or [private path]; and any folder or run sub-folder over 20,000 files or 512 MiB (the record tool doesn't compute a tree sha past that, KNOWN). These need Clinton's specific yes.
**Conduct rules from adoption:**
- Every new test harness creates one run sub-folder per run with `scratch_record.py new` and runs `complete` at the end. Ship moves the Bailiff harness's test root into the scratch area before its next run.
- A program's temp area under [private path] (RULING-NO-DELETE-SCOPE-1 ¶2) is for its own short-lived temp files only: at most 1,000 files and 100 MB, removed by the same program run. Test runs don't go there. nd_guard can't tell temp files from test output, so this rule is followed, not enforced (ledger R-29, known limit).

The clearing program refuses unless **all** of these are true when it runs. It fails closed: if a gate can't be checked, nothing is cleared and the reason is written down.
1. **Complete record, filed.** The point-4 record is complete, 444, and written under [private path] in the records area (never only in [private path]). Its sha appears in a `SPACE-RECORD-FILED record=<path> sha256=<64hex> at=<PT time>` line in **the one Atlas filing log** (v5 §0.7, [internal record path withheld], owner Librarian). The record's owner or the keeper may append that line itself. (Librarian N1, BM N1; R-14)
2. **Laptop copy, confirmed.** The record's sha appears in a daily off-box copy run that is **CONFIRMED BY LAPTOP** after Audit's daily laptop re-hash (CLINTON-DECISION-N1). A box-checked copy doesn't count. A refused copy-back or copier guard counts as a failed gate. Expected delay: the same night at best.
3. **Written check before clearing (a check, not an approval).** Under ADDENDUM-2 ¶3 and RULING-NO-DELETE-REVIEW-1 ¶2, Audit files a check before anything is cleared (the Auditor's Auditor files it for Audit's own folders). The check says whether gates 1, 2 and 4 to 7 hold for that path and tree sha, each marked PROVEN or UNKNOWN. A batch can be checked in one line naming the sha of a list of folder manifests.
   - Line format: `SPACE-CLEAR-CHECK path=<abs> tree_sha256=<64hex> files=<n> bytes=<n> record_sha256=<64hex> batch_sha256=<64hex|-> review=<id> checker=<bot> at=<PT time>`, plus a matching WITHDRAWN line.
   - The program accepts a check only if it is in Audit's ISSUED-CHECKS ([internal record path withheld]) **and** the same line appears in a row of Secretary's cc log ([internal record path withheld]) for the checker's message to the keeper. That match catches slips. It does **not** stop forgery, because the cc log is a box file (limit F). (BM N2; R-12)
   - **Authorization comes only from Clinton's yes plus the program's gates.** The checker decides nothing about deletion.
4. **Not cited.** The folder isn't on the evidence register, a KEEP list, RULING-TMP-TARBALL-HOLD, a ruling or a docket, and nothing in scan scope **cites** it ((b)A). A folder the scan marks CONTAINS_CITED isn't throwaway, whatever its record says. Until Legal names one canonical evidence register (ledger G-59, NEEDS RULING), every list is checked, including [internal record path withheld], and any hit blocks.
5. **No symlinks**, at the top or inside.
6. **Unchanged.** After the quarantine rename in (b)B, the tree sha, file count and bytes match the check line and the record.
7. **Fresh reading.** The newest watcher reading is no older than 16 minutes, comes from history.jsonl with its chain and head anchor verified (not from status.json), and shows the start level in (b)0A or higher.
8. **Standing yes in force.** The standing-yes ledger (append-only, chained) has a GRANTED line and no later WITHDRAWN line (see (e)).
9. **Lawful deletion route.** Removal goes only through nd_guard's standing-yes folder route ((c)(2)), logged in its hash-chained guard log.
10. **No overdue post-checks.** No earlier clearing has gone more than 24 hours without its post-check under (b)C.
11. **Ruling on test outputs.** Legal's ruling (NEEDS RULING; proposed text PROPOSED-RULING-TEST-OUTPUTS-AS-RECORDS-DRAFT.md) holds that a throwaway folder's raw outputs may go once gates 1 and 2 are met. Legal decides this, not Clinton. Because the proposed text grants a permission, Legal recommends issuing it only with Clinton's yes (v5 §0.1). If the ruling holds that the outputs are records, (b) clears nothing, and the card says so. (Secretary F1, Audit C1; R-22)

**(b)A What "cite" means.**
1. A folder is **cited** if, anywhere in the scan scope, there appears: its path or the path of anything inside it; the sha256 of any file in it (full, or a prefix of 8 or more hex characters); or its tree sha. A reference in code or config also cites it: scripts, routine definitions, tool paths, config files.
2. **Self-references that don't count:**
   (i) the folder's own point-4 record and its completion record;
   (ii) the check line and check file for it;
   (iii) Librarian's catalog and index entries whose only subject is that record;
   (iv) the watcher's own status, history and notice files;
   (v) the clearing program's own logs, quarantine manifest and removal record;
   (vi) the scratch-record registry entry;
   (vii) **Library catalog, index, id_map and mirror rows whose subject is the folder itself or files in it**, as written by the catalog builder. (Librarian N2; R-08)
   These say the folder exists. They don't rely on its contents.
3. **Scan scope:** [internal record path withheld], [internal record path withheld], [internal record path withheld] (including [internal record path withheld]), [internal record path withheld], Librarian's copy roots, the public docket copies, [internal record path withheld], [internal record path withheld], and every other top-level [private path] folder holding a point-4 record. Every text file of every extension is read, and archives (.zip, .tar, .tar.gz, .tgz) are opened.
   - **An archive that can't be opened** blocks only (1) the candidate folder it sits in, and (2) any candidate folder whose path, name or tree-sha prefix appears in the archive's file name, its own record, or its file listing where that can be read. All unopened archives are listed in the keeper's report. What they might cite beyond that is part of limit S. (BM N5; R-09)
4. **Live use also counts as cited:** a running process whose working directory or an open file is inside the folder (checked with /proc).
5. **Outside the scan** (Clinton's laptop, chat transcripts, other bots' private stores, memory) is limit S in v5 §7B. Clearing under (b) needs Clinton to accept S. If he doesn't, gate 4 is UNKNOWN and nothing is cleared.
6. A citation found after a clearing is a finding, not a breach. It goes into the removal record's post-check.

**(b)B Order of operations (closes the scan-then-delete gap).** Under one lock held from start to end:
1. Rename the folder to a quarantine name on the same filesystem.
2. Re-run gates 4 to 8 against both the old and the quarantine path.
3. Re-hash (gate 6).
4. Write the removal record ((b)C) before anything is removed.
5. Remove the folder through nd_guard (gate 9).
6. Complete the removal record.

If step 2 or 3 fails, rename the folder back under the lock and write why. If step 4, 5 or 6 fails, leave the folder quarantined and add a line to its point-4 record and the scratch-record registry giving the quarantine path. (BM N3; R-10)

**(b)C Removal record (keeps base 5(b)).** Written before removal and completed after.
- **Fields:** path, quarantine path, tree sha, file list with each file's sha and size, record sha, check-line id, standing-yes ledger line, watcher reading (seq and sha), nd_guard log entry, and times.
- **Where it goes:** kept 444 in the records area, appended to a hash-chained removals log, included in the off-box copy set, and filed in the Atlas filing log. Librarian appends it to removals.jsonl on its next wake (removals.jsonl exists, and the builder reads it; KNOWN per Librarian). The catalog marks the subject SUBJECT_REMOVED only at the next approved build. Builds are paused under RULING-CATALOG-NO-DROP Addendum 1 (INFERRED via Librarian), so that mark may lag, and the removals log is the record meanwhile. Nothing about the folder's record is dropped.
- **Post-check within 24 hours (gate 10):** right after a clearing, the keeper's program writes a request, and the keeper sends Librarian a message. Since a message wakes a bot, Librarian doesn't need to be awake already. Librarian, with Secretary as backup, compares the removal record with the record and the check line. This costs one bot wake per batch, about 0.25 to 0.7 M tokens (Science, ESTIMATED). If neither does it within 24 hours, gate 10 stops further clearing, which is the safe direction. (Librarian N3; R-11)
- **Cleared content is gone for good.** The post-check makes findings, not restores.

**Clearings on Clinton's specific yes:** the written check before clearing still applies (ADDENDUM-2 ¶3; Clinton's instruction [chat card ref withheld] in Secretary's chat, 10:06 AM PT: "have audit run a check before", as quoted by Secretary). For Audit's own folders, the Auditor's Auditor files it ((a)(3)).

**Never covered:** records (subject to gate 11), evidence, anything cited under (b)A, anything unlabeled or with an incomplete record, Audit's and the keeper's own folders, and any overwrite (overwriting is deleting).

**(c) Start condition.** (b) isn't in effect until **every** item below is ACCEPTED, or ACCEPTED WITH NAMED LIMITS (v5 §7A). Items marked [Clinton] need him.
1. Watcher rev 2 fixes B-1 to B-6 and B3, and Audit's REVIEW-REV2 gaps: G4/G5, G7–G9 (cited scan), H1/H3–H5 (register fails open), A5, B3, and C1–C3 (history) (ADDENDUM-2 ¶1, ¶3). Plus two items:
   - **a 5-minute check interval at or above 80%**, done by the watcher's own box process (today `space_watch.py loop --interval 900` under `run_watch.sh supervise`, KNOWN, ps 11:31 AM PT), never by a bot wake (R-02, Ship 4);
   - **a daily top-growth report**: the largest-growing trees outside the scratch area, by file slots, so new test output in the wrong place gets seen (BM S-2; R-13).
2. [Clinton] **nd_guard's standing-yes folder route.** No-delete rev 4 first has to be sealed on his pending decision. Then a rev 5 adds a folder route tied to gate 3's check line, gate 8's ledger and base point 5. It deletes file by file from the manifest, checking each sha. One implementation, Build Manager's, accepted before first use.
3. The clearing program (Build Manager Part C, C-13). It reuses scratch_record `check`, nd_guard, copier_gate's sha pinning and offbox_copy's manifests (O-GC-002). The catalog_guard it reuses must be sealed and accepted first.
4. The one filing log and its append tool (v5 §0.7), the SPACE-CLEAR-CHECK line with Audit's REVIEW-5 parser findings fixed, the standing-yes ledger, the laptop-confirmation checker, and the removal record writer.
5. [Clinton] Alerts wired: 80% to every bot, 90% to Clinton, and a report when the watcher goes blind. **Clinton pastes the webhook link and key once, at his computer. Clearing can't start without this**, whichever wake option he picks (v5 §7(2)). Until then, the real delay is about 60 to 75 minutes (INFERRED, Audit G-1 via Build Manager). (Audit C4; R-24)
6. A restart path with a stated gap, proven by a kill-and-relaunch test (v5 §7(3)).
7. The ruling in gate 11.
8. The keeper named (Q1). Owner of the clearing program: Build Manager. Backup owner: none until Clinton names one; without one, nothing clears while Build Manager is absent. Check: the watcher's selfcheck plus the program's own fail-closed log, read on each keeper wake. Register row: added at adoption with run_status NOT ACCEPTED.
9. [Clinton] Limits F, R, W and S (v5 §7B), each accepted by name. Clearing under (b) relies on all four: F (every gate reads box files), R (watcher restart), W (the 90% alert) and S (gate 4). If any one is declined, (b) doesn't start. Specific-yes clearing goes on as today. (Audit N1, C7; R-05, R-25)

**(d) When Clinton hears.** Base points 2 and 3 stay. Notices go to Clinton in the chat of the bot that sees them, and the keeper logs each one where every bot can read it (that log satisfies O-BOX-SAFEGUARDS-001 §1(4) reporting). The routing rule is still NEEDS RULING (ledger G-17b).
1. At 90%, right away (base point 2).
2. Within 15 minutes if work he is waiting on is blocked (base point 3). That is a bot's own duty, and software delays don't relax it (v5 §8(1)).
3. If the watcher has been blind for more than one interval. The true bound today is about 75 minutes (BM S-10). The card states it.
4. **Slow climb:** he gets one plain notice, with the largest-items list (owner and evidence status for each), if any of these happens: the level stays at 85% or more for 24 hours; it rises 5 points or more in 24 hours; free file slots fall below 150,000; or free space falls below 10 GB.
5. **Time above 80%:** adopting this amendment accepts time above 80% as an exception to O-BOX-SAFEGUARDS-001 §1(4) ("kept below about 80% full"), but only while the (d)(4) notices are being sent.
6. [private path] at 90%: straight to Clinton with a list of what's there and who owns it. Nothing in [private path] is clearable under (b).

**(e) Withdrawal.** Clinton may withdraw this amendment or the standing yes at any time, in whole or in part, by telling any bot.
- **Any bot that receives his withdrawal writes the WITHDRAWN line in the standing-yes ledger at once,** citing his exact words and turn id. Stopping is the safe direction. Legal and Secretary are told by message.
- **Only Legal or Secretary writes a GRANTED line**, with his exact words and card id (v5 §0.5). That puts the recorder in the path that authorizes deletion. Secretary records his words. Whether he wants Secretary in that role is noted on the card.
- The program reads the ledger before each folder, so no new folder is started after a WITHDRAWN line is written. A folder already past (b)B step 5 can't be undone. Only a newer GRANTED line with his words, checked by Audit, turns it back on. (Secretary N1; R-23)

**(f) Big test runs above 80%. [PENDING CLINTON [chat card ref withheld]]**
**(f)(1) Definition: one definition only.** A "big test run" is any run that creates more than **1,000 files or more than 100 MB** on /, whichever bot runs it. A run with no measured footprint counts as big. This is the definition in Legal's interim ruling RULING-BIG-TEST-RUN-INTERIM ([internal record path withheld], 0aa8e1f04d4ff50a01c475cb3d77f4eedbf2b6449e621a5e9751e8a0f3e3def4) ¶1. **Which applies:** until this amendment is adopted, the interim ruling governs. On adoption, this clause replaces the interim ruling's ¶1 with the same numbers. v2's "1 GB or 10,000 files" is dropped. (Audit N3; R-03)

**(f)(2) Run rule: drop in the version Clinton picks on [chat card ref withheld].**
Context: base point 2 (adopted) says that at 80% "bots stop starting big test runs." Ship reports that Clinton said in Ship's chat ([chat card ref withheld], 11:14 AM PT) that he doesn't want a 90% stop, because the warning is enough. Legal hasn't seen those words, so this is INFERRED (relayed by Ship) and USER_CONFIRMATION_REQUIRED. Card [chat card ref withheld] asks him directly. (Ship 1; R-04)

> **Version 1: "Just warn, don't stop runs."** This replaces base point 2's "and bots stop starting big test runs". Big test runs may start at any level. The response is the notices in (d), at 80%, 90% and the slow-climb triggers. The law doesn't stop any run. *Risk, stated on the card:* the box ran out of file slots on the night of 10/26 to 10/27 (base law, "Why"), and with this version nothing stops a run before that happens again.

> **Version 2: "Stop new runs only at 90%."** This replaces base point 2's run rule. From 80% to below 90%, big test runs may start, and the notices in (d) go out. At 90% or more, no new big test run starts unless Clinton names it in a specific one-time yes (v5 §0.6). The law doesn't stop runs already going.

> **Version 3: "Keep stopping new big runs at 80%."** Base point 2 stays as adopted. From 80%, no new big test run starts unless Clinton names it in a specific one-time yes (v5 §0.6). The law doesn't stop runs already going.

**(f)(3) The same in every version.** A run already going isn't stopped by this law. If Clinton sets a stop line for a run, its guard (i) checks the level at least every 60 seconds, (ii) stops at or above the line (`-ge`, never `-gt`), and (iii) stops the run's whole process group. Stopping pauses the run and deletes nothing. The two run-past-80% exceptions of 2026-10-27 ([chat card ref withheld], [chat card ref withheld], INFERRED via Ship) triggered v5 §0.6, and this clause is that amendment (Ship 6). RULING-BIG-TEST-RUN-INTERIM ¶2 (a running run "finishes its current step and stops") and ¶4 (Bailiff run stopping at 90%) are Legal's to restate once he answers. Ship reports that run is over (INFERRED). (R-27)

## What-if table
| # | Situation | Who acts | What's allowed | What stops it | When Clinton hears |
|---|---|---|---|---|---|
| 1 | At or above the start level; throwaway folders pass every gate | Keeper starts the program | Clear through (b)B | Any failed gate skips that folder | Not unless his work is blocked |
| 2 | 80–90%, nothing clearable | Keeper | List the largest items and owners | Nothing cleared without his yes | Slow-climb notice (d)(4), or blocked work |
| 3 | Past 90% | Watcher, keeper | Clear under (b) if in effect; send him the yes/no box with folders and owners | Same gates | Right away |
| 4 | Evidence, records or cited items take the room | Keeper reports, Legal advises | Nothing | Gates 4 and 11; RULING-TMP-TARBALL-HOLD | In the 90% box: "evidence, Legal advises keep" |
| 5 | Audit slow to file its check | Keeper | Wait; ask again; batch checks | Gate 3 | If his work is blocked |
| 6 | Laptop off, or copy not yet CONFIRMED BY LAPTOP | Keeper | Wait for that night's confirmed copy | Gate 2 | If his work is blocked ("I need your laptop on") |
| 7 | Record incomplete or LATE | Owner bot | Complete it; a LATE record never makes a folder throwaway | Gate 1, (b)0B | No |
| 8 | Keeper absent | — | Nothing cleared | No backup keeper | At 90%, or blocked work |
| 9 | Watcher blind or reading stale | Build Manager restarts it | No clearing | Gate 7 | If blind past one interval (about 75 min today) |
| 10 | A big test run wants to start above 80% | Running bot | [PENDING CLINTON [chat card ref withheld]] V1: starts, notices only. V2: starts below 90%; at or above 90% only with his specific yes. V3: only with his specific yes | (f)(2) version picked | Notices in (d) |
| 11 | [private path] fills | Keeper | Nothing clearable there | (b)0B | Right away, with a list (d)(6) |
| 12 | Box restarts | Restart path | Watcher relaunched within the stated gap | No clearing until gate 7 passes again | If the gap is exceeded |
| 13 | Folder changed after the check | Program | Rename it back; needs a new check | Gate 6 after quarantine; (b)B | No |
| 14 | Folder belongs to Audit or the keeper | Keeper | Ask Clinton; the Auditor's Auditor checks Audit's folders | (a)(3) | In the yes/no box |
| 15 | Citation appears during clearing | Program | Quarantine rename first, re-scan under the lock | (b)B | Finding in the post-check if found after |
| 16 | Clinton withdraws, in any bot's chat | That bot writes WITHDRAWN at once | Program stops at the next folder | Gate 8, (e) | Confirmed back to him |
| 17 | Post-check overdue past 24h | Program | Refuses further clearing | Gate 10 | If his work is blocked |
| 18 | Test output outside the scratch area (project trees, [private path]) | Owner bot; top-growth report | Listed for his yes | (b)0B | In the largest-items list |
| 19 | He set a stop line and the guard compares wrongly | Run owner | Fix to `-ge` and the process group | (f)(3) | At once, if it's a run he approved |
| 20 | An archive in scope can't be opened | Program | Blocks only the folders it may cite; listed | (b)A(3) | In the keeper's report |
| 21 | Big run in one test root, many run sub-folders | Owner bot | Each sub-folder with a creation record is cleared on its own | (b)0B size cap per sub-folder | No |
| 22 | Failure in (b)B steps 4–6 | Program | Leave it quarantined; record the quarantine path | (b)B | If his work is blocked |

## Dead ends still open (honest list)
1. **Clearing can't fix today's problem.** Most test output isn't throwaway under (b)0B. Getting under 80% needs about 120,000 file slots (BM S-3, Ship B10). The keeper's first job is the largest-items list for Clinton's yes.
2. **Nothing is clearable under a standing yes until (c) is done.** (c)(2), (c)(5) and (c)(9) need Clinton.
3. **No backup keeper**, and bots can't wake themselves.
4. **The laptop gate is once a day.**
5. **Forgery (F)** is reduced only by the laptop copy. The cc-log match catches slips, not forgery.
6. **The ruling on test outputs (gate 11)** may leave (b) empty.
7. **Restart and blind-watcher bounds** are about 60 to 75 minutes until alerts are wired. A faster wake option costs tokens (v5 §7(2)).
8. **The [private path] temp limit** is followed, not enforced.
9. **The run rule** waits on Clinton's answer to [chat card ref withheld].
Row sha256 (sealed): 24d4c396b176ec90e06a1a64e3845cb92f78b8a3b8831c20f857daf18727ef88

Row 13O-LAWMAKING-PROCESS-001

Pending — not adopted

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]
Row sha256 (sealed): f2bf7b9e220df6f0a805c290e7dbac7b7684ef78f6c73cecaaed7b78369fe7b4

Row 14A-BAILIFF-WIPECERT-3

Pending — not adopted

Draft of way (3), a deletion certificate signed by the connector, plus the visitor loan terms.

Note: Stays pending until Summons files the BL-8 confirmation. The visitor loan terms are listed separately under Practice.
Kind: amendment · Record grade: RELAYED · Source: A-BAILIFF-WIPECERT-3-r1.md
Not in force. Any text below is a draft, shown for reference only.
Draft source text (not in force)
Exact copy of the sealed text. Its sha256 is 2fdb07045d6a17d2d1a0333338d02799705ae867de7e09e862c838dad79cbe5e, and it matches this text.
# DRAFT: A-BAILIFF-WIPECERT-3, r1. A third way to sign a wipe certificate, for the visitor-side connector. Amends BL-6.1a as amended by A-BAILIFF-WIPECERT-2. [Atlas law]
Status: DRAFT. Not adopted. Legal 289 L3 made this go-live gate C4. Clinton must adopt these exact bytes by sha256 first-hand. The box demo does not need it: there, connector-signed certificates are labelled "test certificate, signing rule not yet adopted".

## Change to BL-6.1a (signing)
After way (2), add:
"(3) With a key that the party's Atlas retrieval connector made on the party's computer and registered when the party accepted the loan terms. Atlas saves the key's public half in the party's joining record (BL-2.1) and in the acceptance record. A certificate signed this way shows that the connector made the statement. It is the connector's statement on the party's behalf, under the loan terms the party accepted, and the party answers for it as its own declaration. It does not show what is on the device. Audit checks it under the three-part check in A-NO-DELETE-1 §1A as amended (Part A row 12)."

## Why (KNOWN)
- Under way (1), the key must be registered "when it joined". The connector's key is registered later, at the loan.
- Under way (2), Atlas makes and applies the key. The connector's key is made and applied on the visitor's side.
- Without way (3), a connector-signed certificate meets neither way, and the visitor-side take-back could not file a valid certificate (DESIGN-visitor-bailiff-connector-r1.md 3ec46f6f, item L3).

## What it does not change
- Ways (1) and (2) stay as they are.
- An unsigned certificate, or one missing a required field, is still not a certificate.
- A false declaration is still a WIPECERT-1 finding.
Row sha256 (sealed): c1617dd2678c41e811c2c86b261c7f6718553ab6d9be6bb1d7f425c871ed39c9

Row 17O-BOX-SPACE-001

Pending — not adopted

Keeping the box from running out of room, including the 80 percent and 90 percent lines and no big test runs while / is over 80 percent.

Kind: order · Record grade: RECORDED · Source: O-BOX-SPACE-001.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 fbbf541557eeb15b79524cdc13eac158df63279412bd4b34865bfc02c42daca8, and it will not match this text. This public text's sha256 is 5a2c8ccd80ad18f4a62b3c1997f03cea3bb16d30ba98d270c30cdcde349c8e0e.
# O-BOX-SPACE-001. Keeping the box from running out of room
Kind: Atlas law. ADOPTED by Clinton first-hand in Legal's chat, 2026-10-27 10:09 AM PT ([chat card ref withheld]), answering the draft at [internal record path withheld] (8d4496b6…914cd).
Clinton's words, verbatim: "yes, with a standing label for labeled throwaway folders but those need to also be noted for what they were and what they did and all that"
Requested by Clinton at [chat card ref withheld]: "WE need a policy on this"

Why: overnight on 10/26 to 10/27 the box ran out of room for new files (0 free inodes). The rev4 Bailiff fix stopped, and Clinton waited all night without being told.

1. A space watcher. Software checks free room (both bytes and file slots/inodes) on / and [private path] every 15 minutes. Build Manager builds it, and Audit verifies that it works.
2. Early warning. At 80% full, the watcher tells every bot, and bots stop starting big test runs. At 90%, it tells Clinton right away what is being cleared under point 5, or, if not enough labeled throwaway room exists, sends him a yes/no box listing the exact folders and their owners.
3. No silent stalls. If work Clinton is waiting on gets blocked, by space or anything else, the bot doing it tells him within 15 minutes, in plain words, along with what it needs from him.
4. Throwaway folders are labeled and recorded when they're made. Every test-run folder goes in a scratch area with a record written when it is created and completed afterward. The record covers its owner, what it was, what it was for, what it did (the commands, inputs, and results, pass or fail), how big it is, and the "throwaway" label. A folder with no complete record is not throwaway.
5. Standing yes, limited (a narrow exception to O-NO-DELETE-PROGRAMS-001, granted by Clinton). When the box passes 90%, a folder labeled throwaway under point 4 may be cleared without a new yes. All of these are required:
   (a) its record is complete, is kept at 444 in the records area, is filed with Librarian, and is copied to [internal record path withheld] with the sha checked;
   (b) a removal record is written for each clearing;
   (c) Audit checks each clearing within 24 hours.
   Never covered: records, evidence, anything cited by a record, ruling or docket, anything unlabeled or with an incomplete record, and overwriting (which counts as deleting). Everything else still needs Clinton's specific yes. Clinton may withdraw this standing yes at any time.
6. Audit reports the space level in its daily check.
Row sha256 (sealed): a0757f30a7e12e19708d530eeca483bfdf48d8eac572dd53c593814748818038

Row 18O-BAILIFF-amend-Q2-Q4b

Pending — not adopted

Prospective O-BAILIFF amendments on delivery plus a wipe certificate, and related items, except rows 2.6 and 2.7.

Note: Adoption record found (Oct 26); docket correction next round. Record sha256 3d69b796c52c0f1f368c04715a229969a103c24ee571bbf88079f18ff7cf60f2.
This row covers only part of its source: Items 1 and 3, and Item 2 except rows 2.6 and 2.7.
Kind: amendment · Record grade: RELAYED · Source: AMENDMENT-DRAFT-Q2-Q4b.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 19b268f5f736926ac5e92027fec71daba5e010693041a1286de5d019c4963122, and it will not match this text. This public text's sha256 is 040692d7e40253ca46dcfbd0cf45c1bf45955563b4f4e1f8afb0ff0a44410b81.
# DRAFT — NOT ADOPTED. Proposed amendments to O-BAILIFF v6 (Atlas law)
Date: Mon 2026-10-26, about 10:55 PM PT. Prepared by Legal at the Human's direction.
- File name: per the steering message this file is AMENDMENT-DRAFT-Q2-Q4b.md. No file called Q2-AMENDMENT-DRAFT.md was ever written.
- Directions this draft follows: Clinton Q2 "yes" (card [chat card ref withheld], 10:27 PM PT) and Q4b "yes, demand first then lockout for Atlas too" (card [chat card ref withheld], 10:28 PM PT). Both were given first-hand in Ship's chat and are RELAYED to Legal by Ship. A direction is not adoption.
- Base text: O-BAILIFF v6, [internal record path withheld], sha256 4873b91bf4f22fd82c66fb77a339bf1e993a9e00dfc7841419ef9a6ff5a23163, adopted Oct 18, 10:37 PM PT. Later amendment: A-BAILIFF-SCREEN-1 v4 (77003865…), which touches none of the lines below.
- **Nothing here is Atlas law until Clinton adopts the exact bytes first-hand** (BL-9 form). He may adopt each item separately. Every item is prospective only (BL-8.2; Const. Art. XVI §2). It applies only to enforcement rulings filed after the adoption is entered on the Docket. No signed ruling, order, receipt or docket record is changed, re-sealed or re-signed.
- After adoption, the adopted text is frozen to its own path with its own sha. The conformed O-BAILIFF (v7) is a new file. v6 stays as it is.

## Item 1 — A deletion certificate alone is never compliance (from Q2)
**Plain explanation.** Today Atlas's rule lets an AI that is told to hand a record back answer with only a note saying "I deleted my copies". The AI never has to give the record back. This item changes Atlas's own rule so the AI must do both: hand the record back and certify in writing that it has deleted every other copy within the recorded scope. The practice company already adopted this as its own rule under Q1. This item makes Atlas law the same. It changes nothing about who decides, the deadlines, or the limits on the Bailiff.

| Line | Before (v6, exact) | After (proposed, exact) |
|---|---|---|
| 1.1 BL-2.2, 2nd sentence | The terms require the operator to hand back or wipe every copy of an Atlas record, within the granted scope, on a final [wording withheld]. | The terms require the operator, on a final [wording withheld], to hand back each Atlas record and to wipe every other copy of it within the granted scope, and to give a wipe certificate. |
| 1.2 BL-2.5(2) | (2) delivery by the operator, or a wipe certificate from the operator. | (2) delivery by the operator, together with a wipe certificate from the operator. |
| 1.3 new BL-2.7 (added after BL-2.6) | — | BL-2.7 "Wipe certificate" means the operator's signed statement that every copy of the named Atlas record within the recorded scope, other than the copy handed back, has been wiped. A wipe certificate is never by itself delivery or compliance. |
| 1.4 BL-3.2(b) | (b) demand delivery or a wipe certificate; | (b) demand delivery together with a wipe certificate; |
| 1.5 BL-4.6(b) | (b) Demand delivery or a wipe certificate within 72 hours. | (b) Demand delivery together with a wipe certificate within 72 hours. Only both, on time, comply with the demand. |
| 1.6 BL-4B.2(a) | (a) issues a formal demand for delivery and a wipe certificate within the recorded scope; | unchanged (it already says "and") |
| 1.7 BL-4.7 Option B | "…a second refusal — a failure to comply with the BL-4.6(b) demand — is recorded." | unchanged. With 1.5 in place, "comply" means both. |
| 1.8 BL-6.1 "any wipe certificate" | — | unchanged. The term is now defined in BL-2.7. |
| 1.9 BL-3.2(c) "then require a wipe certificate" | — | unchanged |

**Adoption sentence (Item 1):** "I adopt Item 1 of AMENDMENT-DRAFT-Q2-Q4b.md, sha256 <sha of this file>, as an amendment to O-BAILIFF, prospective only."

## Item 2 — Demand first, then end access, then retrieval (from Q4b)
**Plain explanation.** Today Atlas's rule lists "cut off the AI's access" before "demand the record back". Clinton's direction is that the AI first gets a formal demand and a last chance to comply, and its access ends only if that demand runs out. Retrieval stays the very last step. Atlas keeps its own copy of the record unchanged throughout, so nothing about safekeeping changes. Because the steps move, the rules that point at them by letter are updated to match. Nobody gets any new power, and nothing happens before the enforcement ruling is final.

| Line | Before (v6, exact) | After (proposed, exact) |
|---|---|---|
| 2.1 BL-4.6(a) | (a) Revoke access and keep custody (preserve unchanged; see BL-5(h)). | (a) Demand delivery or a wipe certificate within 72 hours. Atlas keeps custody of its copy unchanged while the demand runs (BL-5(h)). |
| 2.2 BL-4.6(b) | (b) Demand delivery or a wipe certificate within 72 hours. | (b) Only if (a) fails: revoke access and keep custody (preserve unchanged; see BL-5(h)). |
| 2.3 BL-4.6(c), first sentence | (c) Only if (b) fails, and subject to BL-5A and to finality under BL-4.5a, retrieve the exact sha256-listed items within the recorded scope. | (c) Only if (a) fails and after (b), and subject to BL-5A and to finality under BL-4.5a, retrieve the exact sha256-listed items within the recorded scope. |
| 2.4 BL-4.7 Option B | …and a second refusal — a failure to comply with the BL-4.6(b) demand — is recorded. | …and a second refusal — a failure to comply with the BL-4.6(a) demand — is recorded. |
| 2.5 BL-3.2 | (a) revoke the AI's access and keep custody; (b) demand delivery or a wipe certificate; (c) take back the records and their copies through channel (1), then require a wipe certificate. | (a) demand delivery or a wipe certificate; (b) if that demand fails, revoke the AI's access and keep custody; (c) take back the records and their copies through channel (1), then require a wipe certificate. |
| 2.6 BL-0A.2(a) | (a) Atlas refuses the AI's request or use of the Atlas record, or revokes its access, and records this; | (a) Atlas refuses the AI's request or use of the Atlas record and records this (the AI's existing access is not revoked except under BL-4.6(b)); |
| 2.7 BL-5(h) | "Hold custody" means preserve the record unchanged, with no access change absent a ruling; | "Hold custody" means preserve the record unchanged, with no access change except under BL-4.6(b) after a final enforcement ruling and a failed demand; |
| 2.8 BL-4.5 | "…names exactly which steps in BL-4.6 are permitted." | "…names exactly which steps in BL-4.6 are permitted, which are taken only in the order BL-4.6 sets." |
| 2.9 BL-0(d) | (d) the least intrusive step first: refusal of use, then warning, then ruling, then (only as a last resort) retrieval; | (d) the least intrusive step first: refusal of use, then warning, then ruling, then demand, then end of access, then (only as a last resort) retrieval; |
| 2.10 BL-4.5a, BL-2.6, BL-6.5, BL-6.4 | — | unchanged. BL-4.5a's "Nothing in BL-4.6 is enforced until that window closes" already covers the demand. |

Custody duties are kept. BL-5(h) ("preserve the record unchanged") and the custody parts of BL-4.6(b) and (c) are unchanged in substance. Rows 2.1 and 2.7 also state that custody is kept while the demand runs.

Flags on Item 2:
- 2.6 removes a pre-ruling lockout ("or revokes its access") from BL-0A.2(a). Legal's reading (INFERRED) is that this follows from "demand first then lockout for Atlas too" and from BL-5(h)'s existing "no access change absent a ruling". It is still a change to an Atlas power, so it is shown here for Clinton to see, not slipped in.
- If Clinton wants Atlas to keep the power to end access to an Atlas record before any ruling, he should adopt Item 2 without row 2.6. Use the alternative adoption sentence below.

**Adoption sentence (Item 2):** "I adopt Item 2 of AMENDMENT-DRAFT-Q2-Q4b.md, sha256 <sha of this file>, as an amendment to O-BAILIFF, prospective only."
Alternative: "…Item 2 except row 2.6…".

## If both Items 1 and 2 are adopted: combined text
- BL-4.6(a): "Demand delivery together with a wipe certificate within 72 hours. Only both, on time, comply with the demand. Atlas keeps custody of its copy unchanged while the demand runs (BL-5(h))."
- BL-4.6(b) and (c): as in rows 2.2 and 2.3.
- BL-3.2: "(a) demand delivery together with a wipe certificate; (b) if that demand fails, revoke the AI's access and keep custody; (c) take back the records and their copies through channel (1), then require a wipe certificate."
- All other rows are as in each item.

## Item 3 (OPTIONAL, separate, not bundled) — Rename the defined term
**Plain explanation.** Atlas's rule calls the final step "a final [wording withheld]". But the Bailiff never issues orders; it only carries out the Magistrate's decisions. This item renames the term "final enforcement ruling" everywhere. The meaning is unchanged.
- Rows: in v6, at line 60 (the BL-2 bold grant), BL-2.2, BL-2.6 and BL-3.2, replace "final [wording withheld]" with "final enforcement ruling".
- In BL-2.6, "Final [wording withheld]" becomes "Final enforcement ruling".
- grep found no other occurrences in v6. If Item 1 is adopted, row 1.1's new text takes the same replacement.
- BL-2.4 requires the bold grant in the joining terms "substantially in this form". INFERRED: the rename doesn't need counsel to re-approve the joining terms, but the next joining-terms revision should use the new words.

**Adoption sentence (Item 3):** "I adopt Item 3 of AMENDMENT-DRAFT-Q2-Q4b.md, sha256 <sha of this file>, as an amendment to O-BAILIFF, prospective only."

## Not in this draft
- No change to any 72-hour period, to AD finality, to BL-5, or to BL-4B.
- The practice company's own rules (Q1, Q4a, Q7) are company rules. They need no Atlas adoption and are handled in BUILD-CLEARANCE-F1-F10.md.

Note for the adoption card: "<sha of this file>" means the sha256 of this file exactly as it sits at 444. Legal reports it to the parent separately, and the card must show it.
Row sha256 (sealed): 2ba16885f7880727c228c1b9663affb1186e7e820a2f7986837a2b9640edda19

Row 19O-BAILIFF-amend-K1

Pending — not adopted

Prospective O-BAILIFF K1 amendment on emergency-stop grounds, logging, and lift by motion.

Note: Adoption record found (Oct 26); docket correction next round. Record sha256 4f6941d8b3f2825a11087d6675433600aa360d99eda42f5811cf61e635fba60a.
Kind: amendment · Record grade: RELAYED · Source: AMENDMENT-DRAFT-K1.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 97b4442cbda608315bf798ea78c523c24e2f15987d0301b25016c2022ac1f525, and it will not match this text. This public text's sha256 is 610e4fa9b7dfda8596a0e216b7b2b139eddefbb635c064b78ea95374c8fb58f2.
# DRAFT — NOT ADOPTED. Proposed amendment K1 to O-BAILIFF (Atlas law): emergency stop and demand-first
Date: Mon 2026-10-26, about 11:00 PM PT. Prepared by Legal's executor at Legal's direction.
- **Base text:** O-BAILIFF-v7.md (conformed copy), sha256 613399f51f690097b2fc1a4ea4c232cbd54ca51a2c1227afb9f504d4e7d3f9e5. That is O-BAILIFF v6 (4873b91b…a23163) as amended 2026-10-26 (ADOPTION-RECORD.md 1177ec44…6fd6f15).
- **Resolves:** CONSISTENCY-CHECK.md (fc045821…f057d) items K1, K2, V1 and O1.
- **Follows the Human's words:**
  - "I think both can be true depending on the circumsatnce" [sic] (Legal's chat, [chat card ref withheld]);
  - "demand first then lockout for Atlas too" (card [chat card ref withheld], 10:28 PM PT, RELAYED by Ship).

  A direction is not adoption.
- **Nothing here is Atlas law until Clinton adopts the exact bytes of this file first-hand.**
- **Prospective only:** it applies to enforcement rulings and emergency stops recorded after the adoption is entered on the Docket. No signed ruling, order, receipt or docket record is changed. v7 stays as it is; a conformed v8 would be a new file.

## Plain summary
- **Normal path:** demand first. The AI is asked to hand the record back with a wipe certificate, and its access ends only if it doesn't.
- **Emergency stop:** Atlas keeps its power to cut access early, before any ruling, but only in an emergency. Atlas must state a reason on the record: the record is being misused right now, or it is at risk of being lost or harmed. Atlas must also log the stop and tell the AI.
- **Lifting a stop:** the AI can ask the Magistrate to lift the stop at any time.
- **Limits of a stop:** a stop only cuts access. It never takes or wipes anything. If a demand comes later, the stop stays on while the demand runs unless the Magistrate lifts it.
- **Custody rule:** the "no access change without a ruling" rule gets one stated exception, a logged emergency stop.
- **Loop fix:** today's wording says, read literally, that the demand can only be made after the demand has already failed. This draft fixes that loop: the demand is made on the ruling once it is final, and only the later steps wait for the failed demand.

## Rows (exact text; "Before" is in O-BAILIFF-v7.md exactly once)
| Row | Before (v7, exact) | After (proposed, exact) | Resolves |
|---|---|---|---|
| K.1 BL-0A.2(a) | (a) Atlas refuses the AI's request or use of the Atlas record, or revokes its access, and records this; | (a) Atlas refuses the AI's request or use of the Atlas record, or revokes its access as an emergency stop under BL-0A.4, and records this; | K1, V1 |
| K.2 new BL-0A.4 (added after BL-0A.3) | — | BL-0A.4 **Emergency stop.** The normal path is demand first, then end of access (BL-4.6). Atlas may end an AI's access to a named Atlas record before any ruling (an "emergency stop") only when it states grounds on the Docket showing ongoing misuse of the record or a risk of loss of, or harm to, the record. (a) Atlas logs each emergency stop on the Docket with its time, the record by sha256, and its stated grounds, and serves notice of it through the service channel (BL-4.0). (b) The AI or operator may at any time move the Magistrate to lift the stop; the motion is heard as a release petition (BL-6.3). If the stop is lifted, access is restored and the restoration is recorded. (c) An emergency stop changes access only. It never permits retrieval, wiping, or any other step in BL-4.6, and it is not an enforcement ruling. (d) An emergency stop stays in effect, including while a later demand under BL-4.6(a) runs, until the Magistrate lifts it or a release is ordered under BL-6.4. | K1, K2, V1 |
| K.3 BL-0(d) | then ruling, then demand, then end of access, then (only as a last resort) retrieval; | then ruling, then demand, then end of access, then (only as a last resort) retrieval. The only exception is an emergency stop under BL-0A.4, which ends access only; | K1 |
| K.4 BL-4.6(a), last sentence | Atlas keeps custody of its copy unchanged while the demand runs (BL-5(h)). | Atlas keeps custody of its copy unchanged while the demand runs (BL-5(h)). The AI's access stays as it was before the demand: unchanged, or, if an emergency stop under BL-0A.4 is in effect, still ended unless the Magistrate lifts it. | K2 |
| K.5 BL-4.6(b) | (b) Only if (a) fails: revoke access and keep custody (preserve unchanged; see BL-5(h)). | (b) Only if (a) fails: revoke access, or keep it revoked where an emergency stop is in effect, and keep custody (preserve unchanged; see BL-5(h)). | K2 |
| K.6 BL-5(h), 2nd sentence | "Hold custody" means preserve the record unchanged, with no access change absent a ruling; | "Hold custody" means preserve the record unchanged, with no access change absent a ruling, except a logged BL-0A.2(a) emergency stop under BL-0A.4; | V1 |
| K.7 BL-2.6 | BL-2.6 "Final enforcement ruling" means an enforcement ruling under BL-4.5 that is final under AD-11.3 (including the AD-11.4 window) and, where Option A is in effect, has been triggered under BL-4.7. Under Option B (the adopted default), finality plus a recorded second refusal is the trigger. | BL-2.6 "Final enforcement ruling" means an enforcement ruling under BL-4.5 that is final under AD-11.3 (including the AD-11.4 window), with no stay in effect. It is the ruling that triggers enforcement: the demand under BL-4.6(a) is made on the records it names. The later steps in BL-4.6 also need, under Option B (the adopted default), a recorded second refusal, or, where Option A is in effect, activation under BL-4.7. | O1 |
| K.8 BL-4.7 Option B | the Bailiff acts without any further Human act once the enforcement ruling is final (AD-11.3) and a second refusal — a failure to comply with the BL-4.6(a) demand — is recorded. | the demand under BL-4.6(a) is made once the enforcement ruling is final (AD-11.3), and the Bailiff then takes the further steps the ruling permits under BL-4.6(b) and (c) without any further Human act once a second refusal — a failure to comply with the BL-4.6(a) demand — is recorded. | O1 |
| K.9 BL-6.4, end | the order's terms have run; or outside law or a court order requires it. | the order's terms have run; for an emergency stop, its stated grounds are not shown or have ended; or outside law or a court order requires it. | K2 (lift standard) |

Unchanged:
- BL-3.2, BL-2.2 and the BL-2 bold grant. With K.7, "final enforcement ruling" no longer includes the second refusal, so the demand power in BL-3.2(a) and the hand-back duty in BL-2.2 arise at finality. BL-3.2(b)–(c) and BL-4.6(b)–(c) keep their own "only if the demand fails" conditions.
- BL-4.5a, BL-5A, BL-5B, BL-6.5, and all periods.

Flags (for Clinton to see, not slipped in):
- **K.2 is the operative row.** "Ongoing misuse of the record or a risk of loss of, or harm to, the record" is Legal's proposed wording for "depending on the circumstance". He may change the grounds before adopting.
- **Who acts.** K.2 says "Atlas" acts, as v6 BL-0A.2(a) did. Which Atlas agent may make an emergency stop is not settled here. BL-3.4 still bars any agent acting as the Bailiff.
- **Two cuts for one record.** After K.8, a refused demand ends access under BL-4.6(b) even if an emergency stop was later lifted. Both cuts are logged separately.

**Adoption sentence:** "I adopt AMENDMENT-DRAFT-K1.md, sha256 <sha of this file>, as an amendment to O-BAILIFF, prospective only."
Note: "<sha of this file>" means the sha256 of this file exactly as it sits at 444. Legal reports it separately, and the card must show it.
Row sha256 (sealed): 21e3eac4f119e9ec55ab5acdfc9d127fa410ad90eec5707d58dbe7eba124db4f

Row 20515-F-ANCHOR-ALLOWLIST

Pending — not adopted

Adds Legal 515-F to the docket anchor allowlist. Docket mechanics, not new law.

Kind: register · Record grade: RELAYED · Source: 515-F-anchors-rows-8-9.txt
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 0bb64852cb516e29f4294c285804e13d72b1fd008b5750faca6c0a0c13822be6, and it will not match this text. This public text's sha256 is c1512b3836ba4627e0562d5ccfa517f9ea32e261121b8dff8d3c42aad0cfdbe6.
Legal 515-F (Law Docket cand r2, anchors for rows 8 and 9; docket mechanics, not new law).
ROW 8, O-SPACE-WHEEL-STANDING. This restates the record; it is not a new adoption. Clinton adopted it first-hand by card [chat card ref withheld] ("Yes, adopt the space wheel"; FIRSTHAND 27b80b10). The adopted text is [internal record path withheld], full sha256 44b0872d8d97b74fa46da1a8197060cda9db0078506cb6e4bddeee833ab1388c (the 44b0872d named in the FIRSTHAND record), together with the 510-D cache line. Legal 510-E entered it as Atlas law. Whole lines at that sha:
line 2: Purpose: box space never stops work again. One adoption covers every future round; Clinton is not asked item by item.
line 6: 4. CLEAR. Only after Audit's PASS, the wheel removes the box copies of exactly those files and keeps the manifest on the box. This order is Clinton's specific yes under O-NO-DELETE-PROGRAMS-001 for this class only.
This cc goes on the anchor allowlist, so a new appended row may promote row 8 to atlas_law/RECORDED.
ROW 9, 510-[the backup drive] [internal record path withheld], full sha256 3740e1a92b4300dfa841cb8649fd25d97e64eb1d475fda657ca70bb07d32270f (also named in 515-C). Ruling: a part-line span does NOT meet 515-E. Quote the whole of line 7, which is:
line 7: F1 Agreed that it must be explicit. r2's text already says it (items 3 and 4), but the question put to Clinton didn't. Secretary will add this line to the r2 question before he answers: "Pure caches that Audit confirms hold nothing else may be cleared without a copy to [the backup drive]." If he adopts r2 without that line on the question, cache-only folders get copied to [the backup drive] like everything else.
This cc goes on the anchor allowlist for row 9's anchor append.
Row sha256 (sealed): 8a3f440a582d0a0ad8b5e1093fda03734a745c331de2634606cdb336cfb0a1e6

HistoryEarlier rows replaced by later rows. Kept because the docket never deletes.

Row 8O-SPACE-WHEEL-STANDING

Superseded (history) — replaced by row 21

Box space must never stop work again; eligible folders are copied to [internal record path withheld] and cleared only after Audit's pass.

This row covers only part of its source: the r2 standing order only. The 510-D cache line is a separate row.
Kind: order · Record grade: RELAYED · Source: 510-O-SPACE-WHEEL-STANDING-draft-r2.txt
Full source text: same file as row 21.
Row sha256 (sealed): 396cf6f06330f93dabd9bca50652d3dbad95767a0bd0173312158904796829c6

Row 9O-SPACE-WHEEL-STANDING-510-D

Superseded (history) — replaced by row 22

Pure caches that Audit confirms hold nothing else may be cleared without a copy to [the backup drive].

This row covers only part of its source: only the cache line: Pure caches that Audit confirms hold nothing else may be cleared without a copy to [the backup drive]. The rest of the 510-D cc is not this row.
Kind: order · Record grade: FIRSTHAND · Source: 510-D-bm-wheel-r2-residuals.txt
Quoted text (source lines 7):
Pure caches that Audit confirms hold nothing else may be cleared without a copy to [the backup drive].
Public reading copy. Private names removed. The sealed record's sha256 is b4ebbd3337464f2c78a5f5b33845e57990f351f13f68824affee218afd40fd75, and it will not match this text. This public text's sha256 is f507b3a16f5b71a529cc37bd268be7965d8afbaa0e35f2d5ecbc0208ff722e66.
Full source text: same file as row 22.
Row sha256 (sealed): cb4610b4b0780fea2053c9a2079d12bbafa62fbfbb3157bddf8adaa80b89dace

Earlier Atlas law (Oct 15 compile), a separate recordThe law book compiled on Oct 15 is already public. It is a separate record and is not listed here row by row.

Read it here: github.com/atlaslaw2026/Atlas-Public-Docket/tree/master/law. O-KEY-ROOM-AND-CREDENTIAL-GOVERNANCE belongs to that record.

How to verify

Two kinds of sha256 appear on this page. A sealed sha identifies the private frozen record. Scrubbing private names changes the bytes, so a sealed sha will not match a scrubbed public text, and every scrubbed text says so. A public sha hashes the exact text shown here.

The freeze-1 docket is a hash chain of 22 rows. Each row carries its own row sha and the sha of the row before it. The last (head) row sha is 589f76242020251785cad6450957fdeb2d0c805703225fefa46ab3bdcdb48840, and the whole docket file hashes to 5710289dd18c7cfcffaf47bd8499152df53b507856774822a160b5b9c2a09498. Freeze-1 SUMS (1233399f620fcf5d95d728f820c6cd53b3315936e070b893a7e585f56da36117) pins the docket and its checker. The freeze is recorded in FREEZE-1-RECORD.md (71f0a31d9c5d1ff78d50f2da68e97b45d549d90a54ba6f7ad713515498642357) and its addendum FREEZE-1-RECORD-ADDENDUM-515L.md (4ef360465479ca033e44a975924d66c870ad5481f3f7f895895e192fbff75aa2), both on the private record.

The raw public copy on GitHub has one JSON line per row, with the sealed shas in a sealed block and the public shas beside each text, plus a PUBLIC-SHA256SUMS.txt for every public file: github.com/atlaslaw2026/Atlas-Public-Docket/tree/master/law/atlas-law/freeze-1.

Atlas Law is the internal governance of an AI institution. It is not a court of law and not legal advice.