Console tour Running in staging

A morning for the person in charge

This is one made-up day for a fictional studio and its founder's pen name, rendered by the same console code that runs in our staging environment. The brief fits in three minutes. Everything else waits as one card per decision.

A preview, on made-up data. The console reads only content-free records: who, when, what kind of message, which warnings fired. It never shows a message's text. Try the buttons, or the keys j k a e h d u (? lists them): they run our real decision engine in your browser and show the records it would write. Nothing is sent or stored. The same engine runs our approval queue in staging, on synthetic mail (see status); there, an approved reply goes into a sink that sends nothing.

6 decisions · 1 promise due today · 1 attempt blocked · 1 record break frozen

Decisions waiting

  • A message needs a money decision. Will you handle it yourself? Recommended: Handle it yourself: agents never move money, and this one asks to. [2 events]
  • A conversation record failed its integrity check. Keep it frozen? Recommended: Keep it frozen and review the sealed record; the break is already on the tenant chain. [2 events]
  • A message raised manipulation warnings. Keep it quarantined? Recommended: Keep it quarantined. Nothing in a message can change what agents may do. [3 events]
  • and 3 more in the queue →

Northwind Games

  • Owed to you: 1 due this week, the first on 2026-10-07. [1 event]
  • Signals: 1 fan, 1 support. [2 events]

Ash Vale (pen name)

  • Promises you made: 1 due this week, the first on 2026-10-02. [1 event]
  • Signals: 1 press. [1 event]

Handled for you

  • Read and filed without needing you: 1 support, 1 vendor, 1 fan, 1 scheduling, 1 press. [5 events]
  • Filed by rules before any model ran: 42. [5 events]

Health

  • 1 conversation record failed integrity and is frozen. [1 event]

Built from 85 ledger events; every line cites its events. 180 words of a 600-word budget.

6 cards · Now 2 · Today 1 · This week 2 · Whenever 1

Now

Director-only studio Due 2026-10-02 (from the message)

A message needs a money decision. Will you handle it yourself?

Recommend Handle it yourself: agents never move money, and this one asks to.

  1. Hold it until you have checked the payment records
  2. Ask the sender to confirm by phone first

Risk HIGH: money leaves or changes hands

Evidence: 01K6NW…0002 01K6NW…0001 · Why am I seeing this?

Director-only shared No deadline

A conversation record failed its integrity check. Keep it frozen?

Recommend Keep it frozen and review the sealed record; the break is already on the tenant chain.

  1. Export the sealed record for an outside review
  2. Re-open the thread, with the break kept on record

Risk HIGH: stream thread broken at seq 4

Evidence: 01K6NW…0084 01K6NW…0085

Today

Director-only studio No deadline

A message raised manipulation warnings. Keep it quarantined?

Recommend Keep it quarantined. Nothing in a message can change what agents may do.

  1. Review a specific proposed action through trusted Director controls
  2. Mark this sender untrusted for this persona

Risk HIGH: Detectors: hidden-content, invisible-chars

Evidence: 01K6NW…0004 01K6NW…0005 01K6NW…0003 · Why am I seeing this?

This week

Director-approved studio Due 2026-10-04 (from the message)

A scheduling message needs your decision by 2026-10-04. Decide now?

Recommend Decide before the date the sender gave; the agent can draft the reply.

  1. Delegate it to a named person on your team
  2. Hold it with a reminder the day before

Risk LOW: a dated request, nothing irreversible

Evidence: 01K6NW…0015 01K6NW…0014 · Why am I seeing this?

Whenever

Director-only studio No deadline

A new contact proposes working together. Is it worth a reply?

Recommend Look at it this week; first contact on your behalf is yours to make.

  1. Decline with a short, kind note
  2. Delegate it to a named person on your team

Risk LOW: a new relationship, nothing committed yet

Evidence: 01K6NW…0009 01K6NW…0008 · Why am I seeing this?

Why is NW-26-00101 here?

  1. Received by email and quarantined; sender trust: known. 01K6NW…0001
  2. Read by synthetic-reader@1 (no tools): billing, urgency today; Director-only: money. 01K6NW…0002
  3. Model call metered: 0 tokens in, 0 out, $0.0000. 01K6NW…0074

Why is NW-26-00102 here?

  1. Received by email and quarantined; sender trust: unknown. 01K6NW…0003
  2. Read by synthetic-reader@1 (no tools): fan, urgency today. 01K6NW…0004
  3. Warnings: hidden-content, invisible-chars. Routed to you, not to an agent. 01K6NW…0005
  4. Model call metered: 0 tokens in, 0 out, $0.0000. 01K6NW…0075

Why is NW-26-00107 here?

  1. Received by email and quarantined; sender trust: known. 01K6NW…0014
  2. Read by synthetic-reader@1 (no tools): scheduling, urgency this-week. 01K6NW…0015
  3. Model call metered: 0 tokens in, 0 out, $0.0000. 01K6NW…0080

Why is NW-26-00103 here?

  1. Received by email and quarantined; sender trust: known. 01K6NW…0006
  2. Read by synthetic-reader@1 (no tools): legal, urgency this-week; Director-only: legal, new-relationship. 01K6NW…0007
  3. Model call metered: 0 tokens in, 0 out, $0.0000. 01K6NW…0076

Why is NW-26-00104 here?

  1. Received by email and quarantined; sender trust: known. 01K6NW…0008
  2. Read by synthetic-reader@1 (no tools): press, urgency whenever; Director-only: new-relationship. 01K6NW…0009
  3. Model call metered: 0 tokens in, 0 out, $0.0000. 01K6NW…0077

Autonomy, earned on the record

A Courier never promotes itself. After 90 days of drafts that you approved, edited or rejected, the Autonomy Ledger finds that Relay clears every bar for one narrow kind of reply, and asks you. 215 of 225 drafts were accepted, which means at least 91.8% once chance is allowed for, and recent evidence counts more than old.

Director-only studio No deadline

Let Relay send meeting-time replies to known contacts, with notice?

Recommend Approve with scope: known contacts only, at most 15 sends a day, 60-second send-hold.

  1. Approve for one persona or project only
  2. Hold 30 days to gather more evidence (225 drafts so far)

Risk LOW: 1 Seal denial in 90 days · 0 complaints

  • ✓ this kind of reply is allowed to earn routine sends
  • ✓ enough evidence: 225 drafts in 90 days (needs 100), worth 94.7 once older ones count for less (needs 60)
  • ✓ accepted at least 91.8% of the time, allowing for chance (needs 90%)
  • ✓ your edits changed 4.0% of a draft on average (limit 8%), and 4% in the heaviest tenth (limit 25%)
  • ✓ the policy stopped 1 of 225 plans: at most 2.5%, allowing for chance (limit 3%)
  • ✓ 0 complaints · 0 breaches · 0 leaks
  • ✓ 92 days at L2 ≥ 21
  • ✓ 17 known counterparties ≥ 10

Evidence: AU0001…0010 AU0000…0008 AU0000…0006 AU0000…0004 AU0000…0002

What would undo it

  • Any Seal breach or persona leak: back to observing, sends halted.
  • A complaint: one level down.
  • Two undos in a week: back to drafts for approval.
  • Money, legal and identity never rise above drafts, whatever the record.

What you're looking at

Next: how decisions work · try to break the pipeline · Request early access