Centaur · Decision operating system

The brief told you what to do.
Centaur tracks whether it worked.

Compass helps you localize the decision. Centaur holds the move against a precommitted threshold, so when the real signal arrives you can compare expected to actual instead of relying on memory, mood, or hindsight. Founder access begins after Compass, while the advisor workspace is still rolling out through a reviewed waitlist.

Run Compass first →See how Centaur worksStart with a brief · Import context directly

Active episode

In progress

Current intervention

Double down on the PLG motion — delay outbound

Testing hypothesis

If self-serve is the constraint, PLG removes it within 3 weeks

Success signal

Week 3: 4+ new orgs activate without sales touch

Review date

May 14, 2026

How it works

01

Arrive with your brief

Import directly from your Decision Brief link. The decision frame, readiness, and likely explanation are already loaded.

02

Set the threshold

Define the result that would strengthen or weaken the move. Set the date before the evidence arrives.

03

Close the loop

Compare expected to actual, record the learning, and let the next decision start from sharper context.

How you arrive

Compass tells Centaur what to track first.

The readiness verdict changes the job. Sometimes Centaur tracks a committed move. Sometimes it tracks the test you still need before the real decision is ready.

Verdict: Ready

Commit and track

You have enough to decide. Centaur records the chosen frame, the primary hypothesis, and the threshold date.

Typical: days to two weeks

Verdict: Not yet

Test and return

Run the discriminating test first. Centaur tracks what you ran, what came back, and whether the evidence was enough to upgrade the decision.

Typical: one to three weeks

What Centaur tracks

What stays visible between decisions.

Not a project manager. Not a CRM. Centaur keeps the expected signal, the actual result, and the learning in the same place so the case stays legible over time.

The decision you committed to

The exact frame you chose, linked back to the Decision Brief it came from.

The hypothesis you are testing

The explanation you are betting on, with the evidence that would strengthen or weaken it.

The threshold signal

The result that tells you whether the move worked, defined before action so it cannot drift later.

The learning

What is more true now than before. This keeps the next episode from starting blind.

Copilot

Ask the episode what still needs interpretation.

Copilot sits on top of the episode, not beside it. Use it to stress-test a hypothesis, interpret a borderline threshold result, or identify what evidence is still missing — grounded in the current case, not generic AI advice.

Episode · PLG motion — delay outbound
Am I reading the threshold signal correctly? I got 3 activations, not 4.
Three against a threshold of four is borderline. The key question is where the drop-off happened before you call it a demand failure.
The drop-off was at the billing screen.
That points to pricing friction, not clean demand failure. Your hypothesis is not disproven yet — it is still unresolved.

For advisors

Keep the case alive between sessions.

Episode history makes follow-up smarter. What the client committed to, what the signal was, and what actually happened all travel into the next session, so your advice compounds instead of restarting.

Advisor access is rolling out through a reviewed waitlist — we're notifying advisors as the workspace opens.

Your brief is the start, not the end.

Start with Compass to localize the decision. Use Centaur once the move needs follow-through, thresholds, and learning over time.