Everything on the record

An agent working your inbox in the background could be a black box you're asked to trust. Dustav's answer is to leave a visible record of everything it does — not a marketing claim of transparency, but literal surfaces you can open.

Every read leaves a trace

Each email's card carries "What Dustav did" — the step-by-step of that read: what it looked at, what it concluded, and a chip for every action that came out of it (the to-do created, the row collected, the date staged, the file filed, the folder suggested). The trace is stored with the email permanently, and during a live sync you can watch it stream. When a row looks wrong, the trace is where you find out why — and the fix is a conversation, with the correction happening by re-reading the source, on the record too.

Every action lands somewhere you can open

Nothing Dustav produces is loose. A to-do links to its email; a workflow row links to the message it came from; a filed document opens its source; a staged date shows the mail that implied it. Follow any artifact backwards and you reach the evidence. The surfaces aren't a report about the work — they are the work, inspectable.

Every model call has a price tag

Usage & cost prices everything to the cent — each email read, each reply drafted, each chat turn, individually. The headline total and the detailed chart are computed from the same underlying records, so they can't drift apart: what you're told equals what you can audit. On a metered product this isn't a courtesy, it's the bill — and you can check it.

And when something goes wrong, it says so

The failure cases are on the record too. A workflow that matched but couldn't collect shows an honest failure chip — never a silent "nothing to collect." A read that failed says it failed and offers a retry. Something Dustav hit and couldn't finish lights the bell. The commitment isn't that nothing ever goes wrong; it's that you'll never be the last to know.