Skip to content

ADR-032 Structurizr Workspace (2026 Q2)

Status: Initial bounded workspace after Wave42 Model file: structurizr/adr-032/workspace.dsl

This page describes the initial Structurizr/C4 workspace for the ADR-032 line. It is the bounded architecture-as-code layer added after the documentation maturity pass.

Why this exists

The current ADR-032 line already had:

  • a normative ADR
  • a historical rollout plan
  • a maintainer overview
  • a building-block view
  • quality scenarios

The missing piece was a machine-readable architecture model. This workspace closes that gap without changing runtime behavior.

What it models

The workspace models:

  • system context for the Assay MCP policy stack
  • container structure for runtime and evidence/replay responsibilities
  • component structure for:
  • policy runtime
  • evidence and replay layer

Why Structurizr here

As of March 2026, Structurizr’s DSL provides a text-based way to define a software architecture model based on the C4 model, and the DSL supports imported Markdown/AsciiDoc documentation via !docs. It also supports inspections for missing descriptions, missing documentation, missing views, and missing relationship descriptions.

Sources: - Structurizr DSL - Structurizr language reference - Structurizr inspections - C4 model

Workspace Contents

Intended Workflow

Use the workspace for:

  1. local model inspection
  2. diagram export
  3. inspection/validation
  4. architecture review support

Relevant Structurizr tooling/docs: - Structurizr local - Structurizr documentation - Structurizr component view cookbook - Structurizr system context cookbook

CI Validation

The workspace is validated in CI via .github/workflows/structurizr-validate.yml on changes to docs/architecture/structurizr/.

Local validation and export:

bash scripts/structurizr-validate.sh   # validate DSL
bash scripts/structurizr-export.sh     # export Mermaid diagrams

Exported Mermaid views are in structurizr/adr-032/export/.

Scope Discipline

This workspace is intentionally bounded. It does not add:

  • automatic ADR import via !adrs
  • generated static-site publishing of Structurizr exports
  • code-discovered components via !components

Those are possible later as separate bounded follow-ups.

Relationship to the Canonical Docs