Docs
Get the most out of Ravnik
Start every AI session with the briefing
Ask for the session briefing first. It returns pinned pages, unresolved actions and freshness, so the AI starts from facts, not memory.
Keep summary pages fresh
When the gap on a priorities page grows, rebuild it from the decision log. Stale summaries cause confidently wrong answers.
Read one page, edit one section
Use the single-page and section-edit tools instead of replacing whole pages, so large pages are not overwritten by accident.
Use projects to keep work apart
Separate products or areas get separate projects, and your AI instructions should name the one in use.
Link code to decisions
Where commit tracing is available, add a Decision: <ID> trailer to commits so code points back to the reasoning.
Note
Commit tracing works today for the Ravnik project’s own repository. For other organizations it is coming.
Cut versions from decisions when you ship
Cut a version when you release, so your changelog comes from what you actually decided.
Write things down in the same place your AI reads
If it is only in someone’s head or a chat, the next session will not know it.