matter-update

Matter update logging works by capturing the event type, date, and summary, then appending it to history.md and refreshing the _log.yaml portfolio log. This structured approach ensures consistency across procedural, discovery, substantive, strategy, and administrative developments.

When logging a new matter development, you can automatically update impacted fields in _log.yaml including status, stage, next deadlines, risk level, materiality, exposure range, owners, and legal hold status. This ensures the portfolio log reflects current matter conditions accurately.

Materiality tracking enforces explicit user confirmation prompts for substantive events, strategy shifts, settlement activity, risk re-assessments, and regulatory developments. This materiality re-check trigger prevents accidentally skipping a required disclosure posture change during the update logging process.

No, you cannot use this Skill if the matter slug is missing from _log.yaml. An unbypassable conflicts gate refuses to write to history if the slug is not present, preventing unauthorized or mismatched entries from corrupting your litigation portfolio records.

The best way to record settlement authority changes is through this Skill's enforced settlement-acceptance prompt, which requires explicit user confirmation before writing the update. This ensures settlement activity is properly logged in history.md and triggers materiality reclassification checks.

Yes, user confirmation is required before any updates are written. The Skill displays the proposed entry and diff for history.md and _log.yaml, writing the changes only after the user explicitly confirms the displayed modifications are accurate and acceptable.