◆ THE MISSION

Most AI legal tools generate against an internet-trained foundation model and call it done. The output sounds like every other tool, the citations occasionally don't exist, and the firm has no way to make tomorrow's draft sound more like them than today's did. VOUX CORE inverts that. Every draft is grounded first in your firm's own past work — your motions, your briefs, your house style — and the foundation model second. The longer you use it, the more it picks up your jurisdiction quirks, preferred clause libraries, and the arguments that actually win for your matters.

◆ TEXAS-FIRST, ON PURPOSE

We're building for Texas civil practice first because the constraints are specific and the procedural surface is large enough to matter — 254 county clerks, 14 Courts of Appeals, the Supreme Court, the Court of Criminal Appeals, the 5th Circuit, PACER, OAG opinions, and a discrete (and well-documented) disciplinary regime. Building one product that handles all of that well is a higher bar than building a generic legal tool that “works everywhere.” Once the Texas product is working for closed-beta firms, we expand state by state — never by feature dilution, always by adding another jurisdictional layer with the same depth.

◆ THE CONSTRAINTS WE TOOK ON

• Privilege first. Tex. Disciplinary R. 1.05 isn't aspirational; it's the box we live in. Every architectural choice — tenant isolation, audit logging, retention defaults, model provenance — is downstream of that rule.
• Paralegal supervision is a feature, not a footnote. Tex. Disc. R. 5.01 / 5.03 binds attorneys for the work their non-lawyer staff produce. The approval queue is the supervisory record; UPL guardrails are enforced at three layers (model, route, UI).
• Citations either exist or they don't. Cite-check before export, cite-check before filing. Hallucinated authority is a bar grievance waiting to happen and we treat it as a hard fail, not a soft warning.
• The firm's corpus is theirs. Full export on request, scheduled deletion on cancellation, written deletion certificate for the malpractice carrier or bar grievance file. No model is ever trained on tenant data.

◆ WHO BUILDS THIS

A small team that includes people who've filed pleadings, sat through discovery disputes, and lost arguments to opposing counsel they wished they'd known more about going in. The product is opinionated because it has to be — every default has a reason rooted in either the disciplinary rules or the actual workflow of a Texas civil practice. Where the defaults need to flex (matter-specific style overrides, firm-wide compliance gates, supervisory configurations), they flex. Where they shouldn't flex (citation verification, audit logging, the tenant boundary), they don't.

Press, partnerships, procurement: rollingsentiment@gmail.com.