Architecture
Templates

The artefact engineers fill in to record an architectural decision — recognising that the ADR's title precision, status lifecycle, context articulation, decision specificity, consequence enumeration (intended outcomes and accepted trade-offs), and reference anchoring are what determine whether the document accumulates as institutional memory the team can navigate years later or as historical noise that doesn't help anyone.

The artefact a review produces — recognising that the template's scope statement, severity-classified findings, actionable per-finding messages, documented decisions with named authority, captured reviewer-author dialogue, and outcome-traceability to system change are what determine whether the review document is a binding decision artefact or a record of meetings that didn't actually resolve anything.

The artefact that rates a service across architecturally important dimensions — recognising that the scorecard's documented per-dimension criteria, level-based scoring (not aspirational numerics), calibration against actual operational outcomes, aggregation into portfolio views without reduction to a single composite number, owner-driven completion with peer review, and tracked improvement trajectory over time are what determine whether the scorecard becomes a portfolio-visibility instrument that drives investment decisions or a one-time exercise that produces ratings nobody trusts or revisits.