Start with a short project brief and a dated decision log. The brief explains purpose, owner, constraints and current state. Each decision records what was agreed, why it matters and which source supports it. Write so a person returning later can understand the work without opening an old conversation.
Readable files and AI memory have related jobs. A source note can hold the complete rationale, while a checkpoint captures the concise decision a new session should recall. Keep their relationship explicit so an abbreviated memory does not hide an important condition.
Use a small, predictable note structure
This is a suggested human note layout, not a required Central Brain storage format. Put the current purpose and status in the brief, decisions in a dated log, unresolved questions in their own file and supporting material in sources. Link to documents when possible rather than copying large passages into every note.
For example, a decision entry can identify an approved requirements version, the approving owner and the reason for choosing it. If approval is pending, record that condition as an open item. Keep sensitive material within the project boundary that permits its use.
project/
project-brief.md
decisions.md
open-questions.md
sources/
meeting-notes/Choose the right way to retrieve the record
Use exact text search for a known phrase or identifier and semantic search to find related material expressed in different words. Search results are candidate evidence: open the relevant source and check its current meaning before carrying it into an answer. Results include the source path, prepared-file path, page and chunk where available.
Use memory_recall for the saved project brief and notes, and memory_checkpoint for a compact reviewed decision or open item. Five note types (decision, fact, question, todo and summary) plus a project brief, stored as readable local files. Saving a checkpoint does not automatically update a separate decisions.md file. Decide which human record resolves disagreements and keep the brief consistent with it.
Turn notes into reusable project context
- Write the brief and one decision in plain language. Identify a supporting source and any unresolved condition.
- Prepare only the approved project files in Central Brain. Search for a distinctive phrase and inspect the returned source.
- Connect a supported client using its generated configuration. Verify the project root with central_brain_ping.
- Checkpoint the reviewed decision, then start a fresh session and inspect the memory_recall result.
- Ask the assistant to locate the full source before relying on the abbreviated note. Correct stale notes when decisions change.
Keep the record readable as it grows
Review the brief after meaningful changes. Preserve rationale in the source log, identify superseded decisions and keep unresolved questions visible. Before using memory_compact, review the proposed replacement brief; that tool marks older notes as compacted rather than deleting them.
In the default workflow, files, prepared output, vectors and memory stay on storage you choose. Keygen receives licensing and device data, not documents. Connected AI tools receive the context they retrieve, and optional cloud connections send selected data only when enabled. Choose backups and access permissions appropriate to the material, and verify the connection again when switching projects. Readability supports inspection; it still requires a deliberate retrieval habit and a person responsible for keeping the record current.
Common questions
Are plain files enough to make an assistant remember a project?
They preserve a readable record, but the assistant must receive or retrieve relevant content. Use an explicit recall and source-search routine at the start of substantial work.
What belongs in a file versus a checkpoint?
Keep complete rationale and independently readable documentation in files. Save concise reviewed decisions, facts or open items as checkpoints, with a source reference when helpful.
Does a checkpoint update my separate Markdown decision log?
Do not assume that. A checkpoint writes Central Brain memory. Maintain separate human documentation deliberately and resolve conflicting versions before reuse.