recallit Architecture

Explain why the recallit engine stays topic-agnostic — what architectural choices enforce this?

Subject-specific content (cards, scenarios, dialect config) lives entirely in data/ and topic.json, never in src/. The load-bearing rule assigns invariants to code and subject knowledge to prompts+data. No branches in src/ reference a specific subject. This is proven by the World Capitals test running with zero code change.

• Subject-specific content lives in data/ config and prompts, not in src/ code
• The load-bearing rule: code owns invariants/sequencing; prompts+data own subject and pedagogy
• Proven by running a World Capitals deck in tests with zero code change
• Packs extend agnosticism to distribution — subjects ship and version independently of the engine

Explain recallit's 'files-as-truth' principle: what it means and how the system enforces it.

Files (item.md, topic.json, review_log.jsonl) are the primary, inspectable source of truth. The SQLite index is derived — always rebuildable from files, never the authoritative record. data/ is gitignored as runtime state. The durable form of a subject is a pack (packs/{id}/), tracked in source control separately from the engine.

• Files are the source of truth — transparent, inspectable, and agent-editable
• The SQLite index is derived and rebuildable from files — not the authoritative record
• data/ is gitignored because it's runtime state, materialized locally
• Packs (packs/{id}/) are the durable, shareable form of a subject, separate from the engine

What is recallit-the-platform in one sentence?

A topic-agnostic recall engine plus an agent that operates it.

What does 'agent-native' mean in recallit's architecture?

The agent has full parity with the user via atomic primitive tools; features are prompts that compose primitives, not bespoke code paths.

What is recallit's 'load-bearing rule'?

Code owns invariants and sequencing; prompts + data own the subject and the pedagogy.

Name the two architectural layers in recallit.

PLATFORM (code — knows nothing about any subject) and INSTANCE / PACK (data — all the subject-specific content).