Architecture decisions

Each record holds one decision that shapes ferrigura: what it covers, what it decides, why, and what follows from it. The records are living documents. When a decision changes, its record is edited in place; when a decision no longer holds, its record is deleted and its number is not reused. There are no dates, statuses or change logs in a record: what it says is what holds today.

A record has this outline:

• Scope: what the decision covers and, as explicitly, what it does not cover.
• Decision: the rule, worded so that it can be checked where possible.
• Why: the reasons, and the options that were weighed and not chosen.
• Consequences: what follows for the code, the tests and the users.
• Related: other records and the learnings behind it.

A new decision that is hard to reverse gets the next free number. Code comments cite a record by its number, such as decision 0009.

Project

Architecture

Verification

Distribution