The knowledge base stores three types of articles, each with a defined YAML frontmatter schema and a fixed section structure. The LLM uses these templates when compiling daily logs or filing query answers. Humans can read and navigate the articles directly, but the LLM is the primary author — you should rarely need to editDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/coleam00/claude-memory-compiler/llms.txt
Use this file to discover all available pages before exploring further.
knowledge/ files by hand.
All article files live under knowledge/, use lowercase filenames with hyphens, carry required YAML frontmatter, and link to related articles using Obsidian-style [[wikilinks]].
Concept articles
Location:knowledge/concepts/
Concept articles are the atomic units of the knowledge base. Each one covers a single topic — a pattern, a decision, a preference, a lesson, or a technical fact extracted from your conversations. If a daily log mentions ten distinct things, the compiler may produce anywhere from three to seven concept articles.
The compiler prefers updating an existing concept article over creating a near-duplicate. A single article can accumulate entries from many daily logs over time, with each source log listed in the frontmatter.
Full template
Frontmatter fields
| Field | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Human-readable name of the concept |
aliases | list | No | Alternate names or abbreviations for the same concept |
tags | list | No | Domain and topic labels for grouping |
sources | list | Yes | Relative paths to every daily log that contributed to this article |
created | date (ISO 8601) | Yes | Date the article was first created |
updated | date (ISO 8601) | Yes | Date of the most recent update |
Sections
| Section | Purpose |
|---|---|
Core explanation (under # Concept Name) | 2–4 sentence summary; written to be self-contained |
| Key Points | 3–5 self-contained bullet points covering the most important facts |
| Details | Two or more encyclopedia-style paragraphs with deeper explanation |
| Related Concepts | Wikilinks to at least two related articles with brief connection notes |
| Sources | Wikilinks back to source daily logs with a note on what each log contributed |
Every concept article must link to at least two other articles via
[[wikilinks]] and must cite its source daily logs in the Sources section. These requirements are enforced during lint checks.Connection articles
Location:knowledge/connections/
Connection articles document non-obvious relationships between two or more existing concepts. The compiler creates them when a daily log reveals that two separate topics share a pattern, a constraint, or an insight that is not obvious from reading the concept articles individually.
Connection articles are created less frequently than concept articles. A typical compilation produces zero to one connection articles.
Full template
Frontmatter fields
| Field | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Must follow the pattern "Connection: X and Y" |
connects | list | Yes | Relative paths (without .md) to the two or more concepts being linked |
sources | list | Yes | Relative paths to the daily log(s) where the relationship was discovered |
created | date (ISO 8601) | Yes | Date the connection article was first created |
updated | date (ISO 8601) | Yes | Date of the most recent update |
Sections
| Section | Purpose |
|---|---|
| The Connection | What the two concepts have in common or how they interact |
| Key Insight | The non-obvious relationship — what makes this connection worth an article |
| Evidence | Specific examples from conversation logs that demonstrate the connection |
| Related Concepts | Wikilinks to the connected concepts and any other relevant articles |
Q&A articles
Location:knowledge/qa/
Q&A articles store the answers to queries filed with query.py --file-back. Unlike concept and connection articles (which the compiler creates autonomously during compilation), Q&A articles are created on demand in response to an explicit question. Every filed answer becomes a permanent part of the knowledge base and is listed in knowledge/index.md, making future queries on the same topic faster and cheaper.
Full template
Frontmatter fields
| Field | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Must follow the pattern "Q: <question text>" |
question | string | Yes | The exact question string passed to query.py |
consulted | list | Yes | Relative paths (without .md) to every article read when formulating the answer |
filed | date (ISO 8601) | Yes | Date the Q&A article was created |
Sections
| Section | Purpose |
|---|---|
| Answer | The synthesized answer with inline [[wikilink]] citations |
| Sources Consulted | Each consulted article with a note on why it was relevant |
| Follow-Up Questions | Suggested next questions to deepen understanding of the topic |
Conventions
These rules apply to all three article types.Wikilinks
Wikilinks
Use Obsidian-style double-bracket syntax without the Links to daily log source files include the
.md extension. Always use the full path relative to knowledge/:.md extension by convention. Links to knowledge articles do not.Writing style
Writing style
Write in encyclopedia style: factual, concise, and third-person where appropriate. Avoid first-person (“I decided…”) in favour of passive or neutral constructions (“The decision was made to…”). Every section should be self-contained enough to be read without context from surrounding sections.
Dates
Dates
Use ISO 8601 throughout. Use
YYYY-MM-DD for date-only fields (created, updated, filed). Use full ISO 8601 with time and offset for timestamps in knowledge/log.md (e.g. 2026-04-01T14:30:00+00:00).File naming
File naming
Lowercase letters and hyphens only. No spaces, underscores, or special characters. Examples:
Frontmatter requirements
Frontmatter requirements
Every article must have YAML frontmatter with at minimum:
title, sources (or consulted/connects for the appropriate type), and the relevant date fields. Articles without frontmatter will be treated as malformed by lint checks.Source backlinks
Source backlinks
Every article must link back to the daily log(s) that contributed to it. Concept and connection articles do this through the
sources frontmatter field and the Sources section. Q&A articles do this through the consulted frontmatter field and the Sources Consulted section.