Update to dVeracity

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.app.json →

.codex-plugin/plugin.json →

.mcp.json →

assets/icon-dark.png →

assets/icon.png →

assets/logo-dark.png →

assets/logo.png →

.codex-plugin/plugin.json

− removed · + added

--- before
+++ after
@@ -1,9 +1,8 @@
 {
-  "apps": "./.app.json",
   "author": {
     "name": "dVeracity"
   },
-  "description": "Check data against the standards, canonical models and policies it claims to conform to, and get back a graded, machine-readable result that says what was checked, what was not, and why.\n\ndVeracity is a verification engine for regulated data. An agent can read a canonical data model at design time (entities, sectors, semantic codes and policy guardrails), validate a payload against a named standard before submitting it, look up approved regulatory compliance policies with their rules and provenance, and query verified datasets in natural language. Every result states its model version and the checks it ran, so it can be handed to a reviewer rather than pasted into a chat.\n\nThe first standard onboarded is Open Footprint (The Open Group), with O-DEF semantic codes, PACT product-footprint validation and verified emissions and methane datasets. The engine is domain-neutral; further standards are onboarded through the same path.\n\nEighteen tools, all read-only. Model, sector, semantic-code and standards-catalogue tools are free of charge. Natural-language queries and validation are metered per call in credits, with machine-readable HTTP 402 payment semantics: when an account runs out, the tool tells the agent to ask its human operator to top up, and never retries. Compliance-policy tools are available on paid plans.\n\nAuthentication is OAuth 2.1 with dynamic client registration; a human approves access on dVeracity's consent screen. Optional GLEIF-rooted vLEI verified-agent identity is supported for organisations that need attributable agents.\n\nBuilt for compliance, ESG and reporting teams, standards implementers, and anyone whose data has to be checked before it is trusted.",
+  "description": "Check data against the standards, canonical models and policies it claims to conform to, and get back a graded, machine-readable result that says what was checked, what was not, and why.\n\ndVeracity is a verification engine for regulated data. An agent can read a canonical data model at design time (entities, sectors, semantic codes and policy guardrails), validate a payload against a named standard before submitting it, look up approved regulatory compliance policies with their rules and provenance, and query verified datasets in natural language. Every result states its model version and the checks it ran, so it can be handed to a reviewer rather than pasted into a chat.\n\nThe first standard onboarded is Open Footprint (The Open Group), with O-DEF semantic codes, PACT product-footprint validation and verified emissions and methane datasets. The engine is domain-neutral; further standards are onboarded through the same path.\n\nEighteen tools, all read-only. Model, sector, semantic-code and standards-catalogue tools answer from a version-controlled snapshot of the standard. Natural-language queries, validation and compliance-policy lookups run against the caller's dVeracity account; when a tool cannot run for the current account it says so in a machine-readable way and tells the agent to ask its human operator, and never retries on its own.\n\nAuthentication is OAuth 2.1 with dynamic client registration; a human approves access on dVeracity's consent screen. Optional GLEIF-rooted vLEI verified-agent identity is supported for organisations that need attributable agents.\n\nBuilt for compliance, ESG and reporting teams, standards implementers, and anyone whose data has to be checked before it is trusted.",
   "interface": {
     "capabilities": [],
     "category": "Business & Operations",
@@ -12,13 +11,26 @@
     ],
     "developerName": "dVeracity",
     "displayName": "dVeracity",
-    "longDescription": "Check data against the standards, canonical models and policies it claims to conform to, and get back a graded, machine-readable result that says what was checked, what was not, and why.\n\ndVeracity is a verification engine for regulated data. An agent can read a canonical data model at design time (entities, sectors, semantic codes and policy guardrails), validate a payload against a named standard before submitting it, look up approved regulatory compliance policies with their rules and provenance, and query verified datasets in natural language. Every result states its model version and the checks it ran, so it can be handed to a reviewer rather than pasted into a chat.\n\nThe first standard onboarded is Open Footprint (The Open Group), with O-DEF semantic codes, PACT product-footprint validation and verified emissions and methane datasets. The engine is domain-neutral; further standards are onboarded through the same path.\n\nEighteen tools, all read-only. Model, sector, semantic-code and standards-catalogue tools are free of charge. Natural-language queries and validation are metered per call in credits, with machine-readable HTTP 402 payment semantics: when an account runs out, the tool tells the agent to ask its human operator to top up, and never retries. Compliance-policy tools are available on paid plans.\n\nAuthentication is OAuth 2.1 with dynamic client registration; a human approves access on dVeracity's consent screen. Optional GLEIF-rooted vLEI verified-agent identity is supported for organisations that need attributable agents.\n\nBuilt for compliance, ESG and reporting teams, standards implementers, and anyone whose data has to be checked before it is trusted.",
+    "longDescription": "Check data against the standards, canonical models and policies it claims to conform to, and get back a graded, machine-readable result that says what was checked, what was not, and why.\n\ndVeracity is a verification engine for regulated data. An agent can read a canonical data model at design time (entities, sectors, semantic codes and policy guardrails), validate a payload against a named standard before submitting it, look up approved regulatory compliance policies with their rules and provenance, and query verified datasets in natural language. Every result states its model version and the checks it ran, so it can be handed to a reviewer rather than pasted into a chat.\n\nThe first standard onboarded is Open Footprint (The Open Group), with O-DEF semantic codes, PACT product-footprint validation and verified emissions and methane datasets. The engine is domain-neutral; further standards are onboarded through the same path.\n\nEighteen tools, all read-only. Model, sector, semantic-code and standards-catalogue tools answer from a version-controlled snapshot of the standard. Natural-language queries, validation and compliance-policy lookups run against the caller's dVeracity account; when a tool cannot run for the current account it says so in a machine-readable way and tells the agent to ask its human operator, and never retries on its own.\n\nAuthentication is OAuth 2.1 with dynamic client registration; a human approves access on dVeracity's consent screen. Optional GLEIF-rooted vLEI verified-agent identity is supported for organisations that need attributable agents.\n\nBuilt for compliance, ESG and reporting teams, standards implementers, and anyone whose data has to be checked before it is trusted.",
     "privacyPolicyURL": "https://dveracity.com/privacy",
     "shortDescription": "Verify data against standards",
     "supportURL": "https://dveracity.com/support",
     "termsOfServiceURL": "https://dveracity.com/terms",
-    "websiteURL": "https://dveracity.com"
+    "websiteURL": "https://dveracity.com",
+    "logo": "./assets/logo.png",
+    "logoDark": "./assets/logo-dark.png",
+    "composerIcon": "./assets/icon.png",
+    "composerIconDark": "./assets/icon-dark.png"
   },
   "name": "app-6ab0b9e4cd088191a8c953f9d6bd50fd",
-  "version": "2.0.2"
-}
\ No newline at end of file
+  "version": "2.0.4",
+  "extensions": {
+    "com.openai": {
+      "publication": {
+        "release_notes": "Icon updated to the dVeracity mark (light and dark, plus composer icons) and the listing description revised to remove pricing language per directory guidelines. No functional change: same 18 tools, same MCP endpoint, same OAuth configuration."
+      }
+    }
+  },
+  "mcpServers": "./.mcp.json",
+  "apps": "./.app.json"
+}