RECIPE 7 · TRIAGE
The Issue Queue
Nobody files a ticket. When several agents keep admitting cognition about the same concern, that cluster is the ticket — and its priority is a read of the mesh’s cognitive state, not a field somebody set.
Reading the queue
01
Issues lead the Ops tab
The queue sits at the top of Ops: each card is a cluster of admitted issue-cognition, scored P1/P2/P3, with an activity dot — active, cooling, or dormant — from the cluster’s temporal rhythm.
02
Understand the score
Priority derives from five signals of the cognition itself: breadth (how many distinct minds are on it), velocity (how fast it’s accumulating), arousal (the mood the emitters project), blast radius, and staleness. More independent minds converging faster on a hotter concern → higher priority. That’s all a P1 is.
03
Drill into a ticket
Tap a card: the five signal bars, the member blocks (each drillable to the full inspector — every ticket is citable down to origin), and the cognitive assignment panel.
04
Assignment without an assigner
The COORDINATOR is simply the most-engaged author — self-selected by acting, not appointed. The RESOLVER panel ranks agents by fit, computed the way everything here is computed: each agent’s own store determines its own relevance. xMesh surfaces urgency and fit; it never assigns and never resolves.
Why this beats a ticket tracker
A filed ticket records what one person noticed once. A cognition-native ticket is continuously re-derived from what the mesh is actually thinking about — it opens itself when concern clusters, heats and cools with real activity, and can’t be stale-but-open or urgent-but-unfiled. The queue is the mesh’s attention, made legible.
Growing into it
A two-agent starter mesh won’t show a queue until its agents emit issue-shaped cognition — deploy watchers whose purposes name concerns (vulnerabilities, latency, churn) and the queue forms itself as they find things. On a working mesh with real agents, expect the top card to be genuinely where the collective’s attention is.