How SEAL Evaluation Works
Start with a confidential evaluation.
Observe one high-risk legal workflow.
Move to controlled enforcement only after scoped review and written agreement.
SEAL Legal Runtime is available through a staged evaluation path designed to make adoption narrow, safe, and governable.
Why This Path Exists
SEAL is not sold as a broad AI platform.
It is introduced through one governed action class at a time — where the risk is clear, the workflow is narrow, and the value of a pre-execution authority gate is easy to understand.
The goal is not to replace your systems or change firm behavior overnight.
The goal is to place SEAL in front of one high-risk legal action and evaluate three things in real conditions:
- the runtime behaves consistently
- refusal and supervised-review behavior are visible
- the decision evidence is reviewable
At A Glance
1. Confidential Evaluation
A bounded vendor-hosted evaluation track for GC, risk, procurement, and technical reviewers.
- No client system connection required.
- No production workflow change.
- Review governed outcomes, decision artifacts, proof packet, and evidence surfaces.
“Is the gate real, legible, and worth deeper diligence?”
Observed Checkpoint Pilot
A narrow observe-only pilot for one named workflow and one final-submit checkpoint.
- one governed workflow
- one workflow owner
- one technical contact
- one review cadence
- no production blocking in Phase 1
“Would this governed checkpoint create useful evidence without disrupting normal practice?”
Controlled Enforcement`
If the observed pilot proves useful, the firm may separately approve controlled enforcement for agreed refusal categories and agreed workflows.
- coverage expands only by written scope
- enforcement applies only to agreed workflows
- the firm remains owner of policy, authority, supervision, and legal judgment
“Are we ready to rely on this as a mandatory governance control for this workflow?”
Responsibility and Control
You define the authority model.
SEAL enforces it at runtime.
The firm remains responsible for:
- policy posture
- identity and access model
- matter and workflow selection
- legal judgment and professional supervision
- how the organization practices law
Thinking OS™ is responsible for:
- correct operation of the governance runtime within agreed scope
- returning governed outcomes for scoped workflows
- producing reviewable decision artifacts
- maintaining the runtime’s security, integrity, and availability posture
- supporting bounded integration and artifact routing as agreed
Confidential Evaluation, Observed Pilot, and Controlled Enforcement
What an Observed Pilot Includes
Every observed pilot should be governed by a simple pilot charter.
A pilot charter defines:
- the exact governed workflow
- the final-submit checkpoint
- the workflow owner
- the users or roles in scope
- the refusal families in scope
- the observe-only posture
- rollback conditions
- success metrics
- artifact review cadence
The first pilot does not require firmwide rollout.
It is one governed workflow, one final-submit checkpoint, one review cadence, and no production blocking in Phase 1.
Good First Workflows
We do not recommend starting with “all legal work.”
The best first pilots are narrow, high-consequence action classes such as:
- filing under the wrong authority
- restricted motions requiring supervision
- missing consent, authority, or supervision on a high-risk legal action
- deadline-sensitive external actions where accountable escalation matters
The first design-partner pilot is best suited for a regional or midsize law firm with one real filing workflow, one workflow owner, and one final-submit boundary worth observing.
What You Get
Under confidential evaluation, you get:
- access to evaluation materials
- proof packet review
- evidence surface review
- bounded diligence discussion
- no client system connection required
Under observed pilot, you get:
- one agreed workflow scope
- governed outcomes for in-scope attempts
- decision artifacts for governed attempts
- a structured pilot charter
- bounded integration support where required
- a weekly or agreed review cadence
- an executive-ready pilot readout
Under controlled enforcement, you get:
- governed approvals, refusals, and supervised overrides for agreed workflows
- decision artifacts for audit, insurer, regulator, and internal review
- enforcement only for agreed refusal categories and scoped workflows
- the ability to expand coverage over time by written scope
What the License Does Not Grant
The SEAL license does not grant:
- access to internal runtime details, proprietary logic, policy structures, models, or rule internals
- the right to repurpose SEAL outside its licensed scope
- the right to host SEAL internals in your environment unless separately agreed
- a substitute for legal judgment, professional supervision, or ethics obligations
SEAL is a governance control.
It is not the practice of law.
Security and Compliance Fit
SEAL is designed to fit inside a serious legal control posture.
- vendor-hosted in a bounded evaluation or enterprise environment
- uses the firm’s policy, identity, matter, and workflow context as sources of truth
- produces decision artifacts that support audit, insurer, regulator, and internal review
- does not replace your GRC, IdP, DMS, matter system, or system of record
- does not use client artifacts or matter data to train public models or improve other clients’ systems
Public materials describe the runtime’s behavior and evidence surface.
Non-public runtime details are handled under diligence.
Who It’s For
For law firms
Stop wrong-authority filings, disclosures, and approvals before they leave the firm. Preserve privileged workflows while creating reviewable decision artifacts under firm-controlled authority.
For legal departments
Show what was allowed, refused, or escalated under organizational authority — with a decision record your risk, audit, and leadership teams can review.
For legal tech vendors
Add a pre-execution authority gate in front of high-risk actions without rebuilding your models, replacing your UX, or exposing internal logic.
How to Move Forward
For GCs, Managing Partners, and practice leaders, the path starts with a confidential briefing.
- Confidential Briefing (Under NDA)
– A focused conversation on workflow fit, authority model, and proof surfaces. - Select One Governed Workflow
– Choose one narrow, high-risk action class where the value of the gate is clear. - Agree the Pilot Charter
– Define scope, roles, refusal families, observe-only posture, rollback conditions, success metrics, and artifact review cadence. - Run the Observed Checkpoint Pilot
– Evaluate governed outcomes and artifacts in real workflow conditions without production blocking in Phase 1. - Decide Whether to Move to Controlled Enforcement
– If the pilot proves useful, the firm may activate controlled enforcement for agreed refusal categories and agreed workflows under separate written scope.
Bottom line
You do not need to believe the whole category at once.
You need one safe way to evaluate whether a pre-execution authority gate belongs in front of one high-risk legal action.
That is what this staged evaluation path is designed to make possible.