Patterns
8 proven patterns that solve recurring challenges in aDNA projects. Each pattern describes the problem, the solution, and where to find a working example in this vault.
The Question Test
Every new file in an aDNA project needs to land in one of three folders — what/, how/, or who/. Most files are obvious; edge cases cause hesitation. Is ...
AGENTS.md Routing
A project folder can hold hundreds of files. An AI agent working on a single task needs only a handful of them — but how does it know which folders to o...
Dual-Audience Writing
aDNA documentation must serve two audiences with different needs: developers seeking technical precision for implementation, and newcomers seeking plain...
Base/Extension
A shared standard has to be stable enough that teams can build on it, but flexible enough to handle work the authors never imagined. If every team chang...
Context Recipe
Most real tasks need knowledge from several areas at once — not one clean topic. Without a pre-built list of what to load, an agent either grabs everyth...
FAIR Envelope
A shareable object without a label is a black box — nobody outside your project can find it, tell if it's trustworthy, know who made it, or use it legal...
Mission Decomposition
Some jobs — writing thirteen concept files, or building a whole documentation site — are too big for any one agent session to finish in one go. Without ...
Federation Readiness
Something that works in your project isn't automatically safe to hand to someone else. A workflow may rely on files only you have, skip the labels a str...