matter-intake

Legal matter intake standardizes the capture of new litigation or investigation cases by collecting identification, conflicts posture, risk triage, and key dates into uniform portfolio metadata. It then generates a structured matter.md, seeds history.md, and appends a tracking row to _log.yaml.

A conflicts check gate records the conflicts posture as cleared, pending, not-run, or waived during legal matter onboarding. It enforces stopping behavior when required, while supporting user-confirmed bypass with an auditable rationale for pending or waived statuses.

To log a new legal dispute into a litigation portfolio, the intake process collects matter details and writes a narrative matter.md file, seeds an append-only history.md opening event, and appends a structured row to matters/_log.yaml for rollups and tracking.

Yes, matter intake captures outside counsel details, internal owners, and legal hold status alongside jurisdiction, matter type, and materiality. This ensures all critical metadata is recorded uniformly for downstream portfolio workflows and status updates.

Risk triage and materiality are captured during the matter intake process by collecting standardized metadata fields for each new case. This structured approach ensures consistent risk assessment across the portfolio for downstream rollups and status tracking.

Matter intake operates with no external dependencies, using standard file outputs like matter.md, history.md, and _log.yaml. It fits attorney workflows for onboarding cases into a litigation-legal portfolio without requiring specific case management platforms.