01 / DECIDE
Architecture decision
Use it when contributors and agents repeatedly need the same repository-specific instructions.
Durable guidance should name architecture boundaries, commands, conventions, and verification without replacing the current task. Map input, output, state, and side effects as one observable path before deciding which layer owns encode repository truth in agents.md.
02 / BUILD
Three-step implementation
- 01
Frame the contract
Write down the caller, data classification, success condition, timeout, cancellation, and ownership. Use it when contributors and agents repeatedly need the same repository-specific instructions.
- 02
Build one narrow path
Implement one end-to-end path with request correlation, typed state, and reversible failure handling. Durable guidance should name architecture boundaries, commands, conventions, and verification without replacing the current task.
- 03
Prove the outcome
Turn acceptance into a repeatable fixture, contract test, or browser test. A newcomer can run the documented checks and obtain the same repository interpretation without private context.
03 / BOUND
Production boundary
Keep instructions scoped, executable, current, and free of secrets; nested files should only specialize their subtree.
04 / PROVE
Acceptance evidence
A newcomer can run the documented checks and obtain the same repository interpretation without private context.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://learn.chatgpt.com/docs/agent-configuration/agents-md' | sed -n '1,5p'