-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathllms.txt
More file actions
69 lines (55 loc) · 3.14 KB
/
llms.txt
File metadata and controls
69 lines (55 loc) · 3.14 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
# Deja Vu
> A 3-file memory system for any capable AI coding agent.
Deja Vu helps agents stop re-explaining the same repository context across new coding-agent chats through:
- explicit project rules
- a repeatable cue-scan, minimal-recall, and writeback workflow
- tiny Markdown and JSONL memory files inside the repository
- cue quality checks that keep the first recall step sparse and specific
- recall budget and outcome feedback that show whether memory helped, missed, or overloaded the task
- writeback routing and feedback reports that keep remembered project context durable and maintainable
- optional `deja-vu init`, `deja-vu doctor`, and `deja-vu explain` CLI support
The minimum adoption path is three files: `AGENTS.md`, `memory/summary.md`, and `memory/impressions.jsonl`. It does not require npm, embeddings, vector search, a daemon, or a dedicated memory service.
## Best starting points
- [README](./README.md): product overview and primary adoption path
- [Starter Kit](./starter-kit/README.md): copy-first three-file setup and per-agent prompts
- [Comparison](./docs/comparison.md): how Deja Vu differs from vector DBs, hosted memory, runtimes, notes, and transcripts
- [Agent Compatibility](./docs/agent-compatibility.md): which agents can follow the protocol and how chat-only agents can use it manually
- [Flow Diagram](./docs/diagrams/deja-vu-flow.md): cue scan, minimal recall, durable writeback
- [Demo Walkthrough](./docs/demo-walkthrough.md): before/after project memory example
- [Protocol](./docs/protocol.md): normative protocol definition
- [Workflow](./docs/workflow.md): recall, writeback, and compaction lifecycle
- [Markdown Storage](./docs/storage-markdown.md): minimum and optional memory layout
- [Impression Layer](./docs/impression-layer.md): compact keyword-first familiarity surface
- [Scripted Recall](./docs/scripted-recall.md): host script contract for cheap pre-task scans
- [v0.6.0 Candidate](./docs/release-v0.6.0.md): adoption release checklist
- [Templates](./docs/templates): copyable rules and memory templates
- [Protocol Example](./examples/protocol-project): repo-first example with no engine
## Optional engine references
- [Optional Engine Layer](./docs/engine/semantic-engine.md)
- [Protocol-to-Engine Mapping](./docs/engine/protocol-to-engine.md)
- [Plugin Types](./src/types/plugins.ts)
- [Memory Types](./src/types/memory.ts)
- [Core Engine](./src/core/semantic-recall-engine.ts)
## Concepts
- protocol-first memory
- cue-first recall
- project-scoped continuity
- recall before substantial work
- impression-first scripted recall
- cue quality linting
- gist-first summaries
- boundary-aware chunking
- recall budget
- recall outcome feedback
- selective writeback
- event ledger continuity
- Markdown memory
- compaction and supersession
- optional semantic recall engine
## Intended use
Use Deja Vu when you want:
- durable continuity across new conversations
- explicit and inspectable project memory
- a lightweight memory discipline that works in many agent environments
- an optional path to semantic recall without changing the core workflow
Do not treat this repository as a hosted memory platform or autonomous memory daemon.