BLUEPRINT
Build it yourself·Or with help·Then qualify

Hints to help you on your way,
pinned in one place.

Four documents, one shape: an architecture, how it runs end to end, one way to actually build it, and a worked example so you can see the output before you write a line of it. A starting point, not a finished kit.

// The Board

One blueprint. Four documents pinned around it.

Not a finished kit — a starting architecture, structured enough that a coding agent can build from it. The centre sheet is the shape; the four papers are the detail.

The Independent Desk — Rev. 01
SCREEN RESEARCH REPORT INVESTMENT THESIS ADVERSARIAL REPORT EXECUTIVE REPORT
Independent Desk BlueprintConceptual · Not to Scale
Doc 01

Architecture Blueprint

The principles — TOGAF's four domains, the data model, and the no-synthesis rule everything else depends on.

View PDF ↓
Doc 02

Systems Design

The same system in motion — one full cycle traced end to end, and what happens when a stage fails.

View PDF ↓
Doc 03

Technical View

One example stack — components, sizing, and a cost model, so the shape and the weight are both visible.

View PDF ↓
Doc 04

Worked Example

One invented company, traced through every stage — so you can see the actual output before building anything.

View PDF ↓
// Legend

What each document actually covers.

The board carries the shape. This is the part a pinned note can't hold.

01 · ARCHITECTURE BLUEPRINT

What exists, and why

Structured on TOGAF's four architecture domains — vision, business process, data, application, and technology, in that order. States the one non-negotiable principle: every reasoning stage runs independently, with its own access to primary sources, never merging a prior stage's conclusion into its own. For anyone who wants to understand the design before touching a single component.

02 · SYSTEMS DESIGN

How it behaves, end to end

The same architecture traced in motion — a full flow diagram, one cycle narrated stage by stage, and what happens when something fails. Answers "what actually happens when I approve a company for coverage," not just "what components exist."

03 · TECHNICAL VIEW

One way to actually build it

A concrete, illustrative technology stack — deliberately ordinary and swappable — with component specs, data-volume sizing, and a cost model. Written so an operator can see the shape, the weight, and the running cost before committing to anything.

04 · WORKED EXAMPLE

What actually comes out the other end

One invented company, traced through every stage — Research Report, Investment Thesis, Adversarial Report, Executive Report — with real (fictional) figures at each step. Shows the no-synthesis principle in motion: the final stage doesn't simply agree with the thesis that came before it.

// Standard

The board gets you building. The Vault is where you're checked.

These four documents are a starting point, not a finished product — a shape worth building from, sized and costed honestly, with the one design principle that actually matters stated plainly rather than left to be discovered the hard way.

Building the desk is the first step, not the last one. What comes after is earning your way into a library of work built the same way — see the Vault for what that actually requires.

Build it, run it, then bring it. The desk proves itself before anything else does.