matter-update

To log litigation history events, append a dated event to the matter's history file and update the centralized matter log row. This synchronizes status, risk, and deadline information to keep the portfolio current.

Tracking risk re-assessments and deadline updates requires appending the event to the matter history and updating the matter log row. The system enforces explicit materiality confirmation when risk moves or deadline updates occur.

Materiality confirmation prompts for explicit approval when selected event types, such as settlement posture shifts or substantive facts, may require reclassification. An additional settlement-acceptance check applies before flipping materiality for acceptance scenarios.

Yes, you can use it for user-driven logging of procedural, discovery, substantive, strategy, stakeholder, and administrative updates across an existing matter workspace, provided the matter exists in the repository log.

Matter management logging requires an unbypassable conflicts gate to verify the matter slug exists in the repository log, specifically within the _log.yaml file, ensuring updates only apply to validated matters.

When appending events to litigation history, the system writes to history.md and automatically updates the last_updated timestamp and affected fields in the centralized matter log to maintain consistency.