Repository navigation
Expand file tree
/
Copy pathindex.html
More file actions
232 lines (221 loc) · 21.7 KB
/
Copy pathindex.html
File metadata and controls
232 lines (221 loc) · 21.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Transitrix — open methodology and tools for enterprise as text</title>
<meta name="description" content="You leave with a decision you can keep true. 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.">
<link rel="canonical" href="https://transitrix.com/">
<meta property="og:type" content="website">
<meta property="og:url" content="https://transitrix.com/">
<meta property="og:title" content="Transitrix — open methodology and tools for enterprise as text">
<meta property="og:description" content="You leave with a decision you can keep true. 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.">
<meta property="og:image" content="https://transitrix.com/assets/og/transitrix-og.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:locale" content="en_US">
<meta property="og:locale:alternate" content="de_DE">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:image" content="https://transitrix.com/assets/og/transitrix-og.png">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:ital,wght@0,400;0,600;1,400&family=IBM+Plex+Mono:wght@400&display=swap" rel="stylesheet">
<link rel="stylesheet" href="assets/css/style.css">
<link rel="icon" type="image/svg+xml" href="/assets/img/transitrix-icon.svg">
<link rel="icon" type="image/png" sizes="16x16" href="/assets/img/favicon-16.png">
<link rel="icon" type="image/png" sizes="32x32" href="/assets/img/favicon-32.png">
<link rel="icon" type="image/png" sizes="128x128" href="/assets/img/favicon-128.png">
<link rel="apple-touch-icon" sizes="256x256" href="/assets/img/apple-touch-icon.png">
<meta name="theme-color" content="#004D67">
<link rel="alternate" hreflang="de" href="de/">
<link rel="alternate" hreflang="en" href="./">
<script>if(localStorage.getItem('theme')==='light')document.documentElement.setAttribute('data-theme','light');</script>
<!-- Cloudflare Web Analytics -->
<script defer src="https://static.cloudflareinsights.com/beacon.min.js" data-cf-beacon='{"token": "1d2971bbe7964ede92ee02e5c78da48c"}'></script>
<!-- End Cloudflare Web Analytics -->
</head>
<body>
<a class="skip-link" href="#main">Skip to main content</a>
<header class="site-header">
<div class="wrap">
<a class="logo" href="./">Transitrix</a>
<div class="header-right">
<button class="theme-toggle" id="theme-toggle" aria-label="Toggle theme">
<svg class="icon-moon" width="15" height="15" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M21 12.79A9 9 0 1 1 11.21 3 7 7 0 0 0 21 12.79z"/></svg>
<svg class="icon-sun" width="15" height="15" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><circle cx="12" cy="12" r="5"/><line x1="12" y1="1" x2="12" y2="3"/><line x1="12" y1="21" x2="12" y2="23"/><line x1="4.22" y1="4.22" x2="5.64" y2="5.64"/><line x1="18.36" y1="18.36" x2="19.78" y2="19.78"/><line x1="1" y1="12" x2="3" y2="12"/><line x1="21" y1="12" x2="23" y2="12"/><line x1="4.22" y1="19.78" x2="5.64" y2="18.36"/><line x1="18.36" y1="5.64" x2="19.78" y2="4.22"/></svg>
</button>
<nav class="lang-switch" aria-label="Language">
<a href="./" aria-current="true">EN</a>
<a href="de/" hreflang="de">DE</a>
</nav>
</div>
<nav class="site-nav" aria-label="Primary">
<ul>
<li><a href="/learn/">Learn</a></li>
<li><a href="/dsl-examples/">Examples</a></li>
<li><a href="https://github.com/transitrix/methodology" target="_blank" rel="noopener noreferrer">Methodology</a></li>
<li><a href="/library/">Library</a></li>
<li><a href="/install/">Install & start</a></li>
</ul>
</nav>
</div>
</header>
<main id="main" class="wrap" tabindex="-1">
<div class="hero">
<h1>Enterprise as text.<br>Run by humans and machines together.</h1>
<p class="lede">
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.
</p>
<p class="lede-sub">
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.
</p>
<div class="hero-actions">
<a class="btn" href="install/">Install & start</a>
<a class="btn" href="https://github.com/transitrix/methodology">Read the methodology</a>
</div>
</div>
<section aria-labelledby="ways-in-heading">
<h2 id="ways-in-heading">Two ways in</h2>
<div class="stack-grid">
<article class="card">
<div class="card-meta">5 minutes · nothing to set up</div>
<h3>Draw a diagram</h3>
<p>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.</p>
<a class="card-link" href="install/">Install Studio →</a>
</article>
<article class="card">
<div class="card-meta">team · methodology-first</div>
<h3>Set up an architecture repository</h3>
<p>Adopt Transitrix for your organisation. One prompt to a coding agent scaffolds a structured repository and CI validates every change.</p>
<a class="card-link" href="https://github.com/transitrix/methodology">Methodology quick start →</a>
</article>
</div>
</section>
<section aria-labelledby="about-heading">
<h2 id="about-heading">What this is</h2>
<p><strong>Architecture-as-Code for the enterprise</strong> — the git-native, text-first discipline software already has, carried up to the strategy, business and architecture layers that code-scoped tools never reach.</p>
<p><strong>Against code-scoped tools.</strong> 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.</p>
<p><strong>Against context and memory layers.</strong> 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.</p>
</section>
<section aria-labelledby="stack-heading">
<h2 id="stack-heading">The stack</h2>
<p class="section-intro">Two units are open today. Two more extend the same thesis.</p>
<div class="stack-grid">
<article class="card">
<div class="card-meta">methodology · open</div>
<h3>Transitrix</h3>
<p>The foundation. A text-native way to model an organisation — goals, processes, capabilities, and structure — as code. Says <em>how</em> to describe an enterprise so it remains readable, versionable, and executable.</p>
<a class="card-link" href="https://github.com/transitrix/methodology">View on GitHub →</a>
</article>
<article class="card">
<div class="card-meta">tool · open</div>
<h3>Transitrix Studio</h3>
<p>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.</p>
<a class="card-link" href="#studio-features">Explore Studio features →</a>
<a class="card-link" href="install/">Install →</a>
</article>
</div>
<div class="stack-subhead">On the roadmap</div>
<div class="stack-grid stack-grid--secondary">
<article class="card">
<div class="card-meta">strategy product · not yet public</div>
<h3>Transitrix DSM</h3>
<p>Dynamic strategy management that operates on the Transitrix model, updating as the enterprise model changes — not yet publicly available.</p>
<a class="card-link" href="dsm/">More on Transitrix DSM →</a>
</article>
<article class="card">
<div class="card-meta">research · phase 2</div>
<h3>Transitrix Swarm</h3>
<p>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.</p>
</article>
</div>
<p>Neither is open. <a href="strategy-and-behaviour/">See what they do and how to see them working →</a></p>
</section>
<section aria-labelledby="studio-features">
<h2 id="studio-features">What you can do with Transitrix Studio</h2>
<p>Updated for <strong>Studio 3.8.0</strong> in VS Code-compatible editors, the separately installed <strong>CLI 2.10.0</strong>, and <strong>Methodology 7.0.0</strong>. JetBrains support is described separately below; check its <a href="https://plugins.jetbrains.com/plugin/32282-transitrix-studio">marketplace listing</a> for the available plugin version.</p>
<ul>
<li><strong>Connect strategy to delivery.</strong> 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/extension/README.md#17-notations-one-extension">Notation guide</a>.</li>
<li><strong>Describe processes in text.</strong> 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/README.md#quick-start--bpmn">BPMN quick start</a>.</li>
<li><strong>Explore capabilities and catalogues.</strong> 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/extension/README.md#17-notations-one-extension">Format overview</a> · <a href="https://github.com/transitrix/transitrix-studio/blob/main/docs/validation.md#diagnostic-conformance-and-capability-history">Capability history</a>.</li>
<li><strong>Trace requirements and review release coverage.</strong> In VS Code, open <strong>Transitrix: Traceability Matrix</strong> to follow links upstream or downstream, focus on a selected element and compare adjacent columns. <strong>Transitrix: Requirements by Release</strong> 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/README.md#release-scoped-requirement-reports">Requirements reports</a>.</li>
<li><strong>Inspect compliance and verification.</strong> 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/docs/validation.md#compliance-suite---scoperepo-518">Compliance validation</a>.</li>
<li><strong>Record numerical risk degrees.</strong> 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/docs/validation.md#authored-numeric-risk-degrees">Numeric risk authoring</a>.</li>
<li><strong>Share diagrams and findings.</strong> 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/extension/README.md#17-notations-one-extension">Preview exports</a> · <a href="https://github.com/transitrix/transitrix-studio/blob/main/docs/cli.md#commands">CLI commands</a>.</li>
<li><strong>Create consistent model elements.</strong> VS Code commands and the CLI scaffold goals, drivers, constraints and requirements with admission and lifecycle fields, checking IDs and references before writing. <a href="https://github.com/transitrix/transitrix-studio/blob/main/extension/README.md#creating-a-new-element">Element creation</a>.</li>
<li><strong>Check models in scripts and CI.</strong> 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/docs/cli.md">CLI reference</a> · <a href="https://github.com/transitrix/transitrix-studio/blob/main/docs/validation.md#validation-scope-file-vs-repo">Validation scope</a>.</li>
</ul>
<p><strong>Choose your host:</strong> the VS Code extension (also installable in compatible Cursor, VSCodium and Windsurf editors) opens recognised previews automatically and refreshes them <strong>on save</strong>; autosave can shorten the edit–preview loop. <a href="https://github.com/transitrix/transitrix-studio/blob/main/extension/README.md#get-started-in-3-steps">Preview settings</a>.</p>
<p>The <strong>JetBrains plugin</strong> requires a compatible IDE with JCEF (platform builds 242–262). Open <strong>Transitrix: Preview Notation</strong> from the editor's context menu. Its read-only preview is a <strong>snapshot: close and reopen it after editing</strong>. 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. <a href="https://github.com/transitrix/transitrix-studio/blob/main/intellij/README.md#installing-in-intellij-idea">JetBrains installation</a>.</p>
<p>The editor plugins bundle their renderers; the <strong>CLI is a separate installation</strong>, not a command added to your shell by installing an editor plugin. No DSM installation is required for the capabilities listed here. <a href="https://github.com/transitrix/transitrix-studio/blob/main/README.md#cli">Install the CLI</a>.</p>
</section>
<section aria-labelledby="see-heading">
<h2 id="see-heading">See it work</h2>
<p>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.</p>
<figure class="product-shot">
<img src="assets/img/studio-preview.gif" alt="Transitrix Studio in VS Code: a goals-tree source file on the left; on the right, the preview shows a newly added goal branch." loading="lazy" width="700" height="394">
<figcaption>Transitrix Studio — a Transitrix source file and its live preview, refreshing on save.</figcaption>
</figure>
</section>
<section aria-labelledby="layers-heading">
<h2 id="layers-heading">One model, every layer</h2>
<p>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.</p>
<ul>
<li><strong>Business-facing layers — Transitrix Studio.</strong> 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.</li>
<li><strong>Technical layers — PlantUML.</strong> Sequence, state, ER/class, and C4 component diagrams — generated from the same model — render in <a href="https://plantuml.com/">PlantUML</a>, 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.</li>
<li><strong>Mermaid, as a fallback.</strong> Where a lighter, quicker view is enough, the same layers also render in standard <a href="https://mermaid.js.org/">Mermaid</a>, via the recommended editor extension.</li>
</ul>
<p class="note">ArchiMate 3.2 and BPMN 2.0 are foundations, with deliberate modelling choices and explicit interoperability limits. Read <a href="semantic-standards/">Semantic Standards and Interoperability</a> for the profile and maintained differences register. Models remain 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.</p>
</section>
<section aria-labelledby="open-heading">
<h2 id="open-heading">What's open today</h2>
<p>Both the methodology and Transitrix Studio are public. The methodology specification lives at <a href="https://github.com/transitrix/methodology">github.com/transitrix/methodology</a>. 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 <a href="install/">install options</a>. Source at <a href="https://github.com/transitrix/transitrix-studio">github.com/transitrix/transitrix-studio</a>. For the exact shape of every notation, see the <a href="dsl-examples/">model examples</a> reference; recipes — prose with directives, named <code>*.<kind>.ttrs</code> — are described on <a href="recipes/">the <code>.ttrs</code> recipe format</a> page.</p>
<p>If you are evaluating Transitrix for a pilot or want to follow the work, reach out at <a href="mailto:hello@transitrix.com">hello@transitrix.com</a>.</p>
<div class="note">
<strong>Follow releases</strong> — subscribe via Atom/RSS: <a href="https://github.com/transitrix/transitrix-studio/releases.atom">Transitrix Studio</a> · <a href="https://github.com/transitrix/methodology/releases.atom">Methodology</a>. Add either URL to any RSS/Atom reader, or use GitHub's Watch → Releases on each repository.
</div>
</section>
<section aria-labelledby="library-heading">
<h2 id="library-heading">Free reference material</h2>
<p>Cheat sheets, templates and worked examples — read on the page, take the PDF away. No sign-up, no email, no gate. <a href="library/">Browse the library →</a></p>
</section>
<section aria-labelledby="explainers-heading">
<h2 id="explainers-heading">Explainers</h2>
<p>One subject per page, in more depth than this front page goes. <a href="explainers/">Read the explainers →</a></p>
</section>
<section aria-labelledby="learn-heading">
<h2 id="learn-heading">Learn</h2>
<p>Eight steps from "What is this?" to your first diagram. About 20–30 minutes. <a href="learn/">Start the learning path →</a></p>
</section>
<section aria-labelledby="questions-heading">
<h2 id="questions-heading">Questions, answered</h2>
<ul class="qs-viewers">
<li><a href="what-is-transitrix/">What is Transitrix?</a></li>
<li><a href="enterprise-as-text/">What does "enterprise as text" mean?</a></li>
<li><a href="vs-drawing-tools/">How is this different from drawing tools?</a></li>
<li><a href="which-editor/">Which editor do I use?</a></li>
<li><a href="is-it-open-source/">Is Transitrix open source?</a></li>
<li><a href="what-can-i-model/">What can I model?</a></li>
<li><a href="capability-maps/">Business capabilities, system coverage and time</a></li>
<li><a href="do-i-need-dsm/">Do I need DSM to get started?</a></li>
</ul>
</section>
</main>
<footer class="site-footer">
<div class="wrap">
<div class="footer-inner">
<p>
<a href="https://github.com/transitrix">github.com/transitrix</a> ·
<a href="https://x.com/transitrix">@transitrix</a>
</p>
<nav class="lang-switch" aria-label="Language">
<a href="./" aria-current="true">EN</a>
<a href="de/" hreflang="de">DE</a>
</nav>
</div>
<p class="footer-attribution">Created and maintained by Valerii Korobeinikov — enterprise-architecture advisory at <a href="https://korobeinikov.consulting">korobeinikov.consulting</a></p>
</div>
</footer>
<script src="assets/js/theme.js"></script>
</body>
</html>