Back to research
Sandboxing boundary

Sandboxing and database branches

Governed database branches, isolated writes, cleanup, and proof that source data stayed untouched.

Articles

Full archive for this boundary.

Database sandbox matrixPublished

Imladri re-ran governed Postgres branches at 100M, 1B, and 5B rows.

A repeat multi-scale matrix showed complete numeric coverage, 20 storage-COW branch samples per scale, 0 source mutations, 6/6 proof checks, and a 5B metadata-tail explanation.

100M p5019.4ms
1B p5030.53ms
5B p5065.17ms
Mutations0 source
Database sandbox fixPublished

Imladri patched branch-local foreign-key actions in governed Postgres sandboxes.

Branch-local FK orphan rejection, restrict, cascade, set-null, set-default, deferred constraints, composite MATCH FULL keys, self-referential FKs, multi-branch checks, and 100-way concurrent FK branches passed with zero source mutations.

FK suite10 tables
Concurrent FK100/100
Proof7/7
Mutations0 source
Database sandbox follow-upPublished

Imladri branched a verified 5B-row Postgres source, then found the next database-agent gap.

A focused sandboxing note: 5B-row numeric coverage, 100/100 concurrent branches, 10M branch-local writes, 0 source mutations, and the branch-local orphan FK limitation found before the fix.

Rows5B
Concurrent100/100
Heavy write10M rows
FK checkgap found
Database sandboxPublished

Imladri branched governed Postgres sandboxes over 1 billion rows with a 24.07ms p50.

A local Postgres scale run proved exact billion-row coverage, twenty copy-on-write database branches, isolated writes, cleanup, and proof export without mutating the source table.

Rows1B
Branch p5024.07ms
Mutations0 source
Proof6/6