Architecture Synthesis derives where computation happens — deployment topology, data placement, consistency boundaries — from service-level objectives, instead of choosing it from a catalog of styles. Derived, not chosen.
The method runs on nine questions, translated into six architecture axes through a fixed set of rules, and closed with verification arithmetic: back-of-envelope capacity math that checks a derived architecture against its own budget before anything gets built. An architecture produced this way is never a one-time choice. It is re-derived whenever the answers to those nine questions change — on a greenfield system and on one you inherited, by the same procedure.
A practicing architect can start here directly; a reader arriving from Process-First Design will recognize this as the next step.
Four architectures have been derived blind, against a locked answer sheet, and graded against what those systems actually run — in the open, with the misses shown alongside the hits. The registered predictions, answer sheets, operator prompts, and grading rubrics are public in a replication kit. Every derivation after the first four is registered there before its outcome is checked, and counterexamples are invited.
The method runs in your browser. Event ticketing at three scales — an independent venue, a regional platform, an enterprise platform — as three answer sheets over one domain. Only the answers differ; the procedure is identical. Load them in turn and watch the derivation move: the venue derives the null vector and every demand presses nothing, while the enterprise sheet forces five axes, each citing the answer behind it and the mechanism that justifies it.
That is the difference between a procedure and a worked example. You cannot take the example in a design book and re-run it with different requirements to compute a different architecture; the example demonstrates the author’s taste after the fact. Here, changing an answer changes the output, deterministically, in a few hundred lines of ordinary code with no model involved. Where the method refuses to decide — targets, recovery ties, contradictions, product picks — it says so and hands the question back.
The book — Architecture Synthesis: The Next Correct Step — is on Leanpub. The free course edition walks the whole derivation lesson by lesson, each paired with an exercise you run on a system you own.