Procedure is infrastructure.
A procedural execution layer that identifies the correct motion, enforces the court’s authority and scope, and prevents irreversible filing errors before they happen. Not a document generator. A procedural decision engine.
It begins with constraints, not arguments.
MotionLogic does not start with a motion name. It does not assume a legal theory. It starts from the litigation problem and works backward through procedural logic.
Describe the procedural problem in your own words. MotionLogic identifies the legally correct motion, ranks the alternatives, and flags the filings that would waive rights, destroy finality, or block appeal. For every motion it maps the source of the court’s authority, the scope of what the court may consider, and the decision rule the court must apply, then builds a jurisdiction-aware, court-ready scaffold: required sections only, correct sequencing, mandatory findings highlighted, improper arguments excluded.
Five layers of procedural control.
Each layer enforces a constraint. Together they prevent silent procedural failure from reaching the court.
- Procedural issue classification
The problem is classified before any motion is named: what happened, at what stage, under which rules.
- Motion selection engine
The legally correct motion, with the alternatives ranked and the filings that would waive rights, destroy finality or block appeal flagged.
- Standards and scope generator
The source of the court’s authority, the scope of what it may consider, and the decision rule it must apply.
- Constrained motion scaffolding
Required sections only, correct sequencing, mandatory findings highlighted, improper arguments excluded. Jurisdiction-aware.
- Risk, exposure and audit layer
What the filing puts at risk, and a record of why each choice was made.
Same procedural logic, for a human or for a system.
Every conclusion must cross a checked bridge from authority to result.
MotionLogic follows the 12 Bridges framework. Legal reasoning is constrained, not creative: a “therefore” in a brief must cross one of the recognized doctrinal bridges (direct holding, established multi-case doctrine, recognized analogical extension, a fortiori reasoning, statutory codification, overruling-chain completion and the rest) or it is argument, not law. By design MotionLogic cannot cite a case that does not exist and cannot assert a “therefore” the procedural logic does not support.
The twelve bridges, explained →Human UX
Plain-English intake, ranked options, a scaffold you can edit. No motion selection required.
System interface
The same procedural logic, callable by the drafting workflows so that what gets drafted is what the court may consider.
Authority, not information
Research tools return documents about a motion. MotionLogic returns what the court may do, must find, and will refuse.
Filing errors prevented
Waived rights, destroyed finality, blocked appeal: the irreversible ones, caught before filing.
Procedure determines outcome.
In a demo we take a procedural problem in your own words and show what MotionLogic returns: the motion, the alternatives it ranked, and the filings that would have cost you a right.