Make architecture explicit, versionable, and checkable
Architecture as Code turns architecture from documentation into executable, checkable specifications that live alongside your code. Define interfaces explicitly, version changes in Git, and keep architecture in sync with implementation.
Core Concepts
Architecture as Code (DSL)
Define your system architecture in a domain-specific language. Text-based, versioned in Git, and readable by both humans and tools. Architecture becomes part of your codebase, not separate from it.
Interfaces as first-class concepts
Explicitly define interfaces between components. What data flows, what protocols are used, what each component expects. When interfaces change, you can see the impact immediately.
Multidisciplinary by design
Model software, electronics, and mechanical systems together. Understand how different disciplines interact and depend on each other. One architecture, multiple domains.
Git-based workflows
Architecture changes go through the same review process as code. Pull requests, code reviews, and version history. Architecture evolves with the product, not separately.
What It's Not
- • Not SysML: We're not building another modeling language. We're making architecture practical and usable.
- • Not heavy MBSE: No complex toolchains or heavyweight processes. Just architecture that works.
- • Not documentation: Architecture as Code is executable, checkable, and part of your development workflow.