Publishing Memories

Draft first

Every memory starts as a draft. Drafts never appear in context retrieval. A useful memory captures one durable conclusion, uses the narrowest repository/path scope, and includes a source URL or an attributable author where possible.

Allowed types are decision, convention, warning, discovery, ownership, and runbook. Confidence is either tentative or confirmed.

Explicit publication

The propose_memory MCP tool returns the exact draft and tells Claude to show it to the user. publish_memory must be called only after the user explicitly approves that exact draft. Publication records the publisher, timestamp, and an audit event.

Members can publish their own drafts. Owners and admins can manage every memory in their organisation.

Corrections

Editing an already published memory creates an immutable snapshot. Disputing or archiving a published memory also creates a version and immediately excludes the current record from retrieval.

Any member can file a stale, incorrect, conflicting, or sensitive-content report. A report does not silently delete the memory; it lowers retrieval ranking until an owner or admin marks the report resolved.

Safety rules

• Repository paths must be relative and cannot contain traversal segments.
• Source URLs must use HTTPS.
• High-confidence private-key, cloud-key, GitHub-token, and credential patterns are rejected.
• Do not paste transcripts, prompts, source files, terminal output, personal data, or secrets into a memory.
• Current repository code and checked-in instructions outrank Intertool memories.