Verifaid

Controlled pilot

Decides whether a signature can legally proceed: it reads corporate documents and powers of attorney, cross-checks public registries, and says who can sign and within what limits, citing the exact page. 50+ operations cleared for a paying client.

Role: Lead developer, LegalShelf
Period: Jul – Sep 2026
Status: Controlled pilot

operations cleared: 50+
commits in six weeks: 262
pipeline stages: 7
automated tests: 596

Figures as of 11 September 2026.

Problem

Before a lender disburses a loan, lawyers read the borrower's corporate documents to confirm that the person signing actually has the authority to sign, and up to what amount. It is slow, it depends on who reads it, and the reasoning is rarely written down in a way someone else can check.

Every datum cites document, version, page and excerpt. A person approves.

Constraints

The system may recommend, but a named person must approve every conclusion.
Nothing may be asserted without a citation to document, version, page and excerpt.
Synthetic data only until a real-data gate is passed; originals are preserved untouched.
Each client organization's data must be isolated at the database level.

Decisions

Citations before conclusions
Every extracted fact carries its source, and the citation viewer opens the real page with the excerpt highlighted. A cited page is worth more than a confidence score.
Read the law the way a lawyer does
Signing caps are read from the clause itself, including amounts written out in words, and attorneys-in-fact are read from the appointment clause. The powers catalog follows the Civil Code.
Isolation in the database, approval as a granted power
Row-level security in PostgreSQL isolates each organization, the API authenticates the caller instead of trusting a header, and the right to approve is granted explicitly rather than inherited from a role.

Line drawing of the verification path: documents, power of attorney, registry, seal — Documents and powers are read, checked against registries, then sealed by a person.

Outcome

Verifaid returns a decision, not a report: whether signing can proceed, why it cannot, and who holds the authority to sign. It has cleared more than 50 operations for a paying client. In six weeks the platform went from an empty repository to a controlled pilot: a seven-stage pipeline, a citation viewer, traceable human approval where every review keeps its rationale, and a second person required to approve. Dictamen signing and the path to real client documents are the next milestones.

Evidence

50+ operations cleared for a paying client.
262 commits and 85 merged pull requests between 29 July and 11 September 2026.
311 API tests (52 of them tenant-isolation tests) and 285 web tests at the last known-good run.
Private codebase under the client's confidentiality terms; a walkthrough is available on request.

Stack

PythonFastAPIPostgreSQLNext.jsReactTypeScriptClaude APICloudflare R2RenderVercel