Draw a diagram
Write a few lines of text, see a diagram. Install the Studio extension and open a recognised file in VS Code — the preview refreshes on save.
Install Studio →Enterprise as text.
Run by humans and machines together.
You leave with a decision you can keep true. Not a report of one — the model the decision was made in, in your own repository, and the method to keep it current after we are gone.
Architecture-as-Code for the enterprise — the git-native, text-first discipline software already has, carried up to the strategy, business and architecture layers that code-scoped tools never reach.
Two ways in
Set up an architecture repository
Adopt Transitrix for your organisation. One prompt to a coding agent scaffolds a structured repository and CI validates every change.
Methodology quick start →What this is
Architecture-as-Code for the enterprise — the git-native, text-first discipline software already has, carried up to the strategy, business and architecture layers that code-scoped tools never reach.
Against code-scoped tools. Architecture-as-Code exists today and stops at software. The layers where the money is committed — motivation, strategy, business — are the ones it never reaches, and they are the ones this covers.
Against context and memory layers. This is a formal model, not free-form notes and not opaque embeddings. It validates, it diffs, and a change to it is reviewed the way a change to code is reviewed. A machine can act on it because it is grounded, not because it was remembered.
The stack
Two units are open today. Two more extend the same thesis.
Transitrix
The foundation. A text-native way to model an organisation — goals, processes, capabilities, and structure — as code. Says how to describe an enterprise so it remains readable, versionable, and executable.
View on GitHub →Transitrix Studio
The unified editor extension and CLI to author and preview Transitrix formats — the reference implementation of the methodology. Preview strategy, processes, capabilities and catalogues, with the host differences described below.
Explore Studio features → Install →On the roadmap
Transitrix DSM
Dynamic strategy management that operates on the Transitrix model, updating as the enterprise model changes — not yet publicly available.
More on Transitrix DSM →Transitrix Swarm
A research platform for modelling what agents do inside a Transitrix-described enterprise. The behaviour layer of the stack. In narrative; not in active development in the next six months.
Neither is open. See what they do and how to see them working →
What you can do with Transitrix Studio
Updated for Studio 3.8.0 in VS Code-compatible editors, the separately installed CLI 2.10.0, and Methodology 7.0.0. JetBrains support is described separately below; check its marketplace listing for the available plugin version.
- Connect strategy to delivery. Preview goal trees, driver–goal–change–activity chains (DGCA/DGA), activity networks and activity cards. VS Code also offers Gantt and critical-path views, plus completion percentages when model progress records are available. Notation guide.
- Describe processes in text. Preview process maps and stage-by-stage process blueprints. In VS Code, author BPMN in YAML and preview the diagram; the CLI compiles it to BPMN 2.0 XML with automatic layout. BPMN quick start.
- Explore capabilities and catalogues. Preview applications, products, nested blocks and supported inline scenarios. In VS Code, capability maturity is read from dated history records as of the current date. Catalogue previews depend on the supported document form. Format overview · Capability history.
- Trace requirements and review release coverage. In VS Code, open Transitrix: Traceability Matrix to follow links upstream or downstream, focus on a selected element and compare adjacent columns. Transitrix: Requirements by Release shows scope-specific counts with drill-down lists. Both reports share product, project, release and date selection, retain navigation context and refresh after model changes. They require the corresponding model records. Requirements reports.
- Inspect compliance and verification. VS Code provides compliance impact and coverage views, a gap dashboard, and a separate requirement–verification matrix for requirements, assertions and verification results. These views need the corresponding model records. Compliance validation.
- Record numerical risk degrees. Author likelihood, impact and residual risk as numbers on an explicit adopter-defined scale in Methodology 7.0.0 models, and check them with the CLI. Existing qualitative values remain supported. Numeric risk authoring.
- Share diagrams and findings. VS Code saves supported diagram previews as SVG or PNG. Export the gap dashboard and requirement–verification matrix as CSV, or the Traceability Matrix and Requirements by Release snapshot as JSON. PNG clipboard copying is Windows-only. The CLI exports compliance reports as Markdown or PDF; PDF requires the optional WeasyPrint executable. Preview exports · CLI commands.
- Create consistent model elements. VS Code commands and the CLI scaffold goals, drivers, constraints and requirements with admission and lifecycle fields, checking IDs and references before writing. Element creation.
- Check models in scripts and CI. The CLI validates individual files or repository models and emits JSON findings with file-coverage counts. Unsupported forms are explicitly reported as unvalidated and fail strict repository validation. The model's methodology version selects the applicable ACTION numeric rules. The CLI runs independently of either editor and requires Node.js 20 or newer. CLI reference · Validation scope.
Choose your host: the VS Code extension (also installable in compatible Cursor, VSCodium and Windsurf editors) opens recognised previews automatically and refreshes them on save; autosave can shorten the edit–preview loop. Preview settings.
The JetBrains plugin requires a compatible IDE with JCEF (platform builds 242–262). Open Transitrix: Preview Notation from the editor's context menu. Its read-only preview is a snapshot: close and reopen it after editing. It supports strategy, process-map/blueprint and supported catalogue previews, but does not include BPMN, the VS Code requirements/compliance reports or SVG/PNG export commands. Capability history requires the VS Code or repository-validation context; JetBrains cannot resolve it for a standalone preview. JetBrains installation.
The editor plugins bundle their renderers; the CLI is a separate installation, not a command added to your shell by installing an editor plugin. No DSM installation is required for the capabilities listed here. Install the CLI.
See it work
A few lines of text become a diagram you can read, review, and version. You author a Transitrix file in VS Code; the preview refreshes alongside it on save. Autosave can shorten the loop.
One model, every layer
You describe your enterprise once, as text. Two editor extensions render that single model across every layer — so the same source serves the boardroom and the codebase.
- Business-facing layers — Transitrix Studio. Purpose-built notations for strategy and operations: goals trees, capability maps, process blueprints, BPMN, and activity networks. Built for the business/IT interface, not stripped-down copies of generic diagrams.
- Technical layers — PlantUML. Sequence, state, ER/class, and C4 component diagrams — generated from the same model — render in PlantUML, natively inside Studio: no Java, no Graphviz, works even in the browser via vscode.dev. Studio previews PlantUML the way it previews Markdown — a foreign format, not a Transitrix notation.
- Mermaid, as a fallback. Where a lighter, quicker view is enough, the same layers also render in standard Mermaid, via the recommended editor extension.
Built on open standards — ArchiMate 3.2 and BPMN 2.0 — with everything as plain, diffable text. Nothing is locked in: the technical views are standard PlantUML and Mermaid, and your files stay readable with or without our tooling.
What's open today
Both the methodology and Transitrix Studio are public. The methodology specification lives at github.com/transitrix/methodology. Transitrix Studio’s editor plugins install into VS Code, compatible Cursor, VSCodium and Windsurf editors, and compatible JetBrains IDEs; the CLI installs separately. See the install options. Source at github.com/transitrix/transitrix-studio. For the exact shape of every notation, see the DSL examples reference; recipes — prose with directives, named *.<kind>.ttrs — are described on the .ttrs recipe format page.
If you are evaluating Transitrix for a pilot or want to follow the work, reach out at hello@transitrix.com.
Follow releases — subscribe via Atom/RSS: Transitrix Studio · Methodology. Add either URL to any RSS/Atom reader, or use GitHub's Watch → Releases on each repository.
Free reference material
Cheat sheets, templates and worked examples — read on the page, take the PDF away. No sign-up, no email, no gate. Browse the library →
Explainers
One subject per page, in more depth than this front page goes. Read the explainers →
Learn
Eight steps from "What is this?" to your first diagram. About 20–30 minutes. Start the learning path →