Compliance Agent
The Domain Execution Agent that resolves a jobsite's country into the right permit, zoning, and legal-contract paperwork for Construction & Real Estate — a jurisdiction specialist that hands back a ready-to-file form the moment it knows which country a jobsite is in.
What Is the Compliance Agent?
Construction paperwork is not the same everywhere. A Turkish jobsite files Ada, Parsel and Pafta cadastral references, a contractor's social-security registration number, a site manager's certificate number, and floor-area ratios. A US jobsite instead files a Parcel ID, a Contractor License Number, an OSHA Certification Number, and a Zoning Classification. Getting this right by hand, per screen, per country, is exactly the kind of repetitive jurisdiction lookup a compliance specialist does every day — and exactly the kind of task this agent takes over.
Compliance Agent centralizes that expertise: give it a country and a document type, and it returns the correct fields for that jurisdiction, with the right validation built in. Adding a new jurisdiction extends the agent's own knowledge, not the individual screens that ask it for a form.
In one sentence
Given a country and a permit type, Compliance Agent knows exactly which fields that jurisdiction's paperwork requires and hands back a ready-to-render form — the same judgment a compliance specialist would make instantly for a jobsite they know well.
How It Works — Resolve, Prepare, Present
Every request follows the same path from "which country is this jobsite in" to "a working, jurisdiction-correct form on screen":
| Step | What happens |
|---|---|
| 1. Resolve | The agent reads the country code for the jobsite and recognizes it as Turkey, the United States, or, for any other country, falls back to a safe generic form — it never fails to return something usable. |
| 2. Prepare | The matching jurisdiction's field set is assembled — labeled inputs, some with format validation, some numeric with sensible ranges — plus a submit action. |
| 3. Present | The prepared form renders inline in the screen that asked for it, using the same shared rendering path every other server-driven form in TotalApp uses. |
What the Agent Needs to Prepare a Form
To prepare the right paperwork, Compliance Agent needs only two things:
Country
The jobsite's country, which decides which jurisdiction's paperwork the agent prepares. Required on every request.
Document Type
What kind of permit or record this is — a building permit, a zoning record, or a legal contract/lien. Labels the resulting form.
What the Agent Returns — Jurisdiction-Specific Fields
| Jurisdiction | Fields returned |
|---|---|
| Turkey | Ada, Parsel, Pafta (optional), Contractor Social Security Registration Number, Site Manager Certificate Number, floor-area ratio fields (TAKS, KAKS/Emsal), then a submit action. |
| United States | Parcel ID, Contractor License Number, OSHA Certification Number, Zoning Classification, then a submit action. |
| Any other country | A safe generic form — document type, site address, and optional notes — for any jobsite in a country without a dedicated jurisdiction profile yet. |
Format validation travels with the form itself
Fields like the Contractor Social Security Registration Number or Contractor License Number carry their own format check directly on the field, so the screen that renders the form already knows how to enforce it without any extra validation code of its own.
How Teams Actually Use It
Filing a Permit, Zoning Record, or Legal Contract
Inside the Add/Edit modal on Permit Applications, Zoning & Land Use Rules, or Legal Contracts & Liens (all three in Construction → Permits & Zoning Compliance), a "Generate Form" button asks Compliance Agent for the jobsite's resolved jurisdiction and renders the result inline. A Turkish jobsite's user sees the Ada/Parsel/social-security fields; a US jobsite's user sees Parcel ID/OSHA fields — the same jurisdiction judgment either way.
Switching Jurisdiction Mid-Record
Each of the three screens carries its own jurisdiction picker, pre-filled from the selected jobsite but overridable per record. Changing it re-asks the agent and swaps the presented fields to match — useful when a holding company is filing paperwork in a country different from where the jobsite itself is registered.
Where the Compliance Agent Fits
Compliance Agent's entire job is recognizing the right jurisdiction and preparing its form — it has no persistence layer or settings screen of its own. It exists specifically so permit, zoning, and legal screens across Construction (and, in principle, any future add-on with country-specific paperwork) can ask "what does this jurisdiction need?" once, in one place, instead of re-deriving the same jurisdiction logic in every screen that needs it.
| Screen | What it asks for |
|---|---|
| Permit Applications | A permit form matching the category picked in the modal (building, environmental, or scaffolding). |
| Zoning & Land Use Rules | A zoning-record form. |
| Legal Contracts & Liens | A legal-contract form. |
The submitted values themselves are stored by the screen that collected them, not by Compliance Agent — the agent's role ends once the correct form has been handed back.