matter-update

To log litigation matter updates, append a dated event to history.md and refresh the portfolio log. This structures scattered developments into a consistent, audit-ready record with event type, date, and summary fields.

Updating a matter portfolio log after a settlement shift requires appending the strategy event to history and triggering a settlement-acceptance safety check. This enforces materiality reclassification and authority validation for non-lawyers before writing.

Yes, you can record procedural milestones and discovery events against a specific matter slug. The system enforces a conflicts gate requiring the slug to already exist in _log.yaml before accepting any structured update inputs.

Risk re-assessment during ruling or regulatory updates forces explicit reclassification questions for materiality. It prompts you to evaluate impacted fields and reclassify risk levels before appending the dated event to the matter history.

Yes, an existing matter entry in _log.yaml is required. The conflicts gate validates the matter slug exists before allowing any history appends or portfolio log field changes, preventing updates to untracked matters.

Non-lawyers face a settlement-acceptance materiality and authority safety check when logging settlement updates. This gate ensures explicit risk reclassification and validates authorization before the event writes to history.md or updates _log.yaml.