49 lines (34 loc) · 1.72 KB

Example Project Rules

This example shows the minimum Deja Vu protocol adoption path with no engine.

Memory system

Protocol: Deja Vu Protocol v0.4
Scope: project:example-protocol-project
Memory root: memory/

Recall workflow

Before substantial planning, coding, or answering:

Run node ../../scripts/dejavu-scan-memory.mjs "<current task>" when using this example from its own directory.
If the result is not_initialized, create or ask for the three required files.
If the result is none, avoid memory reads by default.
If the result is weak, read memory/summary.md.
If the result is strong, open one to three linked detailed records.
If the script is unavailable, inspect memory/impressions.jsonl directly and apply the same budget.
Keep the scan output's budget fields visible before loading more memory.

Recall budget:

impression scan: always allowed
summary: at most one file
detailed records: one to three records
full memory tree: forbidden unless the user explicitly asks

Writeback workflow

After meaningful work completes:

Write back only durable memory.
Update the relevant detailed memory file.
Update memory/impressions.jsonl.
Update memory/summary.md if project understanding changed.
Update memory/index.md if the project uses one.
Add a short entry to memory/events/ only when the work should remain discoverable without becoming durable memory.
Append memory/recall-feedback.jsonl only when recall was helpful, irrelevant, missed, or overloaded in a way that should tune future memory.

Safety

Do not store secrets.
Do not store full chat transcripts.
Do not store customer or user PII.
Do not store low-value exploration noise.