ENTITY Documentation Portal
ENTITY test 16 | fresh developer storage evidence | 2026-10-01

Developer storage scenario suite

Six fresh, video-recorded scenarios map the storage advantage envelope instead of presenting one universal compression number.

Read this first: positive reduction means the measured ENTITY representation is smaller than the named baseline. Negative reduction means ENTITY is larger. These are workload-specific engineering measurements.

What developers should take away

Scenario A - scale curve

Vacuumed SQLite current state versus ADAM native factored current state. Positive = ADAM smaller.

RecordsRepetitiveMixedUnique
10051.11%26.81%-25.04%
50051.43%19.66%-55.94%
1,50049.67%8.24%-75.67%
5,00050.34%4.06%-82.11%

Raw JSON | Transcript | Script

Scenario B - value-cardinality break-even

3,000 records with progressively fewer reusable values. First non-saving tested point: 1,000 distinct values.

Value cardinalityFactored vs SQLite
142.18%
341.36%
1041.44%
3039.35%
10035.36%
30024.14%
1000-6.24%
3000-75.10%

Raw JSON | Transcript | Script

Scenario C - relationship density / fanout

25 million actual compact bonds were generated at each fanout. All 500 sampled lookups passed for every row.

FanoutEntitiesMeasured bytesIndex sharevs 768-d float32
125,000,000600 MB33.33%99.22%
212,500,000500 MB20.00%98.70%
55,000,000440 MB9.09%97.14%
102,500,000420 MB4.76%94.53%
201,250,000410 MB2.44%89.32%

Raw JSON | Transcript | Script

Scenario D - vector-dimension crossover

Derived from the freshly measured 4.4 GB / 50M-entity Level-3 representation. Baseline is one float32 vector per entity and excludes vector-database metadata/index overhead.

Vector dimsVector bytesENTITY reductionRelation
163.2 GB-37.50%VECTOR_SMALLER
224.4 GB0.00%EQUAL
326.4 GB31.25%ENTITY_SMALLER
6412.8 GB65.62%ENTITY_SMALLER
12825.6 GB82.81%ENTITY_SMALLER
38476.8 GB94.27%ENTITY_SMALLER
768153.6 GB97.14%ENTITY_SMALLER
1536307.2 GB98.57%ENTITY_SMALLER
3072614.4 GB99.28%ENTITY_SMALLER
Measured crossover: 22 float32 dimensions per entity. Below 22, the vector payload is smaller; above 22, the measured 4.4 GB representation is smaller under this bounded comparison.

Raw JSON | Transcript | Script

Scenario E - retained provenance / history cost

200 entities with monotonic unique updates. SQLite stores final current state only; ADAM also retains event history. The current-state factored projection and authoritative journal are reported separately.

Updates/entitySQLite currentFactored currentFactored vs SQLiteJournal / SQLiteInitial time travel
024,57616,88631.29%18.7xPASS
128,67224,61614.15%28.6xPASS
328,67238,576-34.54%53.9xPASS
1028,67289,815-213.25%142.0xPASS
2528,672172,345-501.09%327.9xPASS
Interpretation: current-state factoring is smaller at 0-1 updates in this workload, but repeated unique history grows the retained state rapidly. The journal ratio is the cost of additional provenance semantics, not an apples-to-apples compression comparison.

Raw JSON | Transcript | Script

Scenario F - known temporal-cycle limitation

This is a targeted regression, not a storage advantage. It reproduced the v0.41 interval-history limitation when a revoked deterministic bond identity is later reused.

EXPECTED_INITIAL={"_id": "0a01152898bb82aed9ffedfbded2f2f81855d14a19fa802ef56e86e3eac25112", "_key": "P-1", "_type": "project", "cost": 100, "note": "initial", "status": "active"}
ACTUAL_AT_INITIAL_SEQ={"_id": "0a01152898bb82aed9ffedfbded2f2f81855d14a19fa802ef56e86e3eac25112", "_key": "P-1", "_type": "project", "cost": 100, "note": "initial"}
DIFFERENCES={"status": {"actual": null, "expected": "active"}}
Known gap reproduced: current-state integrity passed, but the earlier status: active interval was no longer reconstructable after the same logical bond identity cycled. Tracked as ENTITY issue #116.

Raw JSON | Transcript | Script

Evidence bundle

Machine-readable suite record | SHA-256 manifest

Claim boundary: These tests map measured advantages and disadvantages for named workloads and baselines. They do not establish universal compression, universal database replacement, or production performance.