Durante OS / The Algorithm
One unit of work, watched end-to-end.
Seven phases. Six gates. Every transition leaves a receipt. Below is the canonical playthrough — a real work order, run through every stage. Click any phase in the rail to skip in.
Surface the signal the room is missing.
The operator's first job isn't to do — it's to notice. Sweep inboxes, tickets, ledgers, CRM. Cluster, score, name what matters before anyone reaches for a tool.
↳ Operator moves
- 01Cluster raw signals across systems by likely situation
- 02Score each with a hypothesis + confidence (0–1)
- 03Surface only the few that change what should happen next
Mixed signal across systems
- QuickBooks A/R aging report
- 34 unread emails — 6 vendor threads
- Slack #ops · 2 escalations
- Calendar — board call Thu 14:00
Acme A/R · 41 days overdue
$12,400 outstanding. Repeat customer, FY24 ARR $89k. Last touch 14 days ago — unanswered. Risk: board call references receivables.
Reason before reaching for a tool.
Multi-LLM debate. The signal is interrogated from three angles. Output: a hypothesis with stakes — not a checklist.
↳ Operator moves
- 01Three models debate the same signal independently
- 02Surface dissent, not just the median
- 03Output a hypothesis with confidence and risk vector
Acme · $12,400 · 41d overdue
Inherited from Observe. Context loaded: last 6 invoices paid on-day-32 avg, two prior late episodes (Q1, Q3).
"ERP migration broke their A/P workflow"
Confidence 0.78. Stakes: relationship intact, just stuck. Recovery path: re-establish A/P contact, accept ACH retransmission.
Pick the smallest reversible next move.
Plans are written as the receipts that will exist once the work is done. If a step can't produce a receipt, it isn't in the plan.
↳ Operator moves
- 01Sequence the receipts that will prove the work landed
- 02Mark reversibility per step — operator can revoke
- 03Approval window 4 min · auto-flips to escalated past
ERP migration broke A/P
Plus context: contact graph, prior communication tone, payment terms (NET-30), relationship value.
Approve · revise · reject
Plan surfaces to operator-of-record in 30s. Default approval window: 4 min. Auto-revisable up to step 03; step 04 requires re-plan.
Compose the artifact before sending it.
Build is where artifacts are constructed in a sandbox — drafts, regenerated invoices, calendar holds, briefs. Nothing leaves the system here.
↳ Operator moves
- 01Compose voice-matched email · attachments · cal block
- 02Version-pin every artifact in the sandbox
- 03Open the review pane for operator approval
4-step recovery plan
Approved at 08:36. Build pulls: brand voice file, invoice template, ACH instructions, Sarah Cho’s contact history.
Sandboxed · review pane
All three artifacts open in a single review pane. Tone, attachments, recipients, send time — adjustable. Nothing has touched the outside world yet.
Send. Log. Own it.
The only phase that touches the outside world. Every side-effect is bracketed by a pre-flight and a post-flight receipt — even when it fails.
↳ Operator moves
- 01Pre-flight check (SPF · DKIM · attachment hash)
- 02Side-effect (SMTP · calendar · file · API)
- 03Post-flight reconciliation written to chain
3 artifacts · operator-approved
Final approval at 08:43. Send-window opens. Pre-flight: SPF/DKIM check, attachment hash, contact verification.
The world has changed
Email delivered. Invoice received. Hold on calendar. The system now waits — but it isn’t idle. Verify is already watching for the reply.
Match outcome to hypothesis.
The conscience of the system. If the world responded differently than predicted, the delta surfaces — and we re-enter Think.
↳ Operator moves
- 01Watch the world for the expected response
- 02Reconcile against the original hypothesis
- 03Surface deltas — never silent on a miss
Reply from Sarah Cho · 09:47
“You’re right — we cut over ERPs and the old A/P queue dropped. ACH sent. Thanks for the nudge — appreciate the heads-up.”
Win · faster than expected
$12,400 cleared at 11:02. Board call asset updated. Confidence on similar future cases bumped 0.78 → 0.84.
Codify what the run taught the system.
Learn writes back. Doctrine updates. A new pattern is named. Future runs on the same shape now start with a pre-loaded hypothesis.
↳ Operator moves
- 01Name the pattern · co-sign with operator-of-record
- 02Update thresholds (0.60 → 0.55 on this shape)
- 03Seed an auto-playbook for future runs
Run 0241 · clean win
22h faster than predicted. Hypothesis correct. Tone-positive close. No human friction.
v0.0.8 → v0.0.9
The next Acme-shaped signal hits Observe with a pre-loaded hypothesis. Plan generates from the saved template. The cycle is now 40% faster on the same shape.
Run 0241 · full playthrough
SHA · 0241ff · 06.12 · 08:14 — 11:08 · 2h 54mClaude Code writes the code. Durante owns what ships.
Want to see this run on one of your situations? Bring a stuck workflow — we'll trace it through the algorithm in a 30-minute office hours.