The reusable machinery for solution decisions — model the requirements, lay out solutions as compositions of buy·rent·build + integration, and compare them on Gate · Fit · Cost · Risk under one shared scenario.
The same machinery, two vantage points — linked, not separate. The Methodology explains how decisions are made; the Architecture, how the system is built.
The decision loop: requirements → candidate solutions → one shared scenario → scoring on Gate · Fit · Cost · Risk. Sharpness and forks: which question to resolve next.
The five layers, the data contract (schema as shape-truth), kernel and shell, building a cockpit, extending per project. With a field reference generated from the schema.
Every cockpit is made of the same five layers. The one load-bearing distinction: kernel and shell are pinned (never edited in the consumer), the template is copied and filled. Each layer leads to its detail page.
One tiny decision — keeping cats off the kitchen counter — runs through the entire methodology once and shows, for each phase, where it lands in the data and the architecture. The fastest way to see both views at once.