Architecture decisions,
on the record.

A seven-phase governed lifecycle: submission → peer review → ADB → under review → ready for decision → ARB review → decision. Risk-based fast-track via TDA for Low/Medium-risk decisions. Every step traceable to the principle that constrained it.

“Every architecture decision, ratified. Every principle, traceable. Every service, registered.”

§ Chief Enterprise Architect
ADR-2026-094 · lifecycle° APPROVED
P1 SUBMITDRAFTA. Patel · Solutions Arch
P2 PEERREVIEW3 reviewers
P3 ADBTRIAGEArchitecture Decision Body
P5 PATHTDARisk: MEDIUMfast-track
P6 TDADECIDETechnical Design Authority
P7 RECORDRATIFIEDLinked: 2 principles, 4 services
II — CAPABILITIES

Seven phases.
Two paths to decision.

Full ARB review for High and Critical-risk decisions. TDA fast-track for Low and Medium — no bottleneck on routine choices.

Seven-phase lifecycle

Submission, peer review, ADB triage, under review, decision-ready, ARB or TDA, recorded. Every transition signed.

Peer review with diff

Inline comments. Threaded annotations. Track changes between revisions. Reviewers attributable.

TDA fast-track

Low / Medium-risk decisions bypass full ARB. Faster decisions where the stakes don’t justify a quorum.

ARB voting record

Quorum, abstentions, dissenting opinions — all explicit. Decisions defensible because they are recorded.

Principle traceability

Every ADR linked back to the EA principles it honours or challenges. Frameworks: TOGAF, Zachman, FEAF.

Audit-grade record

The decision, the context, the alternatives considered, the consequences accepted. All immutable.

III — CONNECTIONS

How it connects.

→ EA principles. Every ADR links to the principles it honours, challenges, or amends.
→ Service catalogue. Decisions linked to the services they shape — ratified architecture visible.
→ Business cases. Decisions made under a case linked back to it.
→ AI governance. ADRs for AI systems automatically classified for EU AI Act applicability.
→ Audit trail. Every phase transition, vote, and revision immutably logged.
II·b — CONTEXT

ADR governance, not ADR templates.

Architecture Decision Records have been a recognised practice since Michael Nygard formalised the format in 2011. The problem is not awareness — most enterprise architecture teams know what an ADR is. The problem is that most ADR implementations are a folder of Markdown files in Confluence with no workflow, no review gate, and no mechanism to prevent them from becoming stale.

In a regulated environment, that is not good enough. An FCA-regulated firm that makes a technology architecture decision without documented review, without separation between proposer and approver, and without a traceable link to the EA principles it was measured against, has an audit exposure. The decision happened. It just cannot be proven to have been governed.

HelixGate treats the ADR as a governed artefact, not a document. The seven-phase lifecycle — Draft, Peer Review, ARB Review, Authority Decision, Ratified, Superseded, Rejected — enforces separation of duties at every gate. Authority routing is risk-based: a Low-risk decision can be fast-tracked through TDA. A High or Critical decision must clear the ARB with quorum. The reasoning, the votes, and the delegation chain are all part of the immutable record.

Supersession is first-class, not a workaround. When a decision is replaced, the original record is locked and linked to its successor. The architecture history is readable; the current state is unambiguous.

Further reading
§ Closing statement

Stop archiving decisions in Confluence.

Walk us through your last big architecture call — we’ll show how the seven-phase lifecycle would have made it defensible.