RWS Architecture article

Workflow - Architecture Promotion Checklist

Use this checklist to move architecture notes through maturity with low overhead.

  1. Typefact
  2. Statusactive
  3. Domainplatform
On this page
  1. Status Gates
  2. Draft -> Active
  3. Active -> Approved
  4. Any -> Archived
  5. Fast Review Pattern (10 Minutes)
  6. Rule of Thumb

Use this checklist to move architecture notes through maturity with low overhead.

Status Gates

Draft -> Active

Promote when all items are true:

  • The problem/scope is clear and bounded.
  • At least one realistic target-state architecture is documented.
  • Major assumptions and open questions are explicit.
  • The note links to relevant ADRs (decided_by) where decisions exist.
  • A delivery team can implement safely without oral-only context.

Active -> Approved

Promote when all items are true:

  • Critical decisions are accepted and linked ADRs are stable.
  • Cross-domain dependencies and impacts are documented.
  • Applicable principles are mapped and reflected in the architecture.
  • Main risks and operational consequences are documented.
  • Governance review has explicitly accepted this note as baseline.

Any -> Archived

Archive when both are true:

  • The architecture is replaced or no longer part of target state.
  • A successor note is linked via superseded_by where applicable.

Fast Review Pattern (10 Minutes)

  1. Read ## Summary and ## Architecture.
  2. Verify decision chain in decided_by.
  3. Verify principle alignment in ## Applicable Principles.
  4. Decide one action: keep draft, promote, or request targeted updates.

Rule of Thumb

  • Keep notes in draft by default while learning.
  • Promote to active as soon as implementation can safely consume the note.
  • Do not wait for perfection; use small, frequent updates.