Resources
The documents this site was written from
Nine engineering documents plus the project README, copied into this site at build time so a claim on a marketing page and the evidence behind it cannot drift apart. Every byte count in the table is the size of the copy being served, read at build time.
Document set
Plain markdown, served from this origin
10 files · 108,659 bytes total · copied from nodavx.com/docs/ on 2026-10-18. No document portal, no third-party host, no login.
| File | What it settles | Kind | Size |
|---|---|---|---|
| ARCHITECTURE.md | Architecture The single-authority decision, the request path, the snapshot contract, and why there is no cache allowed to be right. |
DESIGN | 11,721 B |
| LIVE_STATE.md | Live state protocol How a committed write reaches an open tab: invalidation-only SSE, the cursor, the out-of-band watcher, and every section naming the file to read. |
DESIGN | 6,603 B |
| ONTOLOGY.md | Ontology Object types, link types with cardinality, action types, identity rules, and the storage envelope versus the flexible payload. |
DESIGN | 9,518 B |
| VALIDATION.md | Validation Every latency, frame-rate and journey result in this build, each with its reproducing command, and an explicit list of what was not measured. |
EVIDENCE | 24,172 B |
| BUILD_STATUS.md | Build status Milestone-by-milestone build history. The test figures on this site come from a measured run of both suites (tools/measure-atlas-tests.mjs), not from this document. |
EVIDENCE | 10,188 B |
| DEMO_GUIDE.md | Demo guide The two mandatory stories step by step in the same order the browser journeys assert them — the source of the shortfall and margin figures quoted on this site. |
EVIDENCE | 10,719 B |
| OPERATIONS.md | Operations Configuration, credential handling, data paths, backup and reset, written from package.json and the real tools rather than from intention. |
OPERATIONS | 11,741 B |
| RESEARCH.md | Research and versions Version and licence claims with the label attached: measured on this machine, or vendor-claimed and unverified. |
EVIDENCE | 7,360 B |
| ROADMAP.md | Roadmap What is deliberately after M6 and not built, each item stating what exists today so the next step is concrete. |
DESIGN | 5,742 B |
| README.md | Project README What this folder is, every port the stack listens on, and the two-minute path from a clean clone to a seeded atlas. |
OPERATIONS | 10,895 B |
These are working documents, not brochures. Where a figure is vendor-claimed rather than measured on the build machine, the document says so and this site repeats the label instead of quietly dropping it.
Screens
The atlas, one screen per claim
Captured from the running application on this machine at 1600×1000. The launcher proves the service panel is honest; the shortfall tiles prove the arithmetic is printed; the copilot proves citations are clickable.
If you want to go deeper
Three ways in, depending on what you are checking
Pick the door that matches the question you were asked.
“Is it fast enough?”
VALIDATION.md, then the measured performance summary with the same figures in context.
“Is the model real?”
ONTOLOGY.md for types and cardinality, plus the object coverage table counted live from the store.
“Can we run it?”
OPERATIONS.md for ports, credentials and reset, then README.md to boot it.
Prefer to be shown, not to read?
Fifteen minutes on the two stories, on a call, with your own question put to the copilot at the end.