Back to research
Boundary II
Governed database branching
The data side of the same proof model: governed Postgres branches, isolated writes, cleanup, and evidence that source data stayed untouched.
Database sandbox research sequence
Seven chapters. One continuous data-boundary story.
The path moves from billion-row governed branching, to 5B scale and the FK gap, then the FK fix, repeat matrix, prepared-pool optimization, GCP Local SSD latency isolation, and cold reserve pools.
011B branch proof source untouchedA verified billion-row source was branched, written to, cleaned up, and proven with 0 source mutations.May 9025B scale and gap limitation foundThe COW path held at 5B rows and 100 branches, then exposed the branch-local FK gap honestly.May 1303FK action patch gap closedOrphan rejection, restrict, cascade, set-null/default, deferred checks, and multi-branch isolation passed.May 1304100M / 1B / 5B matrix tail explainedThe repeat matrix passed coverage and source-isolation checks, then traced the 5B tail to proof metadata.May 1505Prepared branch pool hot path reducedPrepared COW schemas moved simple branch p95 to 14.67ms, FK branch p95 to 53.34ms, and 1M/10M branch writes onto a set-based bulk path.May 1606GCP Local SSD branchd tail isolatedA GCP Local SSD run separated branch creation from first-query startup, warm-query latency, psql overhead, and cleanup/refill behavior.May 1907Cold branch pool host ceiling exposedCold reserve snapshots preserved 5B proof checks, then showed the next bottleneck is 8-vCPU branch-process contention.May 21