the-internet-tests

Architecture decision records

Decisions that shaped this repository, with the reasoning that produced them. The code shows what the repository does; these records exist for the part the code cannot show — what was rejected, and why.

What warrants an ADR

Write one when a decision is hard to reverse and affects any of:

Everything else is a pull request. A decision that is cheap to undo does not need a record; a decision someone will otherwise re-litigate in six months does. If you are unsure, ask whether a reader would be able to reconstruct the reasoning from the diff alone. If not, write the ADR.

How to add one

  1. Copy 0000-template.md to NNNN-short-title.md, taking the next free number.
  2. Fill in Status, Date, Context, Decision, and Consequences.
  3. Add it to the table below, and to the documentation index.

ADRs are immutable once accepted. A decision that no longer holds is not edited and not deleted: write a new ADR and set the old one’s status to Superseded by the new number. The record of having been wrong is the useful part.

Records

ADR Title Status Date
0001 Shared scenario catalog as the canonical model Accepted 2026-07-08
0002 Separate UI scenarios from HTTP/resource scenarios Accepted 2026-07-10
0003 Maintain three framework tracks Accepted 2026-07-11
0004 Isolate flaky-demo and not-ci tests from the gates Accepted 2026-07-10
0005 Keep workflows independent and parallel Accepted 2026-07-10