How SEAL Evaluation Works
Start with one filing workflow.
Observe one final-submit authority boundary for 30 days.
End with evidence and a written leadership decision.
SEAL Legal Runtime is evaluated through a narrow, staged process designed to determine whether the control is useful before the firm is asked to rely on it.
At A Glance
Fit + Diligence
Determine whether there is one real filing workflow and one final-submit boundary worth examining.
- 20-minute fit conversation
- review public / diligence materials
- identify likely workflow and owner
- confirm whether deeper diligence is warranted
- no client-system connection required
“Is there a credible workflow and authority question worth evaluating?”
30-Day Observe-Only Review
A narrow, 30-day review of one named workflow and one final-submit boundary.
- One governed workflow
- One workflow owner
- One technical contact
- One weekly review cadence
- Observe-only and non-blocking
- No production filing is disrupted, delayed, or altered during the review
“Does this control produce useful authority findings and reviewable evidence in a real workflow?”
Leadership Decision
At the end of the review, leadership chooses one of four paths:
- Stop
- Continue Observe-Only
- Improve Signals and Re-Review
- Consider One Narrow Controlled-Enforcement Path
“Does the evidence justify any next step?”
Why This Path Exists
SEAL is not introduced as a broad software rollout.
The path advances only as the evidence justifies it.
- First, fit and diligence determine whether there is one credible workflow and authority question worth evaluating.
- Then, a 30-day observe-only review evaluates SEAL at one designated final-submit boundary under real workflow conditions.
The review asks three questions:
- whether the governed outcomes behave consistently;
- whether would-have-refused and supervised-review findings are useful and understandable;
- whether the decision artifacts are clear enough for leadership to review without engineering support.
The review is non-blocking. No production filing is blocked, delayed, or altered.
Only after the review does the firm decide whether to stop, keep observing, improve signal quality, or separately approve one narrow path to controlled enforcement.
Responsibility and Control
You
define
the authority model.
SEAL evaluates it at runtime.
In controlled enforcement, the governed outcome can become authoritative for the separately agreed wired path.
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:
- operating the governance runtime within agreed scope
- returning review findings for the scoped workflow
- producing reviewable decision artifacts
- maintaining the runtime’s security, integrity, and availability posture
- supporting bounded integration and artifact routing as agreed
Evaluation, 30-Day Observe-Only Review, and Optional Controlled Enforcement
What the 30-Day Observe-Only Review Includes
Every review is governed by a simple written charter that makes scope, ownership, review criteria, and stopping conditions explicit.
The charter defines:
- the exact governed workflow
- the final-submit boundary
- the named workflow owner
- the actors and roles in scope
- the would-have-refused conditions in scope
- the observe-only, non-blocking posture
- pause and stop conditions
- evaluation criteria
- the weekly artifact review cadence
The review does not require a firmwide rollout or a change to day-to-day legal practice.
It covers one governed workflow, one final-submit boundary, one review cadence, and one defined authority scope.
No production filing is disrupted, delayed, or altered during the 30-day review.
The goal of the 30-day review is to determine whether SEAL provides a useful authority decision and evidence surface that the firm’s existing controls do not already provide sufficiently well.
If the answer is no, stopping is a valid result.
What Makes a Good First Workflow
We do not recommend starting with “all legal work.”
The best first review is one narrow filing workflow where authority matters at final submit.
Good candidates typically have:
- delegated filing steps involving lawyers, paralegals, staff, or automation
- a meaningful possibility of role or authority mismatch
- required consent, authority evidence, or supervision conditions
- recurring or deadline-sensitive filing activity
- a clearly identifiable final-submit boundary
- a named workflow owner and usable source signals
The 30-day observe-only review is best suited to a regional or midsize law firm with one real filing workflow and one final-submit boundary leadership wants to examine.
What You Get
Before the Review —
Fit + Diligence
- access to the public evaluation materials
- external proof packet review
- evaluator-visible evidence review
- bounded diligence discussion
- no client-system connection required
During the 30-Day
Observe-Only Review
- one scoped final-submit workflow
- a minimum signal map
- weekly review of governed findings
- reviewable decision artifacts
- a final risk ledger
- a leadership recommendation
- observe-only and non-blocking throughout the review
At the End —
Leadership Decision
- final risk ledger
- leadership recommendation
- stop / continue / improve signals / consider controlled enforcement
- no automatic expansion
- no automatic enforcement
Nothing moves into controlled enforcement automatically.
Security and Compliance Fit
SEAL is designed to fit inside a serious legal control posture.
- vendor-hosted for the current bounded evaluation posture; production deployment, hosting, security, and availability requirements are addressed separately in diligence and written scope
- uses the firm’s policy, identity, matter, and workflow context as sources of truth
- produces reviewable decision artifacts designed for firm leadership, risk, audit, and other qualified review where the firm chooses
- 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
Non-public runtime details are handled under diligence.
Who It’s For
Managing Partners
See whether one filing workflow has authority, role, or supervision gaps before enforcement is ever considered.
GCs / Risk Leaders
Review decision artifacts showing what would have been approved, refused, or routed before a filing leaves the firm.
Legal Ops / IT / Workflow Owners
Review one final-submit workflow using minimum structured signals without replacing your matter system, DMS, IAM, GRC, or filing tools.
How to Move Forward
For GCs, Managing Partners, and practice leaders, the path starts with a fit call.
- 20-Minute Fit Call
– Determine whether there is one real final-submit workflow worth evaluating. No architecture review or integration commitment is required at this stage. - Confidential Briefing / Diligence
– If there is a credible fit, move under NDA as appropriate and review the authority model, workflow boundary, proof surfaces, and diligence questions. - Agree the Review Charter
– Define the workflow, roles, refusal families, observe-only posture, success metrics, review cadence, and pause / stop conditions. - Run the 30-Day Observe-Only Review
– Evaluate governed outcomes and artifacts in real workflow conditions without production blocking. - Make the Leadership Decision
– Based on the evidence, the firm may stop, continue observe-only for a defined reason, improve signals and re-review, or separately consider one narrow controlled-enforcement path.