For AI platforms and integrators.
A generic AI platform solves the generic case. Public contracts are not the generic case: the clause counts letter by letter, a repealed rule still governs, and the wrong answer becomes a fine or a lawsuit. The Public Contract Layer is the depth a platform adopts instead of building.
The depth you do not have to build.
- Concession ontology — Obligations, deadlines, adjustment, guarantees, penalties and supervening acts as entities, not loose text.
- Literal verification — The clause citation is checked character by character at the source, without AI. What does not match is discarded.
- Rules and validity — The regulatory base by sector, with an alert for a repealed rule that still reaches the contract in force.
- Human assertion with a trail — Every decision by a person has an author, a date and an immutable record — who asserted what about the contract.
- Curation by discipline — Legal, engineering, operations and economic-financial as the common backbone across the studios.
In an AI platform’s vocabulary.
| Permissions | Five roles and per-user features, decided per resource. |
|---|---|
| Guardrails | Literal verification of the citation at the source, without AI. Without a passage, the layer does not assert. |
| Evals | A second model's shadow over a sample; a switch only after it is measured and approved by a person. |
| Alerts | Deadlines, urgency in bands and a repealed rule that reaches the contract in force. |
| Orchestrator | Single model gate; the base reading projects matrix, manual and analysis in order. |
| Knowledge | Regulatory base by sector and the living contract records — amendments, official letters and service orders. |
| Data | Comes in through a connector that pulls from the client's source (spreadsheet-link, MCP, REST); leaves through six authenticated exports — matrix, manual, obligations, mitigations, plan comparison and users. |
Brazil, concessions and PPP.
- Sectors — water and sanitation, highways, energy, mobility.
- Residency — database and files hosted in Brazil.
- Privacy — LGPD.
One contract, anonymized data.
14days from contract intake to published matrix, on the first contract in production.
Rollout advances by milestones, each verifiable in the system itself:
- Milestone 1Base reading of the contract
- Milestone 2Matrix published
- Milestone 3Human assertion, with a trail
- Milestone 4Operation