The case timeline, reconstructed.

A case is a six-month conversation across letters, filings and hearings.

A technical or legal studio runs on cases rather than on orders and invoices. Each case lives across deposited filings, expert reports, calendar hearings, internal notes between collaborators and a paper trail that often outlives the lawyer originally assigned to it.

Lemnia T3 sits on the studio's headless server (LAN). When a case is reopened after months, the recap is ready in 60 seconds. When a new associate joins the team, the reasoning behind every past decision stays consultable and is not lost with whoever left the studio.

What the case-file actually contains.

• PEC Aruba + Legalmail

  Indexed separately from regular mail to preserve its legal value: subject lines, attachments, ricevuta di consegna.

• Dropbox / Google Drive folders

  The case folder structure (Cliente, Pratica, Atti). Lemnia reads PDF, DOCX and scanned letters via OCR.

• Microsoft 365 / Google Calendar

  Hearings, depositions and on-site inspections, joined to the case they belong to.

• Internal collaborator notes

  Notes a junior associate added to a filing count as first-rank sources, cited like any external document.

What the studio actually reads.

• Cases and handover

  The timeline of a case rebuilt from letters, filings, expert reports and calendar hearings, together with the dossier of everything a colleague follows. Made for reopening after months of inactivity or for onboarding a successor. Every step cites the document, with no performance assessment.

• Pre-meeting brief

  Fifteen seconds before a hearing or a client meeting, it summarises the case state, open questions, last filing and next deadline. Three cited figures, also available by voice.

• Management digest

  Weekly anomalies, such as a deadline coming due or a hearing approaching, and a periodic read for the partners. It stays descriptive, with every figure traced to the document.

• GDPR + AI Act compliance

  DPIA state, access log, sub-processor list and the AI Act art. 50 trail in a single BLAKE3-signed PDF for the DPO or the auditor.

Forensic synthesis runs on the cloud, not on the laptop.

The most ambitious feature of the legal vertical, F37 forensic synthesis (a cited-retrieval narrative draft for medico-legale review), runs only on cloud-burst, under firm limits: 2-hop graph traversal, citation-or-refuse with a 0.8 NLI threshold per fragment, an HITL gate per section. The local model never runs agentic loops.

The defensible posture stays non-negotiable, with Tribunale di Siracusa 338/2026 (Art. 96 c.p.c. gross negligence) as its anchor. Every paragraph drafted by Lemnia is anchored to a source filing. When the source does not exist, the answer is "Non ho evidenza sufficiente per questa affermazione.", with no invented citation.