How it works
Connect · Form · Find · Fix · Prove.
From the records your company already keeps to an outcome verified by a named person. Nothing advances because a screen was opened.
AI
AI reads your records. People make the decisions.
Scale
Build the operating system once. We keep it running.
Entity one and entity forty get the same reading. You retain authority at every step.
Operations
What we run each week
Each week we update one record of what was decided, what is out of bounds, what is ready, what was certified, what was approved and what was released.
The living picture
The picture your records already hold.
Every part comes from a record. Every handoff ends in a person’s call.
Step by step
The method and the software, together.
The method and the software do different work. Both begin with the same evidence.
- 01
Connect
Hand us what the company already produces.
- What you bring
- Map sources, owners, current reports and pain points.
- What we do
- We register what each source can and cannot establish, then read what is held.
- What you get
- A source map and work inventory.
- 02
Form
We rebuild the company as it actually works.
- What you bring
- Confirm the picture with leadership, in your own words.
- What we do
- We form the story from business sources and surface conflicts as questions.
- What you get
- The story so far, with unknowns named.
- 03
Find
We say what is holding the result back.
- What you bring
- Confirm what success means for each part of the business.
- What we do
- We compute what is holding you back and match what we'd change.
- What you get
- The Reading.
- 04
Fix
We say what we'd change, and you approve it.
- What you bring
- Design the change, name its owner, preview it and name who approves.
- What we do
- We put owners, actions, gates and the measure on the record, then run the weekly loop.
- What you get
- An installed change and This week.
- 05
Prove
We show whether it worked.
- What you bring
- Tie the change to cash, risk, speed, revenue or value.
- What we do
- We verify completion through someone other than the doer and show baseline, change and kept.
- What you get
- Did it work, on the record.
Operations
Every week after
Each week we update one record of what was decided, what is out of bounds, what is ready, what was certified, what was approved and what was released.
- 01Sources readYou set the boundary.
- 02Registers updatedYou correct the record.
- 03This weekYou see what moved.
- 04Your callYou decide.
- 05The workYou approve the owner.
- 06KeptYou verify the result.
- 07Release recordThe record stays yours.
Before the first read
What it asks of you
- Start
- One consequential question and the records already used to run that part of the company.
- People
- An operating lead, the owners of the source records and the person with authority to decide.
- Conflict
- When sources disagree, both remain visible until a named person settles what is true.
- Burden
- You choose the boundary, correct the reading and make the call. We assemble the evidence.
Where the method comes from
The questions are fifty years old. The evidence is new.
Find · Fix · Prove runs the focusing steps Eliyahu Goldratt set out in the Theory of Constraints: find the constraint, subordinate everything else to it, act, then look again. Consultants work these steps in workshops, from memory and interviews.
Here, every step must carry its records. A constraint is a count of what the record holds. A conflict is two sources, quoted. A change appears only when its trigger fired and its evidence is held. Nothing advances on our say-so.
Method after Goldratt's Theory of Constraints. The evidence-binding is ours.
The landscape view is after Simon Wardley's mapping method (CC BY-SA) — drawn from your records, not a workshop whiteboard.
Evaporating Cloud
From contradiction to proof
The Cloud does not choose a side. It makes the assumptions visible, records a named ruling, and opens the governed path to a change and its result.
Open the decision instrumentYour Cloud is private. The link opens your company workspace after sign-in.
- 01
Contradiction
Two source readings remain visible.
- 02
Assumption
A named person states what each side depends on.
- 03
Ruling
Your call is recorded as your word.
- 04
Change
An evidence-matched change can be proposed for approval.
- 05
Proof
Completion and outcome require separate records and independent verification.
Plainly
What we read and what we never read
What builds the picture: your records, books and files — entities, plans, transactions, commitments, decisions, outcomes.
What only corroborates it: when things were sent and met, at team level. Never a body, a subject line or a document's contents.
No one is scored. Nothing renders on a person. Names carry accountability, never judgement.
Owners and approvers are named, because accountability needs names.
Team patterns are aggregated and never about a person.
Under the hoodOpen
The machinery underneath, named as the engineering names it. Nothing here changes what you are asked to do.
The syntax of work
Eight questions give the work a common shape.
- Segment
- What part of the business does this belong to?
- Thread
- What result is moving through the company?
- Action
- What needs to happen next?
- Step
- What has to happen in order?
- Evidence
- What shows this is true?
- Owner
- Who is accountable for the next move?
- Call
- What needs a named decision?
- Outcome
- What changed after the work was done?
The stack
- 01
Private Relay
Installation architecture · in developmentSafely observes permitted signals at the customer boundary.
ProducesPermitted, source-linked signals
More detailLess detail
The secure installation architecture and product direction: read-only observation scoped inside your boundary, with classification and redaction done locally. Not a deployed behind-the-firewall agent today.
- 02
Operating Graph
Turns evidence into a living model of work.
ProducesA model of interfaces, work, handoffs and outcomes
More detailLess detail
One canonical graph. Every surface projects the same objects, events and revision basis.
- 03
Narraitive Protocol
Governs evidence, authority, decisions and state transitions.
ProducesGoverned, append-only state
More detailLess detail
A reading becomes consequential only here: named authority, bound basis, append-only events.
- 04
The Reading
Shows flow, friction and gaps.
ProducesA diagnosis a leader can act on
More detailLess detail
Five views of one company, bounded by the evidence actually held.
- 05
Action & Completion Ledger
Connects decision, authorized work, completion evidence and outcome.
ProducesA verified chain of consequence
More detailLess detail
No stage advances from opening a screen or from unsupported text.
- 06
Change Movie
Shows how the operating system changed and what caused it.
ProducesAn auditable history of the model
More detailLess detail
Scrub backward to see what changed, who was authorized and what the evidence was.
The next call