DIRA▮

Repairs you can inspect, without an account

The live product is the Try and Today pages. This page keeps the reproducible engine proofs that carried over from Dira v1: the 48-Hour Shock replay, its ledger, the variation matrix, and the reliability runs. They use stored interpretations and stateful simulators, and are labeled that way. Run them yourself with make demo-replay and make replay-20x.

What actually ran

These are recorded checks, with their original revisions and boundaries. The public replay below runs without credits or OAuth.

Real Nemotron inference

8/8 interpretation cases; 7/7 repair scenarios resolved

Live Nebius Token Factory calls; simulated external tools. Ultra produced 11 bounded proposals, 3 passed all gates, and won 2 of 7 scenarios. All eleven calls completed without truncation.

Inspect dated evidence →

Actual Google Calendar

Source change → review → approval → VERIFIED move

Synthetic events on an owner-selected test calendar. Separate provider GET confirmed the move; fixtures later deleted. Recorded backend revision 00012-h5k, before the October 18 concurrency hardening.

Inspect dated evidence →

Actual Gmail drafts

Fresh draft and interrupted-write recovery independently verified

Operator-provisioned synthetic plans addressed to the owner. Draft creation and recovery verified through fresh provider reads. Recovery reused the existing draft. Recorded backend revision 00013-j4w.

Inspect dated evidence →

Private recovery and sandbox

Database/private Git restore and separate Linux enforcement checks

Private Git recovery plus isolated Linux OpenShell checks. The hosted Cloud Run broker uses the application egress allowlist; the optional Hermes companion is configured separately.

Inspect dated evidence →
Where did Ultra add value?

In the overlapping-block case, the deterministic enumerator found no feasible candidate; Ultra proposed the accepted plan. In a second case it won on disruption cost. Across the full seven-case run it won twice; deterministic candidates won five times. Rejections were retained rather than executed.

Read all seven cases and token counts

Explore the model traces, approved Google Calendar repair, Gmail draft recovery and private-memory checks above. The public demo uses synthetic integrations; real-account connectors and the optional Hermes companion follow owner enrollment.

Recovered rule check · policy verdict only →

Open the interactive demo

One moved commitment can break the whole week.

A midterm moves from Friday to Wednesday. The interview buffer disappears, study capacity no longer fits, and a team deliverable is suddenly at risk. Calendars show that conflict. Dira repairs it.

This reference uses its original autonomous fixture policy. The v2 demo pauses for authenticated approval before delegation. Dira only takes actions permitted by the people and policies in the plan, then verifies the changed world before calling the repair complete.

External changeMidterm: Fri 2 PM → Wed 2 PM
What breaksInterview buffer · study capacity · team QAGLOBAL SLACK +4.1h → −3.6h
Dira's verified repairReplan, rebook, delegate, rebuildV1 REPLAY · +1.3h · 0 INTERVENTIONS
+4h0h-4h+4.1hbefore trigger-3.6hafter mutation+1.3hafter repair
Commitments
10
At risk
0
Interventions (resolved)
1
Global slack
+1.3h
ECON 402 — the 48-Hour ShockRESOLVED
Commitments affected
6
Verified adapter mutations
13
Failures recovered
1
User interventions
0

A professor email moved the midterm forward 48 hours. Dira re-derived the plan: rebooked the interview (surviving a 409 on the first slot), delegated sponsor-deck QA to the backup owner, reclaimed two personal blocks, and rebuilt the study plan — all policy-gated, ledgered, and independently verified. Open the flight recorder →

Runtime note: this overview is the reproducible deterministic reference. It uses stored interpretations and stateful integration simulators, never live services. Reproduce it with make demo-replay.