systembydave.com Davai memory architecture

Canonical routing reference

Davai memory architecture

A seven-layer static guide for deciding where memory belongs, how it should change over time, and how operators keep current state separate from evidence and architectural commitments.

Build from zero Open PROTOCOL.md
input route by retrieval question
identity/ semantic/ episodic/YYYY/MM/ procedural/ reference/ working/ decisions/

Seven layers

Architecture at a glance

Each layer exists because it answers a different retrieval question. Folder shape follows retrieval, not source format.

Routing frame

The question decides the folder

Do not ask where the note came from first. Ask what future retrieval will need: identity, timeless fact, dated evidence, instructions, source location, current state, or architectural commitment.

LayerNameRetrieval questionPath
Layer 1IdentityWho is this person, and what durable preferences shape the response?identity/
Layer 2SemanticWhat is true independent of a specific date or workflow?semantic/
Layer 3EpisodicWhat happened, when, and what evidence proves it?episodic/YYYY/MM/
Layer 4ProceduralHow should the system or operator perform this task?procedural/
Layer 5ReferenceWhere should someone look for authoritative source material?reference/
Layer 6WorkingWhat is active right now and likely to change soon?working/
Layer 7DecisionsWhat choice was made, why, and what does it supersede?decisions/
Davai folder tree with retrieval question callouts.
Folder layout with the retrieval question attached to each branch.

Publish blockers

Known production gaps

These are tracked openly so the site is useful as an implementation reference without pretending the instrumentation is complete.

Benchmark data is synthesized.Re-render latency, recall, and router F1 charts from a real harness before making performance claims.
Storyboard scripts assume a mem CLI.Rename the commands or write the CLI before recording operational walkthroughs.
Schema and links need enforcement.Add frontmatter linting and cross-layer link checks to the Janitor loop.
Routing telemetry is missing.Log input, chosen layer, confidence, and correction events so routing can improve from evidence.
Synthesized chart comparing retrieval latency as corpus scale grows.
Synthesized latency chart. Replace with benchmark data before publication.
Synthesized chart comparing first try recall as corpus scale grows.
Synthesized first-try recall chart. Replace with benchmark data before publication.
Synthesized bar chart of router F1 by trigger class.
Synthesized router F1 chart across the seven trigger classes.