DIRA▮

When one thing moves, Dira fixes everything it breaks.

A professor moves your midterm two days earlier. Suddenly your interview is too close, your study time is gone, and a teammate is waiting on work you can’t do. Dira notices, finds every promise the change breaks, and repairs your week within limits you set. It tells the people affected before they have to ask.

Sign in with Google

The demo is a synthetic student week with a simulated calendar and mailbox. It needs no account and cannot contact real people.

Always watching the sources you choose

Gmail, Google Calendar and course deadline feeds, each connected with its own permission. Dira polls them in the background and keeps a commitment graph of what you promised, to whom, and what depends on what.

Nemotron proposes. Code decides.

NVIDIA Nemotron models on Nebius Token Factory read the change and propose repair plans. Deterministic code checks every plan for feasibility, provenance and policy, and you approve anything sensitive. No model output can authorize an action.

Your corrections become your rules

Reject or edit a step and Dira suggests a rule. Confirm it and it is committed to a private Git repository you can export, and mirrored as a read-only Skill for your Hermes assistant.

What the model may and may not do

Nemotron proposes

  • Commitment drafts from your calendar, email and feeds (Nano)
  • How an email changes an existing commitment (Super)
  • Typed links between commitments and repair plans (Ultra)

Deterministic code decides

  • Whether a plan is feasible and leaves enough slack
  • Whether every action cites a stored fact, and who may be contacted
  • What runs, what waits for you, and whether each change really happened

You stay in charge

  • Drafts only until you allow sending
  • Fence a calendar, your inbox, or a contact
  • Export or delete everything at any time

Engine proofs, including the deterministic replay, the 20-run reliability check and the variation matrix, are on the Evidence page.