AgDR 1.2.0 · OPEN STANDARD
Record what the agent decided
and why.
AI agents make consequential technical choices during implementation. AgDR preserves the decision and its rationale after the session ends.
THE RECORD
A decision that survives the session.
AgDR records the context, alternatives, decision and consequences of a consequential choice.
--- id: AgDR-0001 timestamp: 2026-02-04T12:00:00Z agent: claude-code model: claude-opus-4-5 trigger: user-prompt status: executed --- # Auth Provider for Serverless Chrome Extension Chosen: AWS Cognito Why: Native API Gateway integration and managed security. Trade-off: Hosted UI limitations and AWS lock-in.
Copy Markdown · View raw
ADOPT
Use AgDR with the agent you already have.
Claude CodePlugin or manual /decide command
CodexSkill under .codex/skills
CursorAlways-on .mdc rule
GitHub CopilotRepository instructions
WindsurfCascade rule
Any AISystem prompt instructions
Git + CIHooks and validator workflow
THREE FILES. ANY AGENT.
Portable by default.
AgDR does not require a plugin or proprietary runtime. Copy the template, schema and validator into any repository.
agdr-template.md
+
agdr.schema.json
+
validate-agdr.js
↓
docs/agdr/AgDR-*.mdMACHINE CHECKABLE
A standard the agent can fail.
The repository validator checks metadata, enums, filename identity, required sections, Y-statements, unique IDs and supersession references.
$ node scripts/validate-agdr.js docs/agdr/*.md ✓ AgDR-0001 valid ✓ AgDR-0002 valid 2 records checked 0 errors
WHEN TO RECORD
Record choices that change the system.
Create an AgDR
Choose a library, architecture, storage model, migration strategy, security approach or lasting project convention.
Do not create an AgDR
Variable names, formatting, routine refactoring, existing conventions and straightforward fixes.
ADR VS AGDR
AgDR complements ADR.
ADR
Human or team · design process · usually manual
AgDR
AI agent · during execution · metadata and automated checks
REAL EXAMPLES
Decisions from the repository.
Authentication, data models, migration strategies, mobile architecture, release workflows and image loading.
Browse examples →INTEROPERABILITY
Independent by design.
AgDR remains useful on its own. With ORBIT, a record can optionally reference the execution slice or outcome context where the decision was made.
Read the profile →