Independent Systems Architect

When the same failure keeps returning, the problem is no longer execution. It is structure.

I write fixed-scope structural artifacts for founders, operators, and decision owners who need the architecture exposed or a recurring failure structurally diagnosed. Three paths from £2,000. Diagnosis first. Redesign only from a locked diagnostic frame. Start with contact or the five-line brief.

The same failure costs more the second time than the first. At some point the structure has to be named.

CONTACT SEND FIVE-LINE BRIEF
Jamie Forrester

Jamie Forrester

Independent Systems Architect

Edinburgh, Scotland

I study why complex systems fail, then diagnose, redesign and build better ones.

That work has produced a diagnostic taxonomy of 9 failure classes and 54 subtypes, a growing research programme, the Seeing Systems books, and a series of software ventures built from the same structural principles.

is this for you
This is for you if
  • The same failure keeps returning under different names
  • Internal fixes have not held — the correction loop is missing the real break
  • The team cannot agree on what is actually breaking
  • Builders are inventing design decisions during implementation
  • Workarounds have become part of the operating model
  • The visible symptom is downstream of a rule, boundary, or primitive mismatch
This is not for you if
  • You need code debugging or a technical audit
  • You need live incident response
  • You need implementation ownership or delivery
  • You need generic strategy advice
  • The failure is one-off or already diagnosed
  • The diagnosis is known and you only need delivery
the diagnostic system

Nine failure classes. 54 subtypes. Every recurring structural failure fits somewhere.

When you send the five-line brief, it is run against the Diagnostic Taxonomy — a classification system developed alongside 10 published papers and refined through three public proof sets. The taxonomy identifies which class of failure is producing the recurring break, and which subtype is the specific mechanism. That classification governs the engagement path, the diagnostic frame, and the correction sequence.

Systems do not fail randomly. They fail in recognisable structural patterns — across sectors, scales, and domains. The taxonomy makes that pattern visible before any diagnosis begins.

Class 1
External Constraint
Class 2
Scaling Failure
Class 3
Founding Model
Class 4
Boundary Failure
Class 5
Governance Failure
Class 6
Incentive Misalignment
Class 7
Human-System Interface
Class 8
Transition & Migration
Class 9
Governance Compression
core offerings

Three paths. Fixed scope. No hourly rates.

Start with a Structural Lens Brief when you need the architecture extracted. Use the Diagnostic Artifact when the failure must be named. Use Full Structural Engagement when the correction sequence must be specified.

01 // Structural Lens Brief
£2,000
Fixed fee · 7-day delivery

Extracts the structural architecture beneath one problem, system, method, or body of work. A 6–10 page written artifact naming the underlying architecture, principal functions, boundaries, dependencies, and structural tensions.

You know the domain. I name what it is actually built on.

Stops at architecture extraction — not a full failure diagnosis or redesign.

02 // Diagnostic Artifact
£10,000
Fixed fee · 14-day delivery
  • Primitive definition
  • Invariants and enforcement map
  • Governing diagnosis
  • Build map
  • Translation Artifact
  • Redesign Executive Summary
  • Target boundary redesign
  • Transition sequence
  • Builder handoff specification
03 // Full Structural Engagement
£25,000
Fixed fee · 14-day engagement · Four artifacts
  • Primitive definition
  • Invariants and enforcement map
  • Governing diagnosis
  • Build map
  • Translation Artifact
  • Redesign Executive Summary
  • Target boundary redesign
  • Transition sequence
  • Builder handoff specification

Commissioned separately, diagnosis and redesign total £35,000. As one governed sequence, £25,000. Full service details →

what the artifact does
Before the artifact
After the artifact
The failure is a moving target
Teams debate the root cause. Every cycle names it differently.
The failure is named once
The structural break is located precisely. Interpretation drift stops.
Builders invent structure midstream
Design decisions made during implementation. No written source exists.
Builders execute from a written source
The artifact becomes the design source. Midstream interpretation is removed.
Humans carry what the system leaks
Manual workarounds and shadow processes become load-bearing.
The system carries the function
The boundary is defined. The system enforces. Human workaround load drops.
Nobody owns the failing decision class
The failure crosses teams, systems, or authorities without a single correction owner.
Ownership becomes explicit
The decision class is located. The correction boundary is assigned.
public proof sets

Three systems. Same method. Public proof it repeats.

Outlier proof set
01 // Outlier AI
Recruited as an expertise market. Operated as a reliability pipeline. The worker becomes a node of hidden friction.
Public: Translation · Diagnostic · Redesign Summary
Restricted: Full Redesign Artifact
View proof set →
NHS proof set
02 // NHS Primary Care
Record-rich system. Continuity-poor reality. The patient becomes the carrier of memory.
Public: Translation · Diagnostic · Redesign Summary
Restricted: Full Redesign Artifact
View proof set →
Patreon proof set
03 // Patreon / Apple IAP
Patronage primitive cannot be expressed inside Apple's IAP grammar. Two mutually exclusive exits.
Public: Translation · Diagnostic · Redesign Summary
Restricted: Two Full Redesign Artifacts — Path A · Path B
View proof set →
VIEW ALL PROOF SETS →
diagnostic scan

Self-screen before sending a brief.

Four questions. Answer them honestly and you will know whether the failure is structural, and where to look first. Use this as a first-pass fit check before briefing.

// 60-Second Scan
RUN THE SCAN →
how to start

Send the repeated failure. Not the proposed fix.

The five-line brief. No diagnosis yet. Just the signal.

Step 01

Start with the right entry — contact me or request a Structural Lens for architecture extraction; send the five-line brief for a recurring failure.

Step 02

I review fit and confirm the right fixed scope. No one moves to redesign without diagnosis first.

Step 03

You receive the agreed artifact — Structural Lens Brief, Diagnostic Artifact, or the full four-artifact sequence.

Send these five lines
  1. 01What keeps going wrong?
  2. 02What is it costing? Money, time, trust, load, or drift.
  3. 03Where does it show up? Teams, roles, systems, or touchpoints.
  4. 04What has already been tried?
  5. 05What cannot change? Non-negotiables and constraints.

If the work is not the right fit, I will say so.

the research behind the practice
// Diagnostic Lens Trilogy 3 papers · one closed diagnostic loop

The clearest entry into the research: three papers that move from mismatch, to collapse, to the missing redesign layer.

Cover: The Expertise Illusion in AI Task Marketplaces Published paper 01

The Expertise Illusion in AI Task Marketplaces

Diagnostic instrument: Interface-legitimacy mismatch

How reliability pipelines borrow the language of expertise and create a structural mismatch between signalled capability and consumed capability.

View paper →
Cover: The Four-Function Law of Scalable Institutions Published paper 02

The Four-Function Law of Scalable Institutions

Diagnostic instrument: Four-Function Law — Sensing · Interpretation · Authority · Memory

Establishes what happens when sensing, interpretation, authority, and memory remain fused at the same human node under ambiguity and consequence.

View paper →
Cover: Why Systems Can't Fix Themselves: The Missing Redesign Layer Published paper 03

Why Systems Can't Fix Themselves: The Missing Redesign Layer

Diagnostic instrument: The redesign layer — the upstream layer absent by default in most self-correcting systems

Introduces the Redesign Law and correction collapse, showing why execution and diagnosis cannot reliably produce redesign from inside the same correction loops.

View paper →

Ten papers are published and free to read. The complete Diagnostic Taxonomy is available on request. Together they sit inside a 59-paper research programme that is already mapped.

VIEW THE TRILOGY → VIEW ALL RESEARCH →
the book sequence
Seeing Systems cover
At proof stage
Seeing Systems
Before you can think in systems, you have to be able to see them.
View book →
The 15-Level Abstraction Ladder cover
First draft complete
The 15-Level Abstraction Ladder
Most disagreement is not about facts. It is about altitude.
View book →
The System Founder Framework cover
In development
The System Founder Framework
How one person with the right structural grammar and AI capability can build operating-system-level companies.
View book →
VIEW ALL BOOKS →

For publishers and literary agents: proposals, sample chapters, manuscripts and sequence materials are available for serious enquiries.

PUBLISHING ENQUIRY →
start with the signal

Send the repeated failure. Not the proposed fix.

If you already know what keeps recurring, send the five-line brief. If you simply want to open a conversation first, contact me directly.

CONTACT SEND FIVE-LINE BRIEF

If the case is not structural, I will say so.

↑ BACK TO TOP