matter-intake

Legal matter intake standardizes registration by collecting identifiers, conflict-check outcomes, and risk routing inputs in a guided flow. It generates a slugged case code, writes matter.md, seeds history.md, and appends a structured entry to _log.yaml for portfolio tracking.

During legal matter intake, the conflict check enforces a stop condition when status is not cleared, pending, or not-run, unless an override is applied. This stop rule is governed by the office CLAUDE configuration to prevent registering compromised matters.

Yes, legal matter intake supports contract disputes, labor disputes, IP, administrative/regulatory matters, and internal investigations. It routes these case categories while capturing jurisdiction, cause of action, counterparty details, and initial posture for downstream workflow.

Registering a new litigation matter tracks evidence preservation and court deadlines by capturing stakeholder assignments and evidence-hold data during intake. This information is written into matter.md and history.md to maintain an auditable record for operations.

Running a new matter intake workflow generates a slugged case code, writes a detailed matter.md file, seeds history.md with the initial event, and appends a structured line to matters/_log.yaml to enable portfolio aggregation and status tracking.

Legal matter intake requires no external dependencies but relies on the office CLAUDE configuration to enforce conflict stop and override rules. This configuration determines whether the workflow blocks registration when conflict checks return pending or not-run statuses.