Scaffold .claude/spire/project.md with reliquary-specific facts, create adept templates at docs/workpad/adepts/, build the Zathras agent and skill (Spire's self-maintenance coordinator), and wire /assistant as a local alias for spire:zathras.
2.0 KiB
2.0 KiB
status
| status |
|---|
| generated |
Adepts
This directory holds domain knowledge accumulated by adept agents. Each subfolder is one domain — a subsystem, a library, a cross-cutting concern — named with a short kebab-case slug.
Structure
adepts/
CLAUDE.md ← you are here
_template/ ← starter template; copied on founding
CLAUDE.md
handoff.md
<domain-slug>/
CLAUDE.md ← INDEX — frontmatter + tiered reading list. Short. Auto-loaded.
handoff.md ← rolling state for the successor. Overwritten, not appended.
key-files.md ← solid knowledge docs — as many as the domain needs
conventions.md
architecture.md
gotchas.md
... ← any other doc, provided it is listed in CLAUDE.md
journal/
YYYY-MM-DD-HH-genesis.md
YYYY-MM-DD-HH-<topic>.md
Conventions
- One domain per folder. Overlap → pick the stricter scope. Broad names are gravity wells.
- CLAUDE.md is an index, not a document. Frontmatter + tiered reading list + open questions. Under ~60 lines. It is auto-loaded whenever anything in the folder is read — keep it cheap.
- Every file in the domain root is listed in CLAUDE.md. Unlisted files do not exist.
- handoff.md is overwritten, never appended. Write it early, refresh it after anything significant.
verified-atis the commit the solid docs were last checked against. - journal/ is append-only. One file per topic or session,
YYYY-MM-DD-HH-<topic>.md. Recency and session counts are derived from these names — keep the prefix exact. - Solid knowledge goes in docs; experiences go in the journal. Branch observations stay in the journal (and handoff.md's "In flight") until the code is on main.
- Don't hoard. Findings that belong in the project's docs or a workpad report go there; link from here.
- Metadata is derived. Never hand-maintain counts, dates, or an index file. Declare
domain,summary,covers,related,statusonce in frontmatter; the roster does the rest.