Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Get Started ↗ JA
Home/Use cases/Government & public sector
Government & public sector

Document checks stay rigorous. The procedure gets faster.

Attach a proof to the records you issue and the counter receiving them can confirm they are genuine on the spot — removing most requests for originals and most calls back to the issuing office.

Counter terminal — checking a presented record
Verified
DOC HASH0x68d4…9f01
IssuerCity Office
Issued2026-07-28
SubjectTax certificate
Proof classProvenance
Signature matches Tamper check Issuer confirmed
A case study in
the public sector
Metawater's "MizuDAkO" — proving residents' activity records are genuine, without exposing personal data
Read the case study →
01 — Why LemmaWhat slows a procedure down is checking the paperwork.

A resident collects a tax certificate at one counter and submits it at another, where someone confirms by eye that it is genuine. One document gets handled three times — issued, presented, checked. Digitizing it does not remove the loop, because anyone can produce a PDF: if the receiving side cannot check independently, it ends up asking for the original anyway. What digitization leaves out is a way to check.

One document,
handled three times.

02 — What changesThree things Lemma changes
Counter checks that never wait on a query

Settle on the spot whether a presented record is genuine. No phone call to the issuing office, no follow-up request for the original.

Counter terminal
Record presentedTax certificate (FY2026)
IssuerCity Office
Query to issuerNot needed
VerdictVerified
Open data catalog
Population statistics (monthly)CSV / JSONProof attached
Facility registerJSONProof attached
Tender resultsCSVProof attached
Budget & settlementCSVProof attached
Published data that is actually usable

Publish statistics and registers with proof attached, and businesses or researchers can confirm the origin before they build on them. Fewer inquiries land back on your desk.

Issuing attestations to businesses, simplified

Today, staff produce a tender-eligibility or license attestation by hand for every application. Issue it automatically instead.

POST /v1/documents
// Register the qualification record { "integrityHash": "sha256:…", "issuerId": "city-office" } // What comes back { "docHash": "0x68d4…9f01" }
03 — Threat casesWhat happened when the check became a formality.

Three cases touching government and public services, drawn from the Lemma Critical Briefs. In each one the authenticity of a record or a decision was the point of contention.

See every Brief in this area →

04 — How it worksThree steps, and that's it.
Issuing the proof
RecordTax certificate (FY2026)
IssuerCity Office
What is sentHash only
Issued 0x68d4…9f01
01Attach a proof
Why it holdsChange one character in the record and it no longer matches the proof.
One API call at issuance, or register it from a form. The body of the record is never sent.
The record you issue
Tax certificate
Proof attached — verify here
02Hand it over
Why it holdsThe proof itself is about 200 bytes. How you deliver it is up to you.
The record carries a verification link. PDF or paper — nothing about how you issue it has to change.
The receiving counter's screen
Not tampered with
SignatureTamper checkIssuer
03They check it
Why it holdsThe receiving side settles it alone, without contacting the issuer.
Open the link and the verdict appears. No account, no key.
05 — Use casesHow it is used in this industry
06 — Latest newsAdoption, and what is moving in this area

See all blog posts →

Public Sector

Where does the waiting
at your counter actually start?

We map your current verification flow with you and identify the documents that generate the wait. It starts with a 30-minute call, and we stay with you from pilot to production.