🤖 Add Zathras agent and initialize Spire for reliquary
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.
This commit is contained in:
@@ -0,0 +1,40 @@
|
||||
---
|
||||
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-at` is 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`, `status` once in frontmatter; the roster does the rest.
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
status: generated
|
||||
domain: <Domain Name>
|
||||
summary: <One-line summary of what this domain covers.>
|
||||
covers:
|
||||
- <path/to/main/source/>
|
||||
- <path/to/tests/>
|
||||
related: []
|
||||
status: active
|
||||
---
|
||||
# <Domain Name>
|
||||
|
||||
<!-- Replace this heading and fill the frontmatter during genesis orientation.
|
||||
This file is the index — keep it under ~60 lines. It is auto-loaded by
|
||||
the harness whenever any file in this folder is read. -->
|
||||
|
||||
<!-- One paragraph: scope, boundaries, what is and is not this domain. -->
|
||||
|
||||
## Must-read
|
||||
|
||||
Every genesis, before answering anything. Keep this list to three or four entries.
|
||||
|
||||
- `handoff.md` — where the previous adept left things. Always first.
|
||||
- `key-files.md` — the files that matter, what each does, where the seams are.
|
||||
<!-- - `conventions.md` — rules here that differ from the project-wide ones. -->
|
||||
|
||||
## Good-to-read-if
|
||||
|
||||
<!-- State the condition for each entry. -->
|
||||
|
||||
<!-- - `architecture.md` — if asked how the pieces fit, or where a new thing should go. -->
|
||||
<!-- - `gotchas.md` — if asked why something behaves oddly. -->
|
||||
- `journal/` — if `handoff.md` points at a specific entry, or a question touches a dead end noted there. Do not read the whole journal.
|
||||
|
||||
## Open questions
|
||||
|
||||
Carried forward by predecessors. Try to resolve one before adding one.
|
||||
|
||||
<!-- - "Why does FooService bypass the standard auth middleware?" (since YYYY-MM-DD) -->
|
||||
@@ -0,0 +1,25 @@
|
||||
---
|
||||
status: generated
|
||||
updated: <YYYY-MM-DD-HH>
|
||||
session: <path to current session journal entry>
|
||||
branch: <current branch or worktree>
|
||||
verified-at: <commit SHA when solid docs were last checked against code>
|
||||
---
|
||||
# Handoff — <Domain Name>
|
||||
|
||||
## State
|
||||
<!-- Where things stand. What is documented and verified, what is not. -->
|
||||
|
||||
## In flight (experiences, not solid)
|
||||
<!-- Branch observations, unmerged work. These stay here until the code is on main. -->
|
||||
|
||||
## Open threads
|
||||
<!-- Unfinished investigations, pending questions, next steps. -->
|
||||
|
||||
## Successor: read first
|
||||
1. This file.
|
||||
2. `key-files.md` — most likely to have drifted.
|
||||
<!-- 3. `journal/<entry>.md` if a specific branch is still open. -->
|
||||
|
||||
## Drift check
|
||||
git log --oneline <verified-at>..HEAD -- '<path1>' '<path2>'
|
||||
Reference in New Issue
Block a user