<!-- Envolt Mail · https://envoltmail.com/docs/console · Markdown version of this page for AI agents. Status: in development (https://envoltmail.com/status). -->

[Docs](https://envoltmail.com/docs) / The console

# Using the console

The console is where the accountable person works. It runs in our staging environment today, for our own team only. [Running in staging]

The console shows counts and decisions, never the text of a message. It can't show what it was never given.

## Signing in

You sign in with a passkey. The first passkey needs a single-use enrollment code; after that, adding another device needs both a new code and your existing passkey. A session lasts twelve hours.

Anything that makes the system less safe asks for your passkey again if it was last checked more than five minutes ago. Anything that makes it safer never does.

## The setup checklist

Until setup is finished, the console opens with four steps and says which are done: a passkey enrolled, a mailbox connected read-only, the pilot armed, and the 90-day clock running. The [getting started guide](https://envoltmail.com/start) explains each one.

## The 90-day clock

The clock counts days since the first completed pass over real mail. It also shows how many days had a completed pass and the longest gap between passes, so a pause is visible and can't be mistaken for progress. [Where it stands](https://envoltmail.com/proof#clock).

## Today

How many messages were read in the last 24 hours, how many were flagged for a closer look, and how many of each kind arrived. Below that is the latest morning brief.

## Label review, message by message

For one day the pilot keeps the minute each message arrived and the label the reader gave it. It keeps no sender, no subject and no text. The console lists those rows; you find a message in your own inbox by its time, then save the label as it is to confirm it or choose the right one. Your verdict is kept beside the reader's label, which is never overwritten. You can change a verdict while its row is there. Rows are removed after a day, or at once if you stop the pilot; your verdicts are kept. A message the reader could not label is listed as such and is not counted as any kind.

This is how a mistake by the reader is caught one message at a time, and how a change to the reader shows up as better or worse labels.

## The daily label check

Once a day the console asks whether the day's totals match the mail you remember receiving. You answer yes or no, and can name the label that looked wrong. One answer is kept per day. It records your verdict and the label, and nothing you type.

Together with the message-by-message review, these answers are the first evidence about the reader that comes from real mail. Later, earned autonomy is judged on them.

## The shadow pilot

- **Arm** starts reading for a fixed period. It asks for your passkey.
- **Mark the weekly review done** keeps the pilot running for another week. If a review is overdue, reading pauses until you do it.
- **Stop reading now** ends the pilot at once. It needs only your session.

The pilot shows what the reader has cost this month against its cap. At the cap the reader stops and mail waits.

## The kill switch [Running in staging]

Halting cancels every outstanding permission to send, for every agent, at once. It needs only your session, so it works even when your passkey was checked hours ago. Releasing a halt is a recorded decision and asks for your passkey again.

## When something is refused

The console says what happened in a sentence and changes nothing. If it asks for your passkey, the action continues by itself once you've confirmed. If the page can't reach the service, it says so and never reports an action as done.

See the decision cards and the morning brief on made-up data in the [console tour](https://envoltmail.com/tour).
