Architecture Decisions 🧭

This directory holds the architecture decision records of Infinito.Nexus. A record states one decision that shapes the system, the forces that constrain it, and what living with it costs.

Scope 📋

A record MUST cover a decision whose reversal would be expensive: a contract between components, a data or naming shape other code depends on, or a rule that governs a whole subsystem.
A record MUST NOT be written for a choice that a reader can recover from the code alone, such as a helper's signature or a local refactoring.
A record MUST describe the decision as it stands today, including the alternatives that were weighed and why they lost, so a later reader can tell a deliberate constraint from an accident.
A record MUST be numbered in the order it was accepted, and its number MUST NOT be reused.
A superseded record MUST stay in place with its status changed and a link to the record that replaces it, because the reasoning it carries is what makes the replacement legible.