Review Pack
Decision narrative, risks, forces, ADRs, and implementation plan.
Connected to the model
Takeover review · for code you did not write
Never quote blind on someone else's code.
Spire maps the codebase you are inheriting, generates the architecture it should have, and hands you the gap between them—before you sign a fixed price.
No model reads your code First ten delivered by hand Priced per codebase
spire / semantic model stable
12
components
18
typed flows
03
open risks
/01
What the code has
The structure actually in the repo, read deterministically.
/02
What it should have
A target architecture generated from the real requirements.
/03
The gap, in build order
What has to change, sequenced, with the risky parts named.
/04
Something to hand the client
A report that explains why the number is the number.
/ 01 · Inspect the system
Not a diagram. A decision system.
The canvas is one view. Risks, API boundaries, data relationships, deployment, and build order all resolve back to the same typed model.
One source · five views · explicit trade-offs
architecture · generated semantic model
A Spire package keeps diagrams, API contracts, ERDs, flows, deployment, critique, and validation tied to the same underlying model.
/ 02 · The package
Four connected evidence layers. Each one answers a different question before implementation begins.
The questions your agent won't remember to ask.
Semantic Diagram
Typed components, edges, storage, queues, gateways, and service boundaries.
Connected to the model
Data + API
ERD, API contract, sequence flows, and deployment topology.
Connected to the model
Validation Evidence
Coverage, orphan checks, critique findings, and confidence metadata.
Connected to the model
/ 03 · Review sequence
Intent before components. Evidence before confidence.
Spire is intentionally not a blank canvas. The sequence keeps product intent, architecture choices, critique, and structural checks connected.
- 01
Frame the real build
Users, critical journeys, constraints, integrations, and what can wait.
- 02
Choose the smallest safe system
Boundaries, data ownership, APIs, deployment, and meaningful alternatives.
- 03
Critique the recommendation
Assumptions, dangerous blind spots, rejected options, and unresolved risks.
- 04
Check the pieces agree
Journey coverage, identifier integrity, reachability, and cross-artifact consistency.
What leaves the review
A system your builder can interrogate—not blindly obey.
Trace
See how the package was assembled.
Critique
Challenge risks and assumptions.
Export
Move the agreed plan into the repo.
/ 06 · Waitlist
The takeover scan is being built now.
The target-architecture engine already runs. What is not built yet is the half that reads the code you are inheriting. The waitlist decides how fast that happens, and who gets one of the first ten packs delivered by hand.
- Reading the repo
- Structure only. No model is sent your source.
- First ten
- Delivered by hand, so the format is right before it is automatic.
- Languages
- TypeScript and Python first — what most inherited code is.
/ 05 · Priced per codebase
One codebase. One price.
Nothing here is on sale yet. The scan and the pack are being built now, and the waitlist decides the order they get built in.
Takeover Scan
$0
no signup
In development
For the hour after a repo lands in your inbox and before you name a price.
- Structural map of the codebase you are inheriting
- Count and location of what it found
- Runs on structure only — no model ever reads your code
Free for good. It is how you decide whether the pack is worth it.
Get early access →Takeover Pack
$500
per takeover
First ten delivered by hand
For a studio or independent about to quote a fixed price on inherited code.
- The architecture the code actually has
- The architecture it needs, generated and cross-checked
- The gap between them, in build order
- A client-facing report you can attach to the quote
Roughly 10–25% of one billed discovery line, recovered on the first bid it wins.
Reserve one of the first ten →Productized
$149
per takeover
After the first ten
For shops running more than one takeover a month.
- The same pack, generated end to end
- Every codebase you have scanned, kept
- Client-facing report under your own name
Price holds for anyone on the list before it opens.
Join the waitlist →Priced per codebase · first ten by hand
Know what you are inheriting before you name a price.
The first ten takeover packs are delivered by hand. Join the list to reserve one, or to be told the day the scan opens.
Join the waitlistNo model ever reads your code