8Braid Journal
Follow an argument from first principles to evidence.
Series connect visionary consequences, system architecture, benchmark methods and the objections that sharpen the work.
AI With Authority
Would You Give an AI $100 and Walk Away? · I Would Pay for a Good Counterexample · The Dataset Doesn't Have to Change Hands
Iterating on Navier-Stokes
OpenAI's Navier-Stokes Proof Meets a New Kind of Database · One Loop Inside the Navier-Stokes Blow-Up Proof, Made Measurably Better Twice · The Week Navier-Stokes Moved, and What a Database Company Did About It · 573 Files, Ten Refuted Claims, Three Engine Repairs: What an Archive Review Returns · A Database That Refuses to Record a Conclusion Stronger Than Its Evidence, and Shows You Exactly What Falls When a Premise Does · The Kernel Accepted the Proof. We Audited the Statement, Clause by Clause · One Mathematical Object, Six Views: What a Table of Samples Can Never Ask · Replaying a 150-Gigabyte Proof on a 62-Gigabyte Machine · What a Claim Ledger Must Catch: A Live Case From the Navier-Stokes Frontier · What Attacking a Millennium Problem Taught Us About Our Database
Trust Beyond Ledgers
Benefits With Rules and Accountable Disclosure · What Comes After Blockchain? Money That Carries Its Own Proof · Hand the Regulator the Exact Decision, Byte for Byte, Years Later. Compliance You Replay, Not Reconstruct. · What an Erasure Certificate Can Tell You
Trustworthy AI Data
An Agent Can Only Leak What Its Process Can Decrypt · The Benchmark Nobody Runs: Does Your Agent's Data Tell the Truth? · Agent Memory You Can Actually Deploy: Remembers With Provenance, Forgets on Command, Proves Every Deletion · Show Your Work: Provenance as a Query, Not a Forensic Reconstruction · Stop Your AI Inventing Facts: A Database That Tells the Model Where Every Answer Came From and How Sure to Be · Find the Sanctioned Network the Lists Miss: 17 Unlisted Subsidiaries and One Keystone Entity From 4.28 Million Public Records
Post-Quantum Databases
A Post-Quantum Handshake Protects One Journey. 8DB Seals the Record for Every Journey It Will Ever Take. · Stop Buying Quantum-Proof AES. It Is the Part of Your Database That Was Never Broken. · The 2035 Migration Is Already Scheduled. Is Yours? · We Are Racing Oracle's Online Rekey, and Publishing the Rules Before the Race · Your Backups Are the Quantum Attack Surface Nobody Inventoried. 8DB Inventories Them From the Record and Migrates Them With the Data. · Your Migration Plan Encrypts One Copy of Each Record. Your Stack Holds Eleven. · Your Post-Quantum Migration Has 21 Questions. The Algorithm Answers One. · The Next RFP Question Is About Your Stored Records. Build the Answer, or Embed It · Category 5 Keys in Software, on the Hardware You Already Have, No HSM Required · Your Archive Is the First Quantum Target: Running the G7 Roadmap on Thirty-Year Records · Post-Quantum Cryptography for Stored Data: The Per-Record Cost Is Zero Bytes · M-26-15's Hardest Instruction Is a Database Operation. Here Is How It Runs. · The Database That Reports Its Own Cryptography, Per Dataset, On Demand · The Category 5 Bill Is Paid Once or Paid Per Record. Architecture Decides Which
One Protected Substrate
When the Answer Is More Than Yes or No · When the History Becomes Part of the Key · When the Order Changes the Answer · Replace Six Databases With One Sealed Store: One Migration, One Governance Model, No Seams Left to Breach · A City of Thirteen Million Entities on a Phone, With No JSON in the Hot Path · Stop Buying a Database Per Noun: Modality Is a Projection, Not a Product Boundary · The Next Platform Moat Is Not a Faster Chip. It Is Sealed Intelligence Moving Between Devices, and It Is Built in the Store.
8DB on Apple Silicon
Cut Storage Energy to a Quarter of SQLite's per Gigabyte Written, and Give the Battery Back to Your Users · Private On-Device AI Needs a Store That Never Phones Home: Provenance on Every Fact, Clearance Enforced at Every Hop · One Store Under Every App: 8DB on Apple Silicon, by the Numbers · Faster Than SQLite on the Writes That Matter, With Provenance and Category 5 Sealing SQLite Cannot Give You
Evaluation and Assurance
Every Number on This Site Comes With the Harness That Made It · Entity Resolution You Can Defend in Front of a Regulator: 4.28 Million Records, Every Merge Explained, Identical on Every Run · Make Prompt Injection Harmless to Your Data: Clearance Lives in the Key, So a Hijacked Agent Decrypts Nothing It Was Not Cleared For · Four Claims, One Pinned Artifact: What an Independent Evaluator Should Be Able to Run
Fielded Systems
One Component in the Boundary, No Keys in the Field, and an Artifact for Every Question the Assessor Will Ask · One Sealed Store for Every Shape of Data, and It Works With the Network Gone · Before a Fleet Trusts the Model, It Has to Trust the Data Under It
Model-Independent Data
Replace the Device's Six Data Stores With One Sealed Substrate, and Your On-Device AI Stops Inheriting Fragments