Fewer policy errors
A rule references the same catalog path the agent emitted. There is no translation step in between to get wrong.
Industry vocabulary
Rules that read like your industry, not like code
VeriProof ships a catalog of field names and values for each industry it covers, taken from the standards your teams already follow. Agents emit those names, policies are written against the same names, and reviewers read a plain-language label.
Why a shared vocabulary matters
When every team invents its own field names, the agent emits one thing, the policy checks another, and the reviewer reads a third. Rules drift from what the application actually sends, and the gap only shows up when someone is looking into an incident.
Less coordination
Policy authors and developers work from one published catalog instead of agreeing on names workflow by workflow.
Readable evidence
Business, compliance, governance, and audit users read a plain-language label and a citation, not a code your team invented.
One payment status, three audiences
A single catalog entry serves the agent, the policy, and the person reviewing the record.
The agent emits a standard field
banking.payment.iso20022_status = ACSP. The attribute name and the permitted values both come from the catalog, so the application does not invent either one.The policy matches the same name
data.banking.payment.iso20022_status. Policy authors reference the published path rather than a string agreed in a meeting.The reviewer reads the label
"Accepted Settlement in Process", with a citation to ISO 20022 pacs.002. Nobody needs the code explained to them.
Every value in every catalog carries a plain-language label and the standard it came from.
Anchored to the standards your industry already uses
Each catalog is built on published industry standards rather than a taxonomy VeriProof invented. A few examples of the primary standard behind a catalog:
Scroll horizontally to see all columns.
| Industry | Primary standard |
|---|---|
| Banking and financial services | BIAN v13/v14, with ISO 20022 message families |
| Mortgage and loan processing | MISMO v3.6.2 Reference Model |
| Insurance: P&C, life and annuity | ACORD 2.0 P&C XML and AL3 standards |
| Healthcare and life sciences | HL7 FHIR v6.0 |
| Telecommunications and IT operations | TM Forum Open API v5.0.1 |
| Manufacturing, supply chain and logistics | ISA-95 (ANSI/ISA-95) Parts 1 to 6 |
| Energy and utilities | IEC 61968 distribution management interfaces |
| Government and public sector | NIST SP 800-53 Rev 5 |
| Legal and regulatory technology | Akoma Ntoso 1.0 (OASIS) |
| GRC, ESG and enterprise risk | ISO 31000:2018 |
| Agentic payments and stablecoins | Google AP2 v0.2 Agent Payments Protocol |
Open an industry to see its subdomains, catalog entries, permitted values, and the source behind each one.
Common questions
No. The catalog is there so your teams do not have to invent names for common industry concepts. You can extend it with fields specific to your organization.
Each catalog entry records the standard, the source reference, and a stability marker. Revisions are published through the same catalog your applications and policies already read.
No. Your organization and its advisers decide which standards and requirements apply, and whether the complete system meets them.
See the vocabulary in your industry
Open an industry catalog, or review how each role reads the same decision history.