Today I release a new file format that I have been building for a long time. It is called Engram. This is not just a file format. It is a decision about how memory should behave when the world is messy.
I have lived the pains of system rot. Loose files that drift, archives that decay, and cold storage that becomes unreadable without a ritual of tooling and reconstruction. Reopening old repositories, compiling old texts, or dealing with 57 U.S. Constitutions and Acts taking up a gigabyte of PDFs. It is intolerable in an age we would dare call golden.
I reject that compromise. I reject the idea that memory must be rented, that knowledge must be centralized, or that failure is acceptable because it is common.
We have settled for outages. We have watched misinformation spread while archives silently disappear. We have allowed institutions to outsource stewardship to systems that do not share their values. Meanwhile, "modern" infrastructure keeps scaling itself into fragility, and then asks the public to be patient when it collapses.
Engram is my answer. It is the first of eighteen core technologies we are building at Blackfall Labs to change how computing handles continuity. It is a back to basics move, but with modern precision.
What Engram is
Engram is an immutable archive format that embeds a small filesystem and a first-class SQLite database. Once written, it cannot be modified by any spec-compliant engine. It is built to be portable, verifiable, and offline-first.
Engram is meant to be carried. It should work in libraries, kiosks, crisis centers, rural towns, and disaster zones. It should remain readable when a company goes away, when a cloud account expires, and when a network is down.
The problem it solves
We have archive formats that are fast but bloated, and formats that are compact but slow to access. We have knowledge stores that require extraction, permissions, and brittle tooling. Engram removes the trade-off. It keeps the archive sealed while still letting you query the data inside it.
It also provides the ground truth for AI systems. Models can speak, but they are not authorities. Engram is the memory that does not disappear when the process dies.
The architecture in plain terms
- End-placed table of contents so writers can stream data in a single pass.
- Per-file compression so random access stays fast and predictable.
- SQLite Virtual File System support to query embedded databases directly.
- Open specification and MIT-licensed reference implementation.
Why this is a new era
Engram is not trying to be clever. It is trying to be durable. That is the paradigm shift. We are building computing systems that assume instability in politics, infrastructure, and institutions, and still hold the line on truth and access.
The future cannot be built on rented memory. Engram is a way out.
Where to go next
- Full engineering paper: Engram format announcement
- Full specification: SPECIFICATION-FULL.md
- Reference implementation: github.com/blackfall-labs/engram-rs
- CLI tooling: github.com/blackfall-labs/engram-cli
- Crate: crates.io/crates/engram-rs
- API docs: docs.rs/engram-rs
- Engineering index: engineering documentation
If you are building systems that must outlast funding cycles, product pivots, or institutional turnover, this is your invitation. Engram is ready to be used, tested, and stressed in the real world. You can reach me at magnus@blackfall.dev.