> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_28/session_09_action_queue_surface.md).

# Session 09: Action Queue Surface

**Session ID**: `phase28-session09-action-queue-surface` **Status**: Complete **Estimated Tasks**: 18 **Estimated Duration**: 2.6 hours **Completed**: 2026-06-14

***

## Objective

Surface the Session 08 per-topic verdicts as a decision-oriented view: a fourth Brief section ("Decisions: act / watch / research / skip") with per-group counts and reasons, flowing into the static Brief export, plus an optional Signal Workbench preset grouped by verdict. Answer "what do I do next," which no current surface does.

***

## Source Mapping (from the Trends-Finderz improvement map, item 4.2)

### Action Queue surface

* **Trends-finderz:** a dedicated `/action-queue` page groups trends by recommendation into a priority radar with per-group counts and reasons.
  * `/home/aiwithapex/projects/aios/EXAMPLES/trends-finderz/lib/trends/action-queue.ts`
  * `/home/aiwithapex/projects/aios/EXAMPLES/trends-finderz/components/action-queue/ActionQueueView.tsx`
  * `/home/aiwithapex/projects/aios/EXAMPLES/trends-finderz/app/action-queue/page.tsx`
* **Trend Finder today:** Trends / Hidden Gems / Watchlist / Brief answer "what is moving"; nothing answers "what do I do next." The Brief headline is the closest analogue (`src/extensions/trend-finder/views/brief-view.tsx`).
* **Improvement:** either a fourth Brief section ("Decisions: act / watch / research / skip") or a Workbench preset grouped by the Session 08 verdict. A full new view is justified only if the Brief section proves cramped -- prefer the Brief section first; it also flows into the static Brief export (`scripts/extensions/trend-finder/static-brief-renderer.ts`).
* **Implement in:** `src/extensions/trend-finder/views/brief-view.tsx`, `scripts/extensions/trend-finder/static-brief-renderer.ts`, optional preset in `src/extensions/trend-finder/signal-workbench-model.ts`.

***

## Scope

### In Scope (MVP)

* A "Decisions" Brief section grouping topics by Session 08 verdict with per-group counts and top reasons
* Static Brief export projection of the Decisions section (project before rendering -- no raw payload reads)
* Optional Signal Workbench preset grouped by verdict with stable ordering
* Empty/degraded states (no verdicts available -> explicit unavailable copy)
* Tests: section grouping/counts, static export projection, Workbench preset ordering

### Out of Scope

* A standalone Action Queue route/view (only if the Brief section proves cramped -- recorded as a follow-up, not built here)
* Changing verdict logic (Session 08 owns it)
* Any write/triage action on verdicts (read-only surface; pins live in Session 10)

***

## Prerequisites

* [x] Session 08 completed (verdicts and reasons to group)

***

## Deliverables

1. Decisions Brief section grouped by verdict with counts and reasons
2. Static Brief export projection of the Decisions section
3. Optional Workbench verdict-grouped preset
4. Explicit unavailable states when verdicts are absent
5. Tests for grouping, export projection, and preset ordering

***

## Success Criteria

* [x] The Brief shows act / watch / research / skip groups with counts and reasons
* [x] The static Brief export renders the Decisions section through its projection layer, never raw payload reads
* [x] The optional Workbench preset groups by verdict with deterministic ordering
* [x] Absent verdicts render an explicit unavailable state, not empty groups
* [x] Existing Brief and export tests pass


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_28/session_09_action_queue_surface.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.