Primary-Source Investigations
The Public Ledger
Executive Order 14158, January 20, 2025. 90 Federal Register 8441. Signed by the President of the United States.
I am reading an executive order published at 90 Federal Register 8441 on January 20, 2025, that establishes the Department of Government Efficiency, and I am telling you that the order is not the story. The rebuttal is the story.
The order folds the United States Digital Service's statutory mandate into a temporary organization reporting to the President. It authorizes the agency's leadership structure through July 4, 2026. The order is filed at 90 Fed. Reg. 8441. It is public. It is reproducible by any reader with internet access. The order does not require my permission to be true.
It is a filed document. It is public. It is dated.
I know how this works because I built the system that tracks how this works. TELOS. The pipeline. The substrate. I built it because I got tired of reading "widely reported" and "many believe" in every article about government overreach and surveillance, and I wanted a machine that would only accept claims with a filing number and an archive location. The machine does not care about my opinion. The machine only cares whether the source is named and filed. But I am the operator, and I am sitting here at 3:47 AM reading an executive order that routes federal payroll through a temporary agency, and I am telling you that the center files its acts and the edge files the center's acts again, and symmetry of filing is the regulatory check the founders attempted in 1789, the Federal Register Act attempted in 1935, and the operator's substrate attempts in 2026, each at a different layer of the stack.
The order routes federal payroll. The mesh routes federal documents. One is the source. The other is the citation.
The mesh is six nodes. Three Android phones nobody wanted, swap meet off Route 30, twenty dollars apiece, cash, no paperwork, the seller's table next to a man selling power supplies pulled out of arcade cabinets. One secondhand Moto G Play, twenty-two dollars, charger included. One Motorola edge with a bricked bootloader, Target electronics-returns bin, thirty-eight dollars — the previous owner tried to flash the carrier-locked partition and lost. One GL.iNet GL-MT300N-V2 travel router, fifty-three dollars with the USB cable, flashed to OpenWrt 19.07. One older laptop pulled from a curb cleanup, spring trash day, zero dollars, eight kilograms of plastic and silicon someone in 2019 considered obsolete. One 8GB-VRAM rig built over a year, RTX 5060 from a Micro Center clearance bin. Total power at the wall: approximately fifty-six watts. Total spend: approximately two hundred and fifty dollars.
The order and the mesh share a substrate the way two boats share an ocean. The order is filed at 90 Fed. Reg. 8441 because the regulatory floor is where coercive acts of the state are made legible to the people subject to them — the entire constitutional theory of the Federal Register, in force since the Federal Register Act of 1935, 49 Stat. 500. The mesh is filed at `Telos/substrate/book_arm/claims.jsonl` because that is where the citizen's pulls of those filings are made legible to anyone who clones the substrate. The center files its acts. The edge files the center's acts again. Symmetry of filing is the regulatory check the founders attempted in 1789, the Federal Register Act attempted in 1935, and the operator's substrate attempts in 2026, each at a different layer of the stack.
The center has datacenters. The edge has a USB cable and a fifty-three-dollar router. The center has compute. The edge has a Python script and a deterministic claim_id. The center has the order's signature line. The edge has the substrate's sha256. The political theology says the president's signature outweighs the hash. The cryptographic mathematics says the hash outweighs the signature. The book picks neither side and files both.
Here is how the mesh routes.
Step one — collect. You acquire the hardware. Cash, swap meet, returns bin, curb cleanup. No SKU, no receipt, no service contract. The device is the device. The device does not need permission to exist.
Step two — flash. The vendor partition is the leash. You cut the leash before you wire the harness. LineageOS 21 onto the Motorolas, signed builds, source on lineageos.org. OpenWrt 19.07 onto the Mango, firmware from openwrt.org, build-target `ramips/mt76x8`. Fedora onto the curb laptop, netinstall ISO mirrored from a tier-one US mirror. And on the Motorola edge — the carrier-locked unit — the unlock happens through `mtkclient`, the open-source MediaTek BROM exploit tool, github.com/bkerler/mtkclient. The tool runs against the MT6765 chipset in BootROM mode. It does not require the bootloader to cooperate. It does not require the carrier to authorize. It is filed code. It is public.
Step three — wire. Tailscale provisions the overlay. WireGuard underneath — Jason A. Donenfeld's whitepaper at NDSS 2017, the protocol resident in the Linux kernel mainline since 5.6. Each node gets a fingerprint, a node key, a magic-DNS hostname — `cricket`, `moto-g-play`, `zombie`, `mango-pineapple`, `bw`, `bw-firme-gate`. The audit log records the first connection per node. Funnel goes live. The endpoint is reachable from any browser on the open web. The encryption stays inside the overlay. The carrier does not see the traffic. The ISP does not see the traffic.
Step four — publish. The pull pipeline writes claims to JSONL at `Telos/substrate/book_arm/claims.jsonl`. Every line is a record. Every record carries a `claim_id` — deterministic sha256 of canonical path plus content. Every record carries a `telos_anchor` field mapping the claim back to a Goal in the book's TELOS. Every record carries a `sources` array — the named, filed, publicly-verifiable primary source the claim is anchored to. The audit log writes a parallel line to `Telos/audit/book_arm.jsonl` — one line per ingest, one per gate pass, one per editorial action, append-only, signed by the running specialist. The public push to `Zombie760/unwarranted-influence` is the operator-confirmation gate before final publish.
The Federal Trade Commission filed the policy case in Nixing the Fix: An FTC Report to Congress on Repair Restrictions, May 2021, ftc.gov — finding manufacturer repair restrictions impose costs on consumers without corresponding safety justification, recommending legislative remedies. The Commission filed the brief. `bkerler` filed the code. The carrier filed nothing. Between the agency brief and the public repository, the leash is cut twice — once in law, once in firmware.
The audit log is a JSONL file. Append-only. One line per dispatch. The schema is the SUBSTRATE.md contract, version 1, dated April 25, 2026. Each line carries `id`, `ts`, `arm`, `specialist`, `task_ref`, `input_hash`, `output_ref`, `verdict`, `verdict_reason`, `supersedes`, `tokens_in`, `tokens_out`, `model`. The `verdict` is one of `pass`, `fail`, `deferred`, `corrected`. A `corrected` line carries the `id` of the line it supersedes. The old line stays on disk. The new line stands next to it. Nothing rewritten. Nothing erased. The history is the history.
The append-only property is the load-bearing one. The file does not `seek` and overwrite. It does not delete a line. It only writes new lines at the tail. A specialist retracting a verdict writes `verdict: corrected` and `supersedes: <prior_id>`; the prior line stays in place. The reader walking the log sees both. The reader sees the correction, what was corrected, who corrected it, when. The log carries the project's mistakes alongside its correct work. The mistakes are not deleted because the mistakes are part of the receipt. A book that erases its retractions is a book the reader cannot audit. A book that carries its retractions on the page is a book the reader can verify. The append-only file is the version-control of the truth.
The substrate is the third filing. The substrate records that on a specific date in San Diego, a thirty-eight-dollar device pulled from a returns bin became a primary-source pull node on the operator's mesh. The substrate records the device fingerprint. The substrate records the unlock action. The substrate records the first sync. Three filings, three layers — the regulator, the maintainer, the operator. None of them required permission from the carrier. None of them required the manufacturer's signature. The chain of cuts is complete. The mesh routes.
One row of the substrate, as it sits on disk:
```json
{"claim_id":"<sha256>","mode":"session_log","claim_text":"Operator built six-node Shadow Mesh from $250 of consumer hardware, drawing ~56W at wall, pulling 606+ primary sources into Telos/substrate/book_arm/claims.jsonl as of 2026-05-17.","sources":["Telos/audit/book_arm.jsonl","gl-inet.com/products/gl-mt300n-v2/","github.com/bkerler/mtkclient","tailscale.com/kb/1223/funnel"],"verification_status":"operator_anchored","timestamp":"2026-05-17T00:00:00Z","telos_anchor":"G3"}
```
That is one line. The store is a sequence of those lines, append-only, newline-delimited. The schema is open. A reader can write a parser in fifteen minutes. A reader can join the `sources` arrays across all rows and produce the citation index in a single pass. A reader can verify the deterministic `claim_id` by hashing the canonical content. A reader does not need the author. A reader does not need the publisher. A reader does not need an API key. A reader needs the file.
The file is on disk. The disk is in San Diego. The substrate that anchors a book about regulatory secession is itself a regulatory artifact — append-only, content-addressable, schema-published, gated by a hard Prime-Directive check at write time. The substrate refuses claims with empty `sources` arrays. The substrate refuses claims with `verification_status: cannot_verify`. The substrate fails the write and logs the refusal to the audit log. Every rejection is a filed record of a sentence that did not make it into the book.
Walk the four cold opens of the book this substrate serves.
Chapter 1 opens at the PJM Interconnection 2025/26 Base Residual Auction, cleared July 30, 2024 at $269.92 per MW-day — a filed document, chosen by the operator, opened to the page before the model wrote a sentence around it.
Chapter 2 opens at Vesting Order 248, October 20, 1942, Federal Register Vol. 7, p. 9097, signed by Leo T. Crowley as Alien Property Custodian — a filed document, chosen by the operator, the chapter's spine before the model wrote a sentence around it.
Chapter 3 opens at the Energy Information Administration's Annual Energy Outlook 2024, Table A2, reference case — a filed projection, chosen by the operator, before the model wrote a sentence around it.
Chapter 4 opens at the operator's session-log substrate — timestamped, authored, reproducible, append-only, on disk, in git, on the mesh — chosen by the operator, the chapter's foundation before the model wrote a sentence around it.
Four cold opens. Four filed documents. Four operator selections. Zero model selections. The model did not pick the PJM auction, Vesting Order 248, AEO Table A2, or the substrate. The operator picked each one. The model wrote the prose. The operator filed the verdict. The audit log records both. That is the methodology. That is the difference between the framework and the autocomplete the rest of the industry calls a product.
The Federal Register publishes daily, Monday through Friday, every business day since March 14, 1936, when the first volume rolled off a Government Printing Office press in Washington under the Federal Register Act of 1935. Ninety volumes between then and now. Each volume runs tens of thousands of pages. Each page, one filed federal action. Each page, a line in a public ledger that has not stopped since the Roosevelt administration. The ledger is the same ledger. The Custodian changes. The administration changes. The line keeps writing.
The mesh does not stop either. The Mango has not been rebooted since I flashed it. The router does not need me to attend to it. It needs me to leave it alone. The repo is public. The mesh is routing. The pattern is filed. The book in your hands is the index card to the archive.
A book is a hand. The hand points. It points at the document. The document is the thing.
The system is not broken. The system is working exactly as designed.
Primary sources: Executive Order 14158 (90 Fed. Reg. 8441, Jan 20, 2025); Federal Register Act of 1935 (49 Stat. 500); FTC Nixing the Fix report (May 2021); mtkclient repository (github.com/bkerler/mtkclient); Tailscale Funnel documentation (tailscale.com); WireGuard whitepaper (Donenfeld, NDSS 2017); OpenWrt 19.07 release notes (openwrt.org); LineageOS 21 release manifest (lineageos.org); Telos/substrate/book_arm/claims.jsonl (606+ operator-anchored claims, May 2026).