Capability
Govern every architecture decision at design time, with evidence attached.
Every model has a governance plane: ADRs, business decisions (BCC v5 BD###), 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 BD### business decisions 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
- BD### business decision entity scoped to bounded contexts (BCC v5)
- 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 BD### 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.
- $15B → $17.5B Decision Intelligence market (16.5% CAGR) thinking.EVD017
- Dec 2025 UK Government ADR Framework rollout thinking.EVD001
- 10 BCC v5 model_traits enum values (analyser, executor, drafter, auditor, controller, service-provider, information-holder, structurer, coordinator, interfacer) composition.EVD038