EverOS Documentation

June 10, 2026 · View on GitHub

Documentation for EverOS — md-first memory extraction framework. Organised by Diátaxis — what kind of question you have determines which section to read.

Reference

Technical reference: contracts, commands, schemas — read these when you already know what you want to do and need to know exactly how.

DocPurpose
api.mdHTTP API v1 reference — endpoints, request / response, error contracts
cli.mdeveros CLI subcommands + env var conventions
storage_layout.mdMemory-root tree + frontmatter chassis + EntryId encoding
prompt_slots.mdYamlConfigLoader + three-layer prompt override
migration-to-1.0.0.mdLegacy API and infrastructure migration notes for EverOS 1.0.0

Explanation

Design decisions and architectural concepts — read these to understand why the system is shaped the way it is.

DocPurpose
overview.mdProject vision, scope, design philosophy
how-memory-works.mdStorage stack + on-disk paths + write→index→read pipeline + consistency
architecture.mdDDD layered architecture + dependency rules
datetime.mdTwo-zone discipline — UTC at storage, display tz at boundaries

How-to

Task-driven operational guides — read these when you need to do a specific thing (drain a queue, recover from a stuck row, etc.).

DocPurpose
cascade_runbook.mdCascade subsystem ops — drain queue, recover stuck rows
multimodal.mdIngest images, PDFs, audio, and office docs into memory

Engineering / Internal

For maintainers and contributors working on the framework itself, not for using it.

DocPurpose
engineering.mdEngineering & dev-efficiency infrastructure (CI / tooling / Claude Code)

See also

Top-level project files live next to the repo root:

Coding conventions and slash command workflows are auto-loaded by Claude Code from .claude/rules/ and .claude/skills/.