From the Public Safety edition of October 20, 2026
Louisiana Fifth Circuit Court of Appeal buys two on-premises AI servers to build open-weight-model tools for filing compliance and intake, kept separate from its case management system
Louisiana Fifth Circuit Court of Appeal (with ALEA Institute) · Courts / appellate court operations · Louisiana, United States
- Publisher
- [sch]Legal Tech (Judge Scott Schlegel)
- Original publication
- October 20, 2026 (Judge Scott Schlegel’s newsletter, co-authored with Chief Judge Susan Chehardy)
- Source retrieved
- 2026-10-21
What happened
Two judges of the Louisiana Fifth Circuit, including Chief Judge Susan Chehardy, describe the court’s purchase of two AI servers plus added power and cooling, and a partnership with the ALEA Institute to build applications on an open-weight model. Planned first uses are filing compliance checks (page limits, pagination, missing exhibits) and intake classification, later citation verification, prompt-injection screening and eventually neutral bench memoranda. Staff were interviewed about workflows first. The AI environment is kept separate from the case management system, outputs are suggestions that employees verify, and the court continues to use commercial GenAI tools. No results are reported yet.
Why it matters
A rare first-hand account of a U.S. state court choosing on-premises open-weight infrastructure alongside commercial cloud tools, with explicit reasoning about cost uncertainty, security responsibilities and isolating experiments from official records. It is directly relevant to court IT leaders weighing hybrid AI architecture.
Evidence and measured results
Opened the Oct. 20 post co-authored by the chief judge. It is an operator self-account describing purchases, design choices and plans; it reports no costs, server specifications, model names, performance data or timelines. Future capabilities such as citation verification and bench memoranda are stated as goals.
Limitations and uncertainty
Self-reported account by the court’s own judges; early stage; no metrics or costs; partner named with a non-endorsement disclaimer; applicability to courts without IT capacity is limited.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-21; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Courts face rising workloads and uncertain AI costs, and want tools fitted to their own filing rules.
- Stakeholders
- Chief judge
- Clerk of court
- Court IT director
- Staff attorneys
- Self-represented litigant services
- Discovery questions
- Which filing defects cause the most rework?
- Does the court have facility capacity for AI hardware?
- What commercial GenAI tools are already in use?
- Who would verify AI suggestions?
- Value hypothesis
- Narrow, rule-based filing checks on court-controlled infrastructure may reduce avoidable deficiencies if validated.
- Potential engagement
- Options analysis comparing on-premises and cloud deployment for one filing-compliance use case.
- Unsupported claims
- Cost savings versus cloud
- Accuracy of compliance checks
- That bench memoranda tools are ready
Pre-sales engineering
Role takeaway
- Fit
- Courts with in-house IT and facility capacity considering hybrid AI architecture.
- Architecture and integration
- Isolated on-premises inference environment reading copies of filings, returning advisory flags, with no write access to the case management system.
- Prerequisites
- Server room power and cooling
- Open-weight model selection
- Documented filing rules and staff workflows
- Constraints
- Hardware operations burden
- Limited in-house AI expertise
- Local court rules vary
- Security
- Patch and monitor AI servers like other critical systems and screen incoming documents for prompt-injection content.
- Proof of value
- Proposed: run compliance checks on past filings and compare with clerk-identified defects
- Proposed: measure staff time to verify suggestions
Delivery
Role takeaway
- Work
- Interview staff, build advisory filing-check tools, and evaluate them in isolation before integration.
- Dependencies
- Facility upgrades
- Development partner
- IT staff availability
- Ownership
- Clerk of court and court IT director under the chief judge
- Skills and adoption
- IT staff learn model operations alongside the partner; clerks learn to verify and override flags.
- Governance checkpoints
- No writes to official records
- Testing gate before any CMS integration
- Separate validation for each new task type
- Acceptance criteria
- Proposed: defect detection precision and recall measured on historical filings
- Proposed: zero automated changes to the case record
- Risks
- Security assumed rather than verified
- Scope creep toward judicial drafting
- Key-person dependency on partner
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Hybrid model: on-premises open-weight inference for court-built tools, commercial cloud GenAI retained; the experimental environment is isolated from the case management system of record.
Governance
Who approves, reviews and stays accountable for outcomes?
Outputs are advisory; employees perform official filing review; the system will not recommend rulings; closer integration requires rigorous testing first.
Security and privacy
What data, permissions and controls need testing?
The judges note on-premises does not make a system immune to security issues; planned screening for prompt injection in incoming filings.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Pre-submission feedback could help self-represented litigants; staff knowledge was captured through interviews; in-house IT is learning alongside the development partner.
Procurement
What should contracts, pricing and exit terms secure?
Capital purchase of servers and facility upgrades plus a development partnership, instead of buying a ready-made product.
Operating model
Which teams own the service once it runs?
Court IT must operate power, cooling, maintenance and cybersecurity for AI hardware; tools are built from staff-described workflows outward.
Publication history
- 2026-10-20Public Safety · Issue 426 resources
Stable resource ID: louisiana-fifth-circuit-on-premises-open-weight-ai-court-20261020