The cross-project glance: what the agent is working on right now, how much is queued, which projects and sessions were recently active, and which tickets are hot.

## TLDR

- Active sessions come from each project's live run records — every concurrent one — most recently updated first; recent sessions pool every project's history into one capped, newest-first rail.
- Hot tickets sort into three lanes with strict precedence: being worked on (a live session is implementing it — hard evidence — or it has a plan), sitting in the AI queue, or merely flagged high priority; everything else stays off the card, which is a shortlist, not the backlog.
- "High priority" follows the ticket format's 0-10 scale (7 and up) — reading it as the P-numbers convention once kept a whole urgent backlog off the card.
- The cross-project tickets page keeps one list per project, present even when empty, so importing stays reachable there.
- Forgiving throughout: an unreadable project contributes nothing.

## Before writing SPEC.md files

Read https://raw.githubusercontent.com/brillout/sdd/refs/heads/main/sdd.md
