aDNA Enterprise Adoption Checklist

A structured walkthrough for procurement, security, and platform engineering reviewers evaluating aDNA for multi-team deployment. Four domains — compliance, session audit, federation, and integration surface — each backed by concrete vault artifacts. Scan the section you own; the pattern you evaluate is the pattern you deploy.

1 · Compliance posture

Every aDNA vault ships with the same four root-level governance files (CLAUDE.md, MANIFEST.md, STATE.md, AGENTS.md). An auditor who orients once orients across every team vault.

• Policy source of truth: CLAUDE.md names standing orders, priority hierarchy, and escalation cascade.
• Decision trail: ADR files under what/decisions/ pair each technical choice with rationale, trade-offs, and reviewer attribution.
• Operational snapshot: STATE.md captures current phase, blockers tagged #needs-human, and next actions — so status reviews don't require a meeting.

2 · Session audit trail

Every session — agent-assisted or human — creates a tracked file in how/sessions/ with session ID, intent, files touched, and a closing SITREP. The audit trail is a byproduct of normal execution, not a parallel workstream.

• Traceability: any committed artifact traces back to session → mission → campaign → context inputs.
• Collision prevention: last_edited_by + updated + read-before-write makes concurrent work safe without locks.
• Queryable history: session files are YAML-headed markdown — scriptable with standard tooling, no proprietary query layer.

3 · Federation surface

Three teams should not solve the same problem three times. Team A publishes a validated pipeline as a lattice; Teams B and C pull and compose it with explicit version policy. Every shared artifact passes a six-point readiness check before it crosses a team boundary.

• Opt-in by default: nothing federates without federation.shareable: true and a declared source instance.
• Version policy is explicit: locked / patch / minor / latest — downstream teams choose their own change tolerance.
• Provenance travels with the artifact: FAIR envelope (license, creators, keywords, provenance, identifier) is part of the file, not a side document.

4 · Integration with existing practice

aDNA is a knowledge architecture, not a platform replacement. Confluence, internal wikis, existing repo READMEs, and your identity stack stay where they are. AGENTS.md adds a routing layer; the governance layer lives in git alongside the code it governs.

• No vendor lock-in: the standard is open and permissively licensed; the vault is plain markdown in git.
• Ontology extension without fork: add compliance_check, team_policy, or shared_pipeline per team without breaking the base specification.
• Tool-agnostic: Obsidian, VS Code, JetBrains, plain CLI — any editor that reads markdown works.

Evaluation checklist

A reviewer working through this page should be able to answer the following in a procurement memo:

Next Steps