CasePatronSign in

DECERNERE · NON · OPERARI

A complete legal operating system, designed and built by one lawyer.

Portfolio

One lawyer. Every line.

CasePatron was designed and built entirely by Cesar Augusto Taborda Lima, the lawyer responsible for TL LAW: the data model, the interface, the isolation between offices, the deadline engines and the doctrine that governs its AI. It runs inside his own practice.

TL LAW

Scale

The platform, measured.

15
visa programs live
434
API endpoints
2,311
automated tests
37
scheduled jobs
29
granular permissions
252,000
lines of TypeScript

Counted from the codebase on October 16, 2026.

The house

Five products, one spine.

Each product keeps its own brand, vocabulary and data. Underneath, the same identity, permissions, audit and languages.

ICM

United States immigration
  • 15 visa programs: EB-1, EB-2 NIW, EB-3, O-1, L-1, H-1B, H-2A, H-2B, family-based and K-1
  • One template per visa, with its own stages, checklist and vocabulary
  • USCIS, DOL and DOS forms prepared from case data: I-129, I-130, I-140, I-485, I-864, ETA-9142, DS-260 and more
  • PERM recruitment calendar and deadline cascade from a deterministic engine
  • Visa Bulletin tracking and priority dates
  • Portals for clients and sponsoring employers
  • Knowles, an AI associate that drafts under mandate

LIDE

Brazilian litigation
  • Court publications captured at the source
  • Procedural deadlines counted in business days, holidays included, by a deterministic engine
  • Filings that begin as drafts
  • Case import from existing systems
  • Client portal and an installable app

Base

Legal finance
  • Invoicing, cash flow and monthly close
  • Multiple currencies, with exchange rates locked at creation
  • Bank statement import and reconciliation
  • Automated collections
  • Client money segregated from the firm's
  • Append-only ledger: the past is corrected by new entries
  • An autopilot that proposes and a human who approves

Brasil For You

Global mobility into Brazil
  • A signed bridge from the public website into a lead quarantine
  • AI qualification drafts, adopted by a human
  • Brazilian visa cases with their own stages
  • Mobility programs: employers, demands, selection and journeys through nine gates
  • An employer portal

Radar

Where clients come from
  • Lead attribution by channel, from first visit to signed case
  • Google Search Console and Analytics, read-only
  • Access tokens sealed with AES-256-GCM and bound to each office

Under the hood

The spine every product inherits.

Structural isolation

Each office lives on its own database path. A request across offices answers not found.

29 granular permissions

Roles are presets; capabilities are enforced on the server on every request.

Mandatory two-factor

Every staff account signs in with an authenticator app.

Audit trail

Sensitive actions are logged with who, what and when.

Data protection by design

Per-client export and erasure, with deletion cascading across every linked record.

Deterministic engines

Deadlines, stages and attribution come from reproducible code, never from a model.

AI under mandate

Every AI output starts as a draft that cites its sources and marks its gaps.

Three languages

English, Portuguese and Spanish across the platform.

Doctrine

Four rules the AI cannot break.

  1. It acts by mandate, never on its own.

    Every AI output is born a draft, with its gaps marked. It becomes an act only after human review, or inside a mandate that is explicit, logged and interruptible.

  2. Every claim points to its source.

    Each extraction carries the link to the document it came from. Without a source, the answer is a declared gap, never invented text.

  3. Every reading carries a confidence label.

    Each extracted field arrives sealed. Nothing is accepted silently: you see how far each piece of data can be trusted.

  4. Deadlines stay outside the AI.

    Due dates come from a deterministic engine that is auditable and reproducible. The AI may flag that a deadline exists; the date comes from the engine.

Isolation

Every office is a vault.

Each office's data lives on its own path in the database, never in a shared table with a filter on top.

A request for another office's data receives the same answer as data that does not exist: not found. The system does not even confirm it is there.

Your office
Another office
Another office
404 · NOT FOUND

Origin

CasePatron was not commissioned from a software factory. It was designed by the lawyer responsible for TL LAW, for his own practice.

It is not an off-the-shelf product. It is the working instrument of a practice.

Built inside a practice. Running inside it today.