matter-close

To close a litigation matter, the skill validates the matter slug against `_log.yaml`, captures the resolution type, date, final exposure, and lessons learned, then appends closing blocks to `matter.md` and `history.md`.

Archiving a dismissed litigation case involves updating the `_log.yaml` file and appending a closing entry to the matter's markdown files, ensuring the record remains intact without deletion for portfolio tracking.

Yes, the matter closure workflow enforces a hard conflicts gate before performing any consequential archive actions, ensuring compliance and preventing conflicting closure data from being written to the portfolio.

Yes, you can track final exposure and costs for a judgment outcome by inputting the final exposure or cost values during the closure process, which are then archived in the matter log and narrative files.

Supported resolution types for closing a matter in a legal ops portfolio include settlement, dismissal, judgment, withdrawal, and consolidation, covering various litigation conclusion scenarios.

Validating the slug against `_log.yaml` is required to confirm the matter exists in the portfolio system before archiving, preventing erroneous closure actions on non-existent or improperly identified matters.