Capability

Govern every architecture decision at design time, with evidence attached.

Every model has a governance plane: ADRs, business decision records, motivation, value-streams, evidence_refs. Audit trail is the primitive, not an afterthought.

What it is

Design-time governance means decisions are typed entities, not Markdown files that drift. Archally's governance plane holds D### Architecture Decision Records and business decision records side-by-side with the bounded contexts they affect, the value-streams they serve, and the evidence (EVD###) that backs them. Change impact analysis traces what a proposed model change touches across composed contexts and verticals before it ships - closing the gap that traditional documentation tools cannot.

Built on

  • D### ADR entity with status / context / decision / consequence fields
  • Business decision record scoped to bounded contexts
  • evidence_refs cross-references across every plane
  • Migration record per vertical with semver impact + rationale capture
  • modelDiff + impact-report MCP for cross-vertical impact tracing

How it works

Capture an ADR or business decision record as a YAML entity in .blueprint/v{N}/governance/. Link it to the bounded contexts it scopes (bounded_context_ref), the evidence_refs that informed it, and the value-stream it serves. Run the modelDiff GraphQL query or the impact-report MCP tool against any change. The system returns the cross-vertical impact set: which contexts, decisions, and migrations are touched, with rationale-aware change history attached.

While not mandated for day-to-day team decisions, ADRs will be required for anything brought to the Technical Design Council.
- UK Government Technology Blog, “The Architecture Decision Record (ADR) Framework” (December 2025)