Four layers in a Claude decision
| Layer | Question | Evidence |
|---|---|---|
| Product | Claude app, API, Claude Code or a cloud marketplace? | Enabled surface and administrator |
| Model | Which pinned model ID and lifecycle? | Request logs and model documentation |
| Data | Training, retention, region and safety review? | Operative terms, configuration and exception |
| Workflow | Which sources, tools, actions and approvals? | Permission map and reviewer record |
What Fable 5.1 changes
Anthropic documents the API model ID claude-fable-5-1, a 1M-token context window, 128K maximum output and current list pricing. The company positions it for long-running and enterprise work. Those are product facts and vendor claims. They do not establish legal accuracy, privilege treatment or value on a firm’s matters.
Training and retention are different fields
Anthropic’s public commercial terms say customer content is not used to train models unless the customer agrees. Its covered-model guidance separately describes a 30-day retention rule for covered models, with platform details and eligible exceptions. “No training” therefore does not mean “no retention.” Record both.
Enterprise controls still depend on the route
Anthropic describes Enterprise audit logs, SCIM and compliance tooling, while cloud marketplaces bring their own agreements and architectures. Enterprise Frontier Safeguards were announced as a phased program rather than a control every customer already has. Ask for current availability and scope instead of copying a roadmap claim into a policy.
A useful first evaluation
Select a repeatable task with public or approved data and an existing review standard. Fix the input packet and expected structure. Disable unnecessary tools. Record source fidelity, material omissions, corrections, run cost, reviewer time and export quality. Expansion requires a new decision for each data class and action boundary.
Where Claude sits in a legal stack
Claude may be the interface, an API model inside another product, a coding tool or one component behind a legal vendor. The system of record should remain explicit. A polished model response is not the matter file, contract repository, citation record or final approval.
| Vendor question | Operational evidence |
|---|---|
| What workflow does the product own end to end? | Inputs, transformations, tools, outputs and handoffs |
| Where is the system of record? | Repository, retention and export path |
| What happens when the model is wrong? | Detection, reviewer, rollback and correction log |
| What if the vendor or model changes? | Version pin, notice, regression test and exit path |
MCP and connectors expand the permission boundary
A connector can make a workflow more useful by reaching source systems. It also changes which data and actions are in scope. Inventory each tool, credential, destination and write permission. Start read-only, require approval for material actions and preserve the source record outside the conversation.
Ask what a legal wrapper adds
A legal product built on Claude may add licensed sources, matter controls, templates, integrations, logging, evaluation and support. Those additions can be the real product. Ask which failure modes the wrapper changes and which remain inherited from the underlying model. If the answer is only a model name, the procurement record is incomplete.
Claims this page does not make
- Claude preserves privilege in every configuration.
- A certification covers every feature and connector.
- A large context window makes a result complete.
- A model benchmark predicts work on a specific matter.
- A vendor confidentiality promise replaces the executed agreement.
FAQ
Does Anthropic train Claude on law-firm business data?
Anthropic’s public commercial terms say it does not train on customer content unless the customer agrees. Verify the exact product, account, feedback setting and operative agreement.
Is Claude Fable 5.1 zero data retention?
Not by default. Anthropic describes a covered-model 30-day retention rule and eligible exceptions. Confirm the approved exception and platform scope.
Can Claude be used for legal research?
It can be evaluated for a defined research workflow, but every controlling authority and material factual assertion still needs independent verification.
Sources checked
- Claude Fable and Mythos 5.1 release, checked 2026-09-03.
- Fable 5.1 model overview, checked 2026-09-03.
- Covered Models retention practices, checked 2026-09-03.
- Commercial Terms, checked 2026-09-03.
- Enterprise Frontier Safeguards, checked 2026-09-03.
Operational information, not legal advice. Verify current terms, account configuration and applicable professional duties before use.