legal-practice-v1
The Legal Practice harness pack — everything that makes the AI sound and think like it works at a law firm.
Out of the box, the AI is a smart generalist — it doesn’t know what a “matter” means to a law firm or a “punch list” means to a contractor. A harness pack is the training binder that teaches it one industry: how to talk (prompts and tone), what words mean (glossaries that map industry terms to real records and fields), where to send each kind of question (routing rules with worked examples), and what it must never do (guardrails).
A pack changes how the AI behaves — never what it can access. Permissions are enforced below this layer, and nothing in a pack can widen them.
Packs are versioned like software releases, and a new version can only go live after it passes its test suite. Packs also stack: every industry pack sits on the platform foundation, and individual builders and their customers can fine-tune on top without losing their tweaks when the pack upgrades.
How this pack is layered
When the AI answers, the most specific layer wins, piece by piece.
The layer every pack builds on: safe routing habits, security guardrails, and a neutral business vocabulary.
Adds the legal layer on top: matter and docket vocabulary, practice-area examples, compliance notices.
Builders and their customers can adjust individual pieces further. Their tweaks are stored separately and survive pack upgrades.
What’s inside
The 14 pieces, by kind.
| Kind of piece | Count |
|---|---|
| Prompts The AI’s job description and tone | 1 |
| Routing rules Which kind of question goes where | 1 |
| Glossaries Industry words mapped to real records | 3 |
| Worked examples Questions with the right answers shown | 4 |
| Guardrails The never-do list | 2 |
| Action sets Actions the AI may offer here | 2 |
| Lane preferences Which model handles what | 1 |
Versions
Open versions & publishing| Version | Status | Tests | Went live | |
|---|---|---|---|---|
| v3 | Draft | All tests passed | — | Publish |
| v2 | Live | Passed | Mar 14, 2026 | |
| v1 | Retired | Before testing existed | Jan 30, 2026 |
Behind this page/templates/harnesses/:harnessPackKey · catalog publisher/validator
Retrieve
sp_GetHarnessPack returns the header, active components, and BasedOn chain; the version strip reads TemplateVersions filtered to TemplateType='HarnessPack'.Save
Read-only hub — authoring happens on Components, Versions, and Eval Sets.Success
- Harnesses configure behavior, never access — nothing here can widen a permission envelope.
- Builder / Tenant layers are downstream tenant-AI-DB rows shown as context.
- Same TemplateVersions store as page templates: lifecycle tooling carries over.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.