cairntir

Why Cairntir exists

A new coding task should not require the user to reconstruct a project’s decisions, failed approaches, or unfinished requests.

Cairntir addresses that problem with shared, local, inspectable evidence: verbatim memory, searchable history, provenance, and whole-drawer handoffs under an explicit budget. The memory belongs to the user, not to one model or chat host.

Continuity is a contract to test, not a promise of perfect recall. If a host has persisted an interrupted request, opt-in transcript recovery should return that request verbatim or explain why it cannot. Recovery does not silently store messages or turn their contents into instructions.

Predictions and observed outcomes make it possible to check whether prior reasoning helped. Derived discoveries must cite evidence and remain subject to review. More stored text is not proof of learning.

The project stays focused on this memory layer. Agent execution, model training, commercial product plans, and speculative applications are not requirements of the core build.

See concepts, the roadmap, and the design principles.