Production agent systems · stage 02 of 09
Architecture decision
Which shape, and which credible alternative you are rejecting and why.
The module
Lesson, exercise and rubric
Open the repository in a coding agent and run /module 02 for a Socratic session over this stage.
What you leave behind · markdown
Architecture decision record
Required sections:
- context
- options considered
- decision
- consequences
- what would reverse this
May appear on a public portfolio once redacted: remove internal system names.
The eval · eval:adr-has-rejected-options
The ADR rejects something specific
- two-options-minimumAt least two options were considered and one was rejected with a reason. Checked by: Count entries under options considered; require >= 2 and a stated rejection reason.
- reversal-conditionThe record states what evidence would reverse the decision. Checked by: A non-empty "what would reverse this" section exists.
Every check must pass. There is no partial credit and no override.
Independent review · the author may never review their own work
Architecture decision defence
- The rejected option is one a reasonable engineer would have chosen.
- The consequences section names a cost the author is accepting, not only benefits.
- The reversal condition is observable without asking the author.
Evidence that counts
Proof has to exist outside your own claim.
At least 1 of: a commit or file a third party can open; a recorded, reproducible eval run. Evidence older than 365 days is stale and does not count.