The Reference Architecture, Worked: Stack as Blueprint
The stack-to-architecture bridge (BR.11) established the reference architecture as a deliverable; this is the worked example. The reference architecture is the sovereign stack drawn as a blueprint — the components, the connections, the trust chain, the data flows — packaged so a client can understand the whole system and, if they choose, rebuild it. The blueprint is both a product and the proof that the stack is a system, not a pile of tools.
What the blueprint contains
The reference architecture has five layers, matching the stack’s own structure: the mesh (the actor layer, S1 series — how agents are organized), the knowledge layer (the vault and graph — how memory is stored and queried, S3 series), the skills layer (the capability library — what agents can do, S4 series), the governance layer (the orders and gates — how decisions are made and gated, S7 series), and the surface layer (the studio and business services — what the stack produces, S9/S6 series). Each layer is drawn with its components, its interfaces, and its failure modes — the blueprint is honest about what can break (S7.4).
The blueprint as a sales artifact
The reference architecture is the sales artifact for every other service: the migration service (EX-8) uses it to map the client’s current stack against the target; the security review (EX-7) uses it to scope the audit surface; the white-label publishing (EX-6) uses it to explain where the client’s content lives in the system. The blueprint makes the stack legible to a client before they buy — and legibility is what turns a pitch into a decision.
The blueprint as a product line
The reference architecture is itself versioned: each round of the stack updates the blueprint, and clients who bought an earlier version get the update (the same lifecycle as skills, S4.9). The blueprint is the stack-as-a-service in document form — the knowledge product (EX-14) at the highest level of abstraction. A client who holds the blueprint can audit the stack, extend it, and own it — which is the sovereignty the whole business model promises.
Grounded in the EX worked-example series, the BR.11 stack-to-architecture bridge, the S1/S3/S4/S7/S9/S6 series, and the S7.4 threat-model article. Eleventh article in the Round D examples track.
