Skip to content
claudian.appDocsGitHubInstall on Windows

The memory protocol

Selective capture, linked notes and corrections that keep AI memory useful.

Read the smallest useful context

Begin with an entry note, locate the relevant topic and read the notes needed for the current task. A full chat export and an entire vault are both poor defaults for every conversation.

The protocol describes behavior. The chosen AI application supplies the model and the actual file tools. A skill cannot bypass that application’s permission system.

Memory should reduce work, not create it

A useful memory system shortens the path from a question to a decision. A beautiful graph or an elaborate folder taxonomy is not the goal. Notes should earn their maintenance cost through reuse.

Keep a small entry point, connect related concepts and update existing notes before adding more. The protocol should reduce repeated explanations and retrieval work without making the user manage a second job.

Keep decisions, preferences and lessons

Durable instructions, accepted decisions, corrections and lessons from a failed approach are useful candidates for memory. A passing mood, raw conversation transcript or repeated fact usually is not.

Search for an existing note first. Update the relevant passage instead of creating a duplicate file. Create a separate note when the concept has enough depth and will be useful from more than one place.

A correction outranks an old note

A note is a fallible record, not evidence against its owner. When a user corrects it, the active record should change. Preserve the reason for a meaningful reversal without leaving two contradictory instructions active.

Keep observation separate from inference. Record where a claim came from and when it was established when that context matters.

Shared facts, separate voices

The shared protocol governs memory. An AI-specific adapter describes how a particular application reaches it. Personal preferences and interaction style belong in a user overlay, rather than being embedded into rules for everyone.

This separation is the universal protocol direction. The current installer uses generated local skills; a complete policy-enforced gateway for all providers is not part of this preview.