diff --git a/MANIFEST.md b/MANIFEST.md index 7836726..729cc6e 100644 --- a/MANIFEST.md +++ b/MANIFEST.md @@ -42,6 +42,8 @@ admits future files. - `explainers/how-the-repository-works/how-the-repository-works.pdf` - `explainers/how-the-repository-works/index.html` - `explainers/index.html` +- `explainers/what-is-architecture-as-code/index.html` +- `explainers/what-is-architecture-as-code/what-is-architecture-as-code.pdf` - `favicon.ico` - `index.html` - `install/go/claude/index.html` diff --git a/explainers/SHA256SUMS b/explainers/SHA256SUMS index 7a12795..f0e114c 100644 --- a/explainers/SHA256SUMS +++ b/explainers/SHA256SUMS @@ -1,2 +1,3 @@ 8ae367f04698355742ee093740ed148a5ebd9a139b80e161788215c2ff4098f0 how-a-document-prints/how-a-document-prints.pdf c694fa298d6279f00da62236956592de9207c4f62c5c4e318c5634015d1e901d how-the-repository-works/how-the-repository-works.pdf +22c60a38dad79e467ecef08103b0a121ed14d6f15d984a80ed6ab1fd9fb67866 what-is-architecture-as-code/what-is-architecture-as-code.pdf diff --git a/explainers/index.html b/explainers/index.html index 75e11ea..3f14c3d 100644 --- a/explainers/index.html +++ b/explainers/index.html @@ -56,12 +56,17 @@

Explainers

-

One subject per page, in more depth than the front page goes. Read online — no PDF, no sign-up.

+

One subject per page, in more depth than the front page goes. Read online, with a one-page PDF where available. No sign-up.

Explainers

+
+

What is architecture-as-code?

+

The problem, the approach and what remains with your team. Read online or take the one-page PDF.

+ Read it → +

Governed access to your enterprise model

Repository MCP: who can see and change what, and how to choose a deployment and implementation path.

diff --git a/explainers/what-is-architecture-as-code/index.html b/explainers/what-is-architecture-as-code/index.html new file mode 100644 index 0000000..605aa33 --- /dev/null +++ b/explainers/what-is-architecture-as-code/index.html @@ -0,0 +1,97 @@ + + + + + + What is architecture-as-code? | Transitrix + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+ +
+ +
+
+
+

What is architecture-as-code?

+

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.

+

Download the one-page PDF

+
+

The problem

+

A system is retired. A diagram still shows it. A process changes. The document does not.

+

The same facts live in separate diagrams, documents and spreadsheets. Before a decision can use them, someone has to work out which copies are still true.

+

The work changes: people maintain the shared description and review changes, rather than reconcile separate copies.

+
+

How it works

+

Describe the organisation once

Plain-text files name goals, processes, systems, owners and their relationships. Together, these records form the model.

+

Generate what you need to see

Diagrams and reports show selected parts of that model. They are produced from the same records instead of being edited as separate copies.

+

Review and check each change

A repository keeps the files and their history. Proposed changes are reviewed; automatic checks flag broken rules and references.

+
+

What stays with you

+

A description you can inspect Your team can read the records, see their history and propose the next change.

+

Connections you can follow Trace the recorded links from a system to the processes and goals that depend on it.

+

A way to keep it useful The model and review practice remain with your team after an engagement ends.

+
+
+

Architecture-as-Code for the enterprise

+

That is what Architecture-as-Code for the enterprise is for: the git-native, text-first discipline software already has, carried up to the strategy, business and architecture layers that code-scoped tools never reach. The enterprise is described once, in plain text, and every view — a goal tree, a capability map, a sequence diagram — is projected from that one description.

+
+

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.

+
+ +
+ + + + diff --git a/explainers/what-is-architecture-as-code/what-is-architecture-as-code.pdf b/explainers/what-is-architecture-as-code/what-is-architecture-as-code.pdf new file mode 100644 index 0000000..76f1e59 Binary files /dev/null and b/explainers/what-is-architecture-as-code/what-is-architecture-as-code.pdf differ diff --git a/sitemap.xml b/sitemap.xml index d37b3e7..f271ba3 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -37,6 +37,10 @@ https://transitrix.com/explainers/how-the-repository-works/ + + https://transitrix.com/explainers/what-is-architecture-as-code/ + + https://transitrix.com/install/