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
Before Day 1 — Define Authority + Confirm Readiness
Confirm one workflow and the authority posture SEAL will evaluate.
- 20-minute fit conversation
- Guided filing authority intake
- Firm-confirmed authority posture
- Identify required facts and source owners
- Technical Readiness & Signal Map
- Readiness decision
- Finalize written review scope
No new production workflow or direct database/document-repository access is required merely to complete the first review.
“Is this workflow sufficiently defined and technically ready for a 30-day observe-only review?”
30-Day Observe-Only Review
For 30 days, SEAL evaluates the agreed final-submit authority question without controlling the production filing.
- One governed workflow
- One final-submit boundary
- One named workflow owner
- Agreed authority conditions
- Would Have Approved
- Would Have Refused
- Would Have Routed for Supervision
- Weekly review of findings
- Reviewable decision records
- No production filing is disrupted, delayed, or altered during the review
“Are the authority findings useful, understandable, and supported by evidence?”
Leadership Decision
At the end of the review, leadership chooses one of four paths:
- Stop
- Continue observing for a defined reason
- Improve source information or authority rules and review again
- Separately consider one narrow controlled-enforcement path
Nothing moves into controlled enforcement automatically.
“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
Before Day 1 → 30-Day Evidence Period → Leadership Decision
What the 30-Day Observe-Only Review Includes
Before observation begins, the firm confirms the authority posture for one filing workflow, Thinking OS maps the minimum facts required to evaluate that posture, and the parties confirm that the workflow is ready for review.
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 authority conditions in scope and how the firm expects each to be treated
- 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 firm-confirmed authority posture.
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 Day 1 — Define Authority + Confirm Readiness
- Guided Filing Authority Intake
- Firm-confirmed authority posture
- Named workflow + authority-rule owners
- Minimum Signal Map
- Technical Readiness review
- Readiness decision
- Finalized written review scope / charter
During the 30-Day
Observe-Only Review
- One scoped final-submit workflow
- Would Have Approved findings
- Would Have Refused findings
- Would Have Routed for Supervision findings
- Weekly review of governed findings
- Reviewable decision artifacts
- Observe-only and non-blocking throughout
- No production filing blocked, delayed, or altered
At the End —
Leadership Decision
- Final Risk Ledger
- leadership recommendation
- Stop
- Continue observing for a defined reason
- Improve source information or authority rules and review again
- Separately consider one narrow controlled-enforcement path
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.
1. 20-Minute Fit Call
- Determine whether there is one real final-submit workflow worth examining and identify the likely workflow owner.
2. Guided Filing Authority Intake
- Confirm the final-submit boundary and the firm’s authority posture: what counts as authorized, not authorized, or requiring supervision for that workflow.
3. Technical Readiness & Signal Map
- Identify the minimum facts required, where they come from, who owns them, and whether they are available and connected to the filing before it goes out.
4. Finalize Scope, Diligence & Commercial Terms
- Resolve any remaining security, operational, commercial, and written-scope questions. Finalize the Review Charter and explicit exclusions.
5. Readiness Decision
- Confirm that the workflow is ready, ready after identified confirmations, should be narrowed, or is not currently ready for the review.
6. Run the 30-Day Observe-Only Review
- Record Would Have Approved, Would Have Refused, and Would Have Routed for Supervision findings; review them weekly; no production filing is blocked, delayed, or altered.
7. Make the Leadership Decision
- Stop, continue observing for a defined reason, improve source information or authority rules and review again, or separately consider one narrow controlled-enforcement path.