19. Optional Extensions
Scan: Six opt-in subsystems — machine registry, backlog, skill files, testing/CI awareness, reference code, ADRs. Adopt based on need.
The following patterns are available but not required. Projects adopt them based on need.
19.1 Machine Registry
Decision: D10
For projects running on multiple machines or sync environments where path patterns vary.
Location: what/hardware/machines/ or a similar what/ subfolder.
Per-machine file contents: hostname, user, OS, path patterns, installed tools, capabilities.
RECOMMENDED for sync-based environments (cloud storage, team sync tools) where file paths differ across machines. OPTIONAL for git repositories where environment variables handle path differences.
19.2 Backlog System
Decision: D13
Durable ideation and improvement tracking.
Location: how/backlog/
Lifecycle: idea → triage (priority/effort assessment) → graduation to how/missions/ or archive.
Frontmatter: type: idea, category, priority, effort, status, proposed_by.
Agents SHOULD scan how/backlog/ during session startup for ideas relevant to the current work. New ideas discovered during work SHOULD be captured as backlog files.
19.3 Skill Files
Decision: D15
Reusable agent procedures — step-by-step instructions agents can follow autonomously.
Location: how/skills/skill_{name}.md
Sections: purpose, prerequisites, steps, verification, rollback, notes.
Skills are distinct from processes: skills are agent-executable (precise steps, verification checks); processes are human-readable (guidelines, decision trees).
19.4 Testing/CI Awareness
Decision: D23
aDNA does not prescribe test frameworks or CI/CD configurations — these belong to the project content layer. However, agents SHOULD be aware of test status.
Awareness pattern:
- CLAUDE.md includes an optional section on testing: where to check, how to run, what signals mean
- AGENTS.md for code directories includes testing guidance as an enrichment layer
- STATE.md reports test status when relevant (pass/fail, coverage, regressions)
- CI/CD configuration lives in project content (
.github/,Makefile,pyproject.toml, etc.)
19.5 Reference Code
Decision: C11
Bounded exception for code-adjacent reference material inside the aDNA structure.
Location: what/reference/
Rules:
- Executable code MUST live in
what/reference/or in the project content layer — nowhere else in the triad - what/reference/ MUST be bounded — no unbounded growth
- Entries SHOULD link to source implementations rather than duplicating code
- Documentation-only projects skip this entirely
19.6 Architecture Decision Records (ADRs)
Decision: C12
Lightweight records of significant project decisions.
Location: what/decisions/
Template sections: context, decision, consequences.
ADRs are knowledge artifacts — decisions outlive the process that produced them. A 2-year-old ADR is reference knowledge, not an active operation. This is why they live in what/, not how/.