Feature. The Dismissal Engine
The Attorney Approval Ceremony. The Gate That Holds The Platform’s Posture.
The gate every draft motion crosses to become an approved attorney work product. The approval is not a button. It is a structured event the API enforces: firm-staff authentication, an attorney workspace account, a bar number, a bar-number match if the attorney profile carries an expected bar number, a document body, and a citation-verification status of passed or passed_with_review_required. On approval, the API records motion status attorney_approved, the SHA-256 hash of the document body, the attorney’s bar number, the attorney’s user identity, and the approval timestamp.
AI On This Page
Buddy Stages The Named Attorney Approval; Nothing Court-Bound Exits Without It.
Buddy is The IMC Machine’s AI assistant. Talk, upload, or speak – Buddy turns what you send into structured records you approve before anything moves.
Talk To Buddy
“Stage The Approval For The 39.14 Production”
Buddy assembles the approval packet with every file, transcript, and worksheet ready for review.
Upload A Photo
Drop A Signed Bar License Image.
Buddy reads the license and confirms attorney identity against the approval ceremony record.
Voice Note
Voice-Approve The Production.
Buddy records the named approval with timestamp, voice file, and the production set sealed at that moment.
Buddy autofills are reviewable. Nothing publishes, files, or sends without a named human approval on the record.
Why a ceremony, not a checkbox
The Gate Is The Structural Answer To AI Hallucination Risk.
A legal-AI product that drafts motions has two ways to handle the question of whether the draft is correct. The lazy way is to add a disclaimer at the bottom of the document and a checkbox in the UI that says “I have reviewed this draft.” The serious way is to make approval an event the system records and the platform’s downstream behavior depends on. The Approval Ceremony is the serious way. The platform’s render-and-filing surface refuses to run on a motion whose record does not show an approval event with a verified bar number, a citation-verification status that cleared, and a SHA-256 hash of the exact document body the attorney saw. The Drive upload does not happen without the approval. The filing packet does not generate without the approval. The mark-filed action does not run without the approval. This converts a posture into a property. The platform cannot file automatically. The platform cannot render a filing packet against an unapproved draft. The boundary is enforced server-side, in the API, where the browser cannot bypass it.
The required inputs
Six Conditions, All Of Them Present, On The Same Request.
The API rejects an approval request that is missing any of the six conditions. The error message names the missing condition. The motion does not advance until the condition is satisfied.
Required 01
Firm-Staff Authentication
A valid Supabase JWT for a user who passes requireFirmStaffAuth. Both valid auth and presence on the firm-staff email allowlist. The browser does not hold the service-role key; server-side credential handling validates auth before the request reaches the approval endpoint.
Required 02
An Attorney Workspace Account
The user account is marked as an attorney in the firm’s workspace. Firm-staff accounts (paralegals, investigators, intake staff) can move drafts through the early lifecycle states, but the approval transition is reserved to accounts whose attorney status is verified.
Required 03
A Bar Number
The approval request must carry the attorney’s bar number. The bar number is the operational identity the platform records on the motion. What the eventual filed motion will reference and what the audit log preserves as the attorney of record on this approval.
Required 04
A Bar-Number Match
If the attorney’s workspace profile carries an expected bar number, the request’s bar number must match. The platform refuses to record an approval that names a different bar number than the firm has on file for the user. This catches typos before they become court-filed errors.
Required 05
A Document Body
The exact text the attorney is approving must be present on the request. The hash recorded on the motion is computed against this body. If the attorney edits the draft after approval, the post-edit version requires a fresh approval. A new hash, a new timestamp, a new audit row.
Required 06
Citation Verification Status
The motion’s citation-verification status must be passed or passed_with_review_required. A status of failed blocks the approval. The verification step exists because the model that drafted the citation can be wrong about whether the citation says what the draft claims it says; the platform refuses to record an approval that the verification step did not clear.
What gets written
Five Facts, On The Motion Record, On Approval.
When the six conditions are satisfied, the approval API writes five facts to the motion’s record. The five together constitute the approval ceremony in the platform’s audit log.
- Motion status: attorney_approved. The motion advances to the lifecycle state that permits the filing-ready render and the Drive upload of the filing packet.
- SHA-256 document hash. The hash of the exact document body the attorney approved. Any subsequent edit to the body produces a different hash and requires a fresh approval.
- Attorney bar number. The attorney of record on this approval, as identified by their licensing identifier.
- Attorney user ID. The platform’s internal identifier for the attorney’s workspace account, so the audit can resolve the bar number against the named user.
- Approval timestamp. The server-side time the approval transition was recorded. The timestamp anchors the motion’s audit trail.
None of these fields can be retro-edited. An attorney who wants to change a recorded approval is recording a new approval, with a new hash and a new timestamp, against a new version of the document. The history is preserved.
After approval
The Platform Renders The Packet. The Attorney Files.
What The Render-And-Filing API Does
With approval recorded, the API loads the firm’s court-filing template, fills caption/party/matter/attorney variables, renders the PDF and DOCX, uploads them to Court Filings/Drafts/ in the matter’s Drive tree, and returns a manifest with the generated files and their Drive URLs. Case-specific argument placeholders that the attorney completed during review render into the final packet exactly as the attorney edited them.
What The Attorney Does
From here, the attorney files. The platform records the manual eFileTexas envelope ID and the filed date as separate fields, entered by the attorney or firm-staff after the filing actually occurred. There is no automated filing step. There is no “the platform filed it for me” condition. The Dismissal Engine drafts, explains, organizes, and prepares. The attorney approves, edits, signs, and files. Nothing files automatically.
The Principal Product Control
The Approval Ceremony is the platform’s principal product control around legal authority. The three-model consensus gate exists upstream against AI hallucination risk; the approval ceremony exists downstream to ensure that no motion reaches the filing surface without a named, bar-licensed attorney recording their approval against a specific document body whose integrity the platform can verify with a hash.
Why The Gate Matters Beyond The Firm That Uses It
Gideon v. Wainwright, 372 U.S. 335 (1963), established the Sixth Amendment right to counsel. The cliché concern about AI in criminal defense is that someone will let a model file a motion without an attorney’s read. The Approval Ceremony makes that concern an architectural impossibility on this platform, regardless of which firm or which deployment. The promise of Gideon is meaningful only if the work product reaching the court genuinely carries the attorney’s judgment.
See the ceremony on a draft
A Thirty-Minute Walkthrough Of The Gate, End To End.
We will walk a draft motion through citation verification, through the approval gate, through the bar-number match, and through the hash-and-timestamp record. And stop at the point where the platform hands the filing packet to the attorney for filing.
Why This Matters
A Named Human Decision, Enforced Server-Side.
Legal-AI products that draft motions face a structural question: how does the system know the draft is correct? A checkbox at the bottom of a page is not an answer. With 104 U.S. exonerations in 2024 involving official misconduct5 and the State of Texas paying $156M to exonerees since 20096, the cost of a weak gate is concrete. The Attorney Approval Ceremony is the load-bearing element of the platform’s posture: an API-enforced event requiring firm-staff authentication, a verified attorney account, a bar number with match, a document body, and a passing citation-verification status. On approval, the API records the motion status, a SHA-256 hash of the document body, the bar number, the attorney’s identity, and the timestamp. Aligned with the ABA’s framework for indigent-defense systems7, the gate converts posture into a property of the system.
Sources
Where The Numbers Came From.
Sources and citations
- RAND / NCSC / ABA, National Public Defense Workload Study (2023). rand.org; ABA Journal coverage.
- Sixth Amendment Center, State of the Nation on Gideon’s 60th; Bureau of Justice Statistics, State Government Indigent Defense Expenditures.
- Texas Tribune, Feb. 27, 2025; SMU Dedman / Deason Center, “Country Justice in Texas.”
- Colorado Public Radio, Jan. 2, 2026; The Journal.
- National Registry of Exonerations, 2024 Annual Report. DPIC coverage; Registry homepage.
- Zealous Advocate, $156M paid to Texas exonerees since 2009.
- Three-Model Consensus aligns with the Attorney Approval Ceremony; reviewable framework. See ABA Standing Committee on Legal Aid and Indigent Defendants.
- Texas Code of Criminal Procedure Article 39.14; Watkins v. State (2021) analysis; 2025 remedies update.
Learn This Product
Want the working order, in a course?
Continue Learning
Learn The Evidence Orchestrator
Five sequential modules on defense-side evidence preparation: the matter record, multi-format intake, the Cockpit, the three-model consensus gate, and the Article 39.14 native-file posture.
Open The Course →Continue Learning
Learn The Dismissal Engine
Five sequential modules on defense-side motion practice: the firm-control premise, the dismissal pathway library, evidence-to-motion drafting, the six-state lifecycle, and the attorney approval ceremony.
Open The Course →