← Work
Interaction DesignAgentic Systems

Triage

A command center that collapses operational noise into confident next actions.

Triage sits on top of existing operational infrastructure — alerts, task managers, communication tools — and normalizes their feeds into a single interface. Each channel is assigned a specialized agent tuned for that domain. Opening an item doesn't show raw data. It shows a recommendation.

The shortest path from need to completion

Interfaces fail not because they lack features but because they add steps between intent and outcome. Every confirmation dialog, every mode switch, every context lost accumulates into abandonment or error. Triage treats the elimination of that friction as the primary design constraint — not aesthetics, not feature parity.

Interaction Model

Each item moves through a defined state sequence. The content area transforms at each stage — not a static detail pane, but a live workspace that changes character based on where the user is in the flow.

01

Alert

Item surfaces from the channel feed. Agent has already assessed context and severity.

02

Explain

Agent presents a plain-language summary: what happened, likely cause, recommended action.

03

Offer

Two exits: fix with AI or fix it yourself. Both actions keep the lightweight interaction intact.

04

Act

If AI is chosen, the agent executes. A live log surfaces what's happening in real time.

05

Verify

Agent reports what was done — tersely, in a code-style log, not a paragraph. Sign-off is the natural endpoint.

06

Sign Off

User confirms. The item closes. The channel badge updates. The loop is complete.

Design Decisions

Graduated autonomy. The user controls how much they delegate at every step. AI acts only when explicitly chosen. This preserves trust and keeps sign-off meaningful.

Terse verification. The Check Work state deliberately avoids over-explanation. A long explanation erodes trust — if it takes 400 words to describe what the agent did, sign-off becomes rubber-stamping. The log is a receipt, not a defense.

Specialized agents per channel. A generic assistant that handles everything develops mediocre-to-everything. Domain-specific agents develop fluency — they know what "resolved" looks like for alerts versus tasks versus messages.

Non-disruptive deployment. Triage normalizes existing feeds. It does not replace alert systems, task managers, or communication tools. It sits on top of whatever infrastructure is already in place.

Relationship to GDL

Triage applies the same decision architecture as GDL — translating ambiguous inputs into a single confident recommendation — at the operational surface rather than the product catalog surface. GDL handles "what should I buy?" Triage handles "what should I do next?" Same engine, different domain.