Practice Daily Triage

---
name: practice-daily-triage
description: Produce an explicitly requested read-only practice attention brief from a bounded mail scope and the local matter register. Does not process an inbox or change records.
---

# Daily attention brief

This is an optional instruction module read through the workflow catalog. It
does not add an installed host skill, setup module, mailbox connection or
background task. Use when the lawyer asks for a practice-wide attention brief;
use inbox workup for filing attachments or drafting replies.

Sibling skill links identify the shared workflow prose. For actual operations,
follow the active host's installed owning skill and installed references after
the catalog's dependency check. An absent dependency remains unavailable.

Read [scope and authority](../../workflows/scope-and-authority.md),
[source verification](../../workflows/source-verification.md) and
[matching and reporting](references/matching-and-reporting.md). Load
[dates](../../workflows/dates.md) when a date affects the recommendation.

## Establish scope

Record the lawyer's bounded mail query or source selection, start/end and
timezone, result/body limits, and tracker scope. Resolve missing material bounds
before searching. No request supplies standing access to unrelated accounts.
The bundled intake acquires one resolved matter's mail; it cannot run a
practice-wide mailbox sweep. Wider mail review requires source-complete supplied
messages or an actually available, authorized active read/search connector that
supports the agreed scope. Never invent a broad command, global cache or tool.

If access or coverage is missing, finish the available tracker or supplied-mail
brief and identify exactly which cross-check could not be made. Supplied messages
establish their own contents, not the current state or completeness of an inbox.

## Review and rank

1. Read the selected open register rows through
   [matter tracker](../../../skills/practice-matter-tracker/SKILL.md); record snapshot time and
   scope. Read mail metadata first, then complete relevant bodies and needed
   attachments. Paginate the agreed query and report every cap or interruption.
2. Match threads using the reference. Preserve ambiguity and multi-matter
   relevance; keep unidentified material separate. Resolve each selected matter
   before opening its files. Read only sources needed for its flagged issue.
3. Establish current instructions, later replies and commitments before calling
   an item unanswered or outstanding. A processing checkpoint is not evidence of
   a reply or completion; a Sent observation is not delivery, filing or service.
4. Cross-check due/overdue next actions, protective dates, missing ownership and
   unexplained staleness against the newest relevant evidence. A stale brief or
   tracker flag still deserves attention, with its age and unreviewed newer
   correspondence disclosed. Preserve unresolved protective risks.
5. Rank by earliest plausible consequence and reversibility of delay. Separate
   an asserted date from a legally verified deadline. The bundled jurisdiction
   profile supplies no deadline calculator. Use a supplied verified calculation
   or a separately authorized suitable calculation facility, with verified legal
   inputs and current sources. Do not substitute generic legal-date arithmetic.
6. Present the reference's brief. Proposed writes remain proposals and go to the
   owning tracker/calendar workflow only after exact approval. This run changes
   no mailbox state, matter memory, register or calendar.

## Completion

Report source coverage, ambiguity, protective items and the smallest useful
next actions. Say "no urgent items located in the reviewed scope" only after
both agreed mail and tracker checks completed; otherwise state the missing
check. A clean report is a scoped finding, not a claim that the whole practice
has no risk.