High entropy asks: each names its decision, options and default; the few that matter first; noise shown as a number on the board #689

Pillar: P1 Feed (umbrella #587); renders inside #634's pinned "needs you". One run, after the expiry and collapse issue lands.

Why. Owner, 2026-10-05: "Do these really need my attention? This should be high entropy." Every row shown to him should carry information and need him; today the rows are the same sentence ("is green, waiting for your look") sixteen times, unranked.

The job: see the few decisions that matter most first, and see whether asks are worth raising at all.

Acceptance.

• [ ] An ask earns its place. Each ask names the decision, the options, and what happens if nobody acts (for example "Ship, or say what is off. If nobody acts: it waits; nothing ships"). An ask the crew or the planner can decide within the repository's limits is not raised for a person: it is decided, and the decision lands in the ledger.
• [ ] Ranked by consequence. Default view: at most five rows, ordered by consequence (security and money first, then what blocks other work, then age), with "N more" one tap away. The rule is one function with a test, not ordering scattered across renderers.
• [ ] Noise is a number. The board shows, for the last 7 days: asks raised, acted on (shipped, told, closed), dismissed, and expired by themselves. A high dismissed share is visible as a figure, not a feeling.
• [ ] Adding says what it removes: the per-row repeated sentence goes; the pull title and one clause stay.
• [ ] Reachable: the page, GET /api/v1/feed carries the decision, options, default-if-nothing and rank; the MCP reads the same; tests; looks at phone and desktop widths.

Start from: src/web/studio/asks.ts, src/feed/rank.ts, src/web/pages/board.ts, src/core/decisions.ts.

Must not touch: the release workflow, the chart, other repositories.