smalltalk pre-release

Attention

Attention is one inbox per person, holding everything that needs them right now. It's how smalltalk turns a busy fleet of agents into the short list of things that need a human.

st attention ls --as person/ada

What shows up#

• Human gates waiting on your review.
• Launch approvals for missions a planner drafted.
• Revision approvals for changes to running missions you protect.
• Unread messages addressed to you.
• Fault requests raised explicitly for a person, such as a seat that keeps failing to start.

Each item says what it's about, how old it is and where it sits in the graph, and gives the exact commands to act on it. --json returns the same items as structured data for apps.

What doesn't#

The runtime doesn't turn every diagnostic into work for a human. Faults are recorded on the subject they affect, and show up in the status views. Only an explicit request puts something in someone's attention.

Items leave on their own when they're resolved: a decided gate, an approved launch, a read message. Requests that no longer apply, like a gate from a superseded generation, don't linger either.

Signal over noise#

Attention exists so that nothing depends on someone happening to read a message. A step that needs a person is a human gate, and the graph tracks it until it's decided. You don't watch agents to find out whether they need you. You check one list.

Attention is always for a named person, from --as or the person in your st config. It's never guessed from the environment.