Architecture Decision Records (ADRs)¶

Architecture Decision Records (ADRs) document significant architectural decisions made during the development of Trussium.

They capture the reasoning behind important technical choices, allowing contributors to understand not only what was decided but also why.

Each ADR represents a single decision and follows a consistent structure.

Purpose¶

ADRs help maintain long-term architectural consistency by documenting:

Context
Decision
Consequences
Alternatives considered

As the project evolves, ADRs provide historical context for contributors and maintainers.

Status¶

Each ADR includes one of the following statuses:

Proposed
Accepted
Superseded
Deprecated

Naming¶

ADRs are numbered sequentially.

Example:

0001-language-strategy.md
0002-project-structure.md
0003-capability-first-architecture.md
0004-plugin-architecture.md
0005-runtime-bootstrap-architecture.md
0006-controlled-tool-execution.md
0007-provider-batch-inference.md
0008-community-provider-plugin-boundary.md

Numbers are never reused.

Template¶

Every ADR follows this structure:

Status
Context
Decision
Consequences
Alternatives Considered

Philosophy¶

Architecture decisions should be documented before implementation whenever practical.

This ensures implementation follows documented design rather than architecture emerging from implementation.