Architecture diagrams¶
The architecture defines the target model. The views in workspace.dsl, run sequence and run state describe its responsibilities, not a release or qualification claim. For available commands and SDK interfaces use the package references and host reference.
Context shows users, the platform and native systems.
Composition shows campaign orchestration, a finite attempt, document evaluation and retained evidence.
Native interfaces separates SDK control and media from the document path.
Consumer interfaces shows offline MCP, custom assessment and the external attempt boundary.
External Test API shows producer metadata and custody; it does not own native execution.
Complete graph includes the modeled paths.
Local execution and Kubernetes execution illustrate deployments. The local and Kubernetes campaign profiles are alternatives.
Sequence and state show evidence-before-cleanup and independent evaluation.
A C4 container is an application or data store, not a Python package or an OCI image. Native process, GPU-memory and IPC boundaries depend on the selected profile. Provisioning is described in the infra architecture.
Rendering¶
Edit DSL and Mermaid sources, not generated SVGs. render.sh uses pinned Structurizr and Mermaid CLI images with the shared theme. From the repository root:
CONTAINER_ENGINE=podman docs/architecture/render.sh
python3 docs/architecture/publish_readme.py --check
Review generated views for readable labels, arrow directions and consistency with the architecture.