Articles & Publications
Legal Architecture
Translating legal expertise into the architecture of LegalTech and FinTech products: AI service logic, risk matrices, and technical specifications for developers.
How a Service Reads a Register Response: Five Rules
"Found" and "not found" in a register response are not yet a conclusion about the client. Five rules for a legal service and a table for the specification.
Client Consent to a Check and the Credit History
How to draft client consent to a check under 152-FZ: what to record, where its limits lie and the special rules for credit histories under Law 218-FZ.
Third Parties and the API Provider in Client Checks
Data of a director, founders and dispute participants in a register response: how to notify them, who answers for the API provider and what 152-FZ risks.
“The Register Is Open” Does Not Mean “You May Use the Data”
An open register does not cancel the personal data law. Four grounds under 152-FZ, a court example and how to record the balance of interests.
Client API Verification: What a Legal Service May Check
Client API verification in a legal service: which registers are open, which are closed, and three questions to ask before every request.
Red Flags in LegalTech: When a Legal AI Service Hands the Case to a Human
Red Flags in a legal AI service: when it stops and hands the case to a lawyer. Examples from bankruptcy, labor disputes and personal data.
What Is Triage Logic in LegalTech?
What Triage Logic is in LegalTech: how a service sorts requests by urgency and risk and when it hands a case to a lawyer, with a labor dispute example.
How to Write a LegalTech Spec
How to write a technical specification for a LegalTech service: six steps, from a parameter table to test scenarios, with a worked example.
Where's the Line Between a Glitch and a Refusal?
A LegalTech product needs to tell "the server didn't answer" apart from "the law says no." Here's what happens to a user when the product mixes the two up.
Startup Due Diligence
Startup due diligence: what investors actually check before a deal, and why the product's legal logic usually gets skipped.
Legal Architecture Audit
Legal architecture audit: a fast review that finds legal risk in a live product — worth doing before you sign a deal with an investor.
Legal Architect for a Startup
Legal architect for a startup: three questions for a founder that reveal, in five minutes, whether an investor's money is protected from million-ruble fines.
Data Leak: ₽400K Instead of ₽10M
A real Russian case: a company paid ₽400,000 instead of ₽10–15 million for a personal data leak — a rare stroke of luck, not the rule.
AI in Court: A ₽50,000 Fine
AI in court handed a company citations to court rulings that don't exist — the result: a ₽50,000 fine. We break down where the check should have happened.
Legal Architect vs Developer
Both roles seem to "build LegalTech." I break down how a legal-logic architect differs from whoever writes the platform's code — and why you need both.
AI Law 2026: Risks for LegalTech
There's no special AI law for API startups yet, but the risks are real: regulators, Civil Code rules, and the first AI-hallucination fine.
Choosing Your Legal Architecture Format
The landing page offers four formats. I break down each one in plain language: what's included, who it's for, and how to know which one you need.
LegalTech Glossary: Investors & Founders
25 legal-architecture terms explained in plain English — what they mean, why they matter, and how they work, with everyday analogies and no jargon.
Prompt Engineer vs Legal Architect
Founders and investors mix them up constantly. I draw the line between a prompt engineer and a legal architect — and why a product needs both roles.
OpenAI/Telon: LegalTech Architecture
OpenAI named LegalTech startup Telon an implementation partner. Here's why that role calls for legal engineers who translate law into algorithms.