Artifact Registries

Canonical registry of the artifact cohorts. This document carries the full enumerations of commands, rules, delegated workers, hooks, skills, output styles, artifact-evolution discipline, and empty-artifact-class declarations; the substantive tables live here. The project source layout provides the condensed always-on view.

1. Commands

Forty-five commands are registered from src/apothem/commands/*.md (non-recursive) — the full, always-current per-command reference is the generated Commands reference, and the thirteen-stage /research pipeline (/research-ideate through /research-disseminate) plus the /audit and /fortress wrapped-workflow orchestrators are enumerated there in full. Every command is a first-class registered file; the /plan orchestrator only chains the already-first-class plan stages and carries no stage logic of its own, so there is still no monolithic dispatcher and no subcommand grouping. The non-plan, non-research audit and elevation commands:

Plan-pipeline commands

The plan pipeline ships as eight first-class commands — one per stage, each invocable directly as /plan-<stage> from its own registered file at src/apothem/commands/plan-<stage>.md.

Operator-workflow & orchestrator commands

Three commands enter a deep procedure rather than carry stage logic of their own: two operator-workflow entry points (each backed by a sibling skill of the same name) plus the thin plan-pipeline orchestrator.

2. Rules

Behavioral rules live under src/apothem/rules/ — a small always-on core plus a larger path-filtered set (demand-loaded on matching artifact touches). The complete per-rule enumeration — with the Scope (always-on / path-filtered) and Implements columns — is the source-generated reference/rules.mdx, refreshed from src/apothem/rules/*.md by the reference-inventory generator; consult it for the authoritative current list.

CM-21 facet delineation (three rules co-implement CM-21 with distinct non-overlapping facets): creative filters & cognitive identity → cognitive-identity.md; generation methodology (writing & re-writing protocols) → clean-room-generation.md; planning/review techniques → planning-techniques.md. Each rule owns its facet; the others refer out.

Interactive-questions schema pointer. The canonical structured-inquiry invocation schema — required fields, field-summary table, two executable worked examples (single-select at §2.1 and multi-select at §2.2) — lives at src/apothem/rules/interactive-questions.md §2 "Structured-Inquiry Shape". Downstream artifacts may copy §2.1 or §2.2 as invocation templates; the three-segment option-annotation schema that every option's description body carries is specified in the same file's §3.

3. Delegated Workers

Twelve persistent worker definitions ship with the ecosystem; the orchestration rule's team patterns dispatch to them. Each definition lives at the file path listed below.

Worker              File                                       Pattern         Model Policy
------------------- ------------------------------------------ --------------- -------------
Codebase Explorer   src/apothem/agents/codebase-explorer.md   Research        host-selected
Convention Auditor  src/apothem/agents/convention-auditor.md  Audit           host-selected
Dependency Auditor  src/apothem/agents/dependency-auditor.md  Audit           host-selected
Fact Checker        src/apothem/agents/fact-checker.md        Audit           host-selected
MCP Builder         src/apothem/agents/mcp-builder.md         Generation      host-selected
Memory Auditor      src/apothem/agents/memory-auditor.md      Audit           host-selected
Prompt Evaluator    src/apothem/agents/prompt-evaluator.md    Quality         host-selected
Quality Gate        src/apothem/agents/quality-gate.md        Quality         host-selected
Refactor Surgeon    src/apothem/agents/refactor-surgeon.md    Implementation  host-selected
Research Scout      src/apothem/agents/research-scout.md      Research        host-selected
Security Scanner    src/apothem/agents/security-scanner.md    Audit           host-selected
Test Runner         src/apothem/agents/test-runner.md         Quality         host-selected

4. Hooks

Every registered hook command uses Claude Code's exec-form command shape (command: "python" plus an args array) and invokes either -m apothem.hooks.dispatch or -m apothem.conformity.gate. The dispatcher imports src/apothem/hooks/lib/resolve_root.py for ecosystem-root resolution and delegates to two helpers that sit alongside it under src/apothem/hooks/ itself: src/apothem/hooks/emit_hook_context.py formats event payloads for the assistant, and src/apothem/hooks/session_start_bootstrap.py carries the SessionStart preparation work the dispatcher hands off when it routes that event. The hook messages surfaced to the assistant when the supported events fire live as Markdown context files under src/apothem/hooks/messages/ — one per event variant: postcompact.md, precompact.md, pretooluse-bash.md, pretooluse-bash-plan-guard.md, pretooluse-conformity.md, pretooluse-dependency-guard.md, pretooluse-edit.md, pretooluse-edit-header-guard.md, pretooluse-eval-guard.md, pretooluse-notebookedit.md, pretooluse-write.md, pretooluse-write-header-guard.md, pretooluse-write-plan-guard.md, sessionstart.md, stop.md. Each routed context file is loaded by the dispatcher when its event fires and its context argument is registered in settings.json; three context files (pretooluse-conformity.md, pretooluse-dependency-guard.md, pretooluse-eval-guard.md) ship as available variants without a current settings.json routing entry.

Event             Automates                Timeout  Purpose
----------------- ------------------------ -------- --------------------------------------------------
SessionStart      CM-14                    30s      Read memory, check plan state, report readiness
PreCompact        CM-24 §2.3               30s      Verify state externalized before compaction
PostCompact       CM-24 §6.2               30s      Restore working state after compaction
Stop              CM-14/CM-22/CM-24/CM-26  60s      Session-end externalization
PreToolUse        CM-7/CM-22               10s      Write/Edit/NotebookEdit validation — codebase-isolation, frontmatter, license-header, and plans-locality checks plus the conformity gate. Bash validation — git artifact isolation and plans-locality
PostToolUse       —                        10s      Accepted by src/apothem/hooks/dispatch.py whitelist for forward compatibility; no settings.json entry currently routes this event
UserPromptSubmit  —                        10s      Accepted by src/apothem/hooks/dispatch.py whitelist for forward compatibility; no settings.json entry currently routes this event
Notification      —                        10s      Accepted by src/apothem/hooks/dispatch.py whitelist for forward compatibility; no settings.json entry currently routes this event

Convention. Rows where Automates is — are accepted by dispatch.py but not wired in settings.json; the Timeout column shows the dispatch-level default that applies if and when the event is later wired.

Timeout-value canonical block. This table's Timeout column is the single source of truth for hook timeout values across the ecosystem. The settings.json per-hook timeout fields, the mirror tables in site/content/docs/reference/settings-reference.mdx § Hook Events and site/content/docs/reference/artifact-schema.mdx § Hooks Pipeline, and the rule guidance at src/apothem/rules/persistent-conventions-vigilance.md § Convention Awareness all derive from this column. Future timeout revisions land here and the consumers re-derive at next reference.

Settings Template Review Cadence

settings.json is the single Claude Code template. Every hook command uses exec form instead of a shell-specific wrapper, so cross-OS behavior is reviewed inside one file rather than by diffing paired templates. New permission entries, hook events, timeouts, and status messages land in that file atomically.

5. Skills

Reusable skills live under src/apothem/skills/, one folder per skill.

Convention. Each row's Path is a folder; the entry point is the SKILL.md file inside it — e.g. src/apothem/skills/plan-suite/SKILL.md — per the folder-with-SKILL.md skill convention declared in the project source layout.

6. Output Styles

Four output styles live under src/apothem/output-styles/.

7. Artifact Evolution

Mandatory. When a reusable pattern, correction, or technique recurs (2+ instances in a session, or noted in memory as recurring), the ecosystem must evolve. The cycle has four steps: Detect the pattern during any interaction; Search existing skills, rules, commands, hooks, and memory for overlap; Act by evolving the matching artifact in-place (update procedure, anti-patterns, scope) or creating a new one when the concern is genuinely orthogonal; Validate that cross-references still resolve and dependent artifacts remain consistent. Prefer refinement over creation — new artifacts compound maintenance surface. See src/apothem/rules/persistent-conventions-vigilance.md §2+§4 for the full protocol including the closed catalogue of gap-detection triggers across every artifact class.

8. Empty Artifact Classes

Surfaces declared in the ecosystem registry but intentionally empty until an activation trigger fires. Each row records the reserved surface, the file or directory that scaffolds the class, and the trigger that promotes the row from empty-attest to populated.

Empty-attest is a positive declaration, not a gap. The class's scaffold (when one exists) is the canonical no-op artifact that tracks the activation moment. Promotions from empty-attest to populated land in the relevant registry section atomically with the scaffold's first non-empty value.