Resources
Whitepapers
Long-form technical papers will collect the deeper design arguments behind StrataDB.
Current long-form material
Internals→Architecture→Architecture→
Engine internals
The closest current substitute for a whitepaper: storage, recovery, vectors, testing, and benchmarks.
Storage substrate
The storage layer and how higher-level data capabilities are built above it.
Commits and versioning
How StrataDB records versions and exposes historical reads.
Publication standard
Clear scope
Each paper should state what it proves, what it does not prove, and which release it covers.
Reproducible evidence
Claims need commands, source references, environment details, and raw outputs where possible.
Readable PDF
The PDF should stand on its own for technical readers who are not browsing the website.