| name | vertical-legal |
| title | /vertical-legal |
| description | Pre-configured legal vertical pack for the ai-brain-starter substrate. Ships typed-memory categories for matter management and privilege handling, retention defaults aligned with ABA Model Rule 1.15 and state-bar variations, and connector configurations for Clio, NetDocuments, and iManage. Use when onboarding a law firm, in-house legal department, or legal-ops team that needs the substrate to come pre-shaped to the work rather than starting from a blank vault. |
| author | adelaidasofia |
| author_url | https://github.com/adelaidasofia/ai-brain-starter/tree/main/skills/vertical-legal |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | us |
| practice | general |
| language | en |
/vertical-legal
A pre-configured pack that turns the empty substrate into a legal-ready system in one install. The pack ships typed-memory categories that match how a matter actually moves, connectors for the three platforms most firms already pay for, retention defaults that map to the ABA Model Rules, and decision-audit patterns for privilege handling and conflicts checks.
Why this exists
A blank install of the substrate forces every legal team to invent the same vocabulary on day one: what is a matter, what is a privileged document, what is a conflicts check, how long do we keep depositions. The vocabulary is not novel. Every firm in North America runs roughly the same primitives, with the same retention obligations, against roughly the same three document management platforms.
This pack ships the primitives so the firm can spend day one on what is actually theirs (their playbooks, their authority chain, their client list) instead of re-deriving the category structure.
What this pack sets up
Run /vertical-legal init and the pack writes:
| Layer | What ships | Where it lands |
|---|
| Schema | 8 typed-memory categories with frontmatter contracts | schema/typed-memory-categories.md |
| Connectors | Clio, NetDocuments, iManage specs and OAuth flows | connectors/*.md |
| Retention | Per-category retention rules mapped to ABA Model Rule 1.15 and state variations | retention/defaults.md |
| Decision audit | Privilege-handling guardrails and conflicts-check pattern | decision-audit/*.md |
Nothing is auto-applied to a live install. The pack stages drafts under drafts/ and prints the path; the firm reviews and accepts before merging into the production memory layer.
Categories shipped
- matter
- client
- opposing-counsel
- privilege-tagged-doc
- retention-policy
- billing-event
- deposition-note
- court-deadline
See schema/typed-memory-categories.md for required and optional frontmatter on each.
Connectors shipped
connectors/clio.md — Clio API, OAuth2, per-firm key, sync cadence, write-back rulesconnectors/netdocuments.md — NetDocuments REST and ndOffice API
