matter-briefing

To prepare a litigation briefing, the system loads the matter workspace files (matter.md, history.md, _log.yaml) and generates a structured snapshot summarizing posture, recent changes, next CPR deadline, and open questions. It enforces an unbypassable conflicts gate and flags staleness if last_updated exceeds 30 days.

A conflicts gate is an unbypassable validation check that refuses to generate a matter briefing if the specified matter slug is not present in the matter log. It ensures only verified matters proceed to the briefing workflow and risk recalibration.

You track CPR deadlines and staleness by loading the matter log, which surfaces the next CPR deadline and flags staleness when the last_updated timestamp exceeds 30 days. The briefing workflow automates this check alongside risk recalibration.

No, you cannot brief on a matter slug missing from the log because the conflicts gate refuses to generate the briefing. The slug must be present in the matter log to pass the gate and proceed with the workflow.

Yes, you need to run matter intake for that slug before generating a briefing, as the workflow requires loading existing matter workspace files (matter.md, history.md, _log.yaml) and applying risk calibration from the CLAUDE config.

The best way to summarize recent changes is to use a briefing workflow that extracts the most recent 3 to 5 entries from the matter history file, showing what has moved since the last update alongside current posture, exposure, and open questions.