# Tasks, notes and scoped work

The native terminal's details rail includes **TASKS / NOTES**. It presents the active session's checklist as a hierarchy, public operational notes, and recorded runner activity. It remains available during transcript scrollback. When viewing an agent tab, the session label identifies which session owns the displayed checklist.

At narrow terminal widths, or with the right rail collapsed, a three-row task strip appears above the transcript. Current work appears first; pending work is dimmed. Completed items leave this compact strip and remain in the detailed hierarchy. Click a task to open its details. Tab moves between controls; Enter or Space expands disclosures, and Left/Right navigates the compact strip. Disclosure state and the input draft survive layout changes.

Todo items use square marks: □ pending, an animated shaded block for active work, ■ completed and ▣ blocked. Repeated progress meters use block fills; individual circular status icons are retained. `OMNIUS_TUI_REDUCE_MOTION=1` disables task animation. Animation runs only for visible active tasks and stops when the work is idle or the view is destroyed.

Task details expose recorded ownership, dependencies, requirement and acceptance links, sources, affected paths and action constraints when supplied. **A completed checklist item is not independently verified work.** Worker output remains a candidate; the existing workflow's host-bound receipts and exact artifact versions govern verification. The interface does not advance these states itself.

Recorded orchestration shows actual execution, context compaction, trajectory checkpoints, completion holds and terminal receipt identities. A scoped workflow worker also exposes its exact assignment hash, matching the input hash used in its receipt, with the admitted plan/card references and scope/tool counts. This is the latest assignment observation, not a history of every worker. Resumed observations are marked “Last observed”; unfinished historical execution is not displayed as currently attached.

## Public notes and persistence

The `working_notes` tool supports add, list, search, summary and clear. Notes intentionally supplied through this tool are public operational records, not hidden model reasoning or verification evidence. Host-bound session identity takes precedence over a model-supplied session identifier.

Notes persist at `$OMNIUS_HOME/working-notes/<session SHA-256>.json`; metadata-only activity persists at `$OMNIUS_HOME/task-observations/<session SHA-256>.json`. Without `OMNIUS_HOME`, the root is `~/.omnius`. Todos retain their existing `todos/<session>.json` location. Notes clear only within their session, and note IDs/revisions continue monotonically. Corrupt or unreadable stores produce an unavailable state instead of fabricated empty success. Competing note writes return a retryable busy result rather than blocking terminal rendering.

Native snapshots are bounded to 256 tasks and 64 notes with explicit omitted counts. Active tasks and ancestors are prioritized; long display text ends in an ellipsis. Full notes remain accessible through the tool. Activity storage excludes raw prompts, assistant output, tool arguments/results and private reasoning. It is advisory observability, not a second task acceptance ledger.

## Scoped context

Workflow assignments now use a deterministic versioned context envelope. Host authority, tool/path scope, frozen acceptance references and exact evaluator inputs are separate from quoted input artifacts. Large source bodies are omitted whole with their immutable retrieval references. Authority itself is never silently truncated: an oversized contract requires splitting the card. Fields that the current invocation does not provide remain explicitly unavailable.

This change uses the existing workflow controller, workboard, task contracts and trusted child receipt boundary. It does not add a cross-process task scheduler, fenced task leases or automatic independent worktrees. The broader orchestration brief's follow-on gaps, frozen acceptance criteria and verification evidence are tracked in [.aiwg/planning/task-orchestration-20261017](../../.aiwg/planning/task-orchestration-20261017/contract.md); the primary-source review is in [research.md](../../.aiwg/research/task-orchestration-20261017/research.md).
