Disclosure publication simulator

A drafting app wants to publish a sample disclosure. VeriProof applies rules the disclosure team set outside the app before release.

How the simulation works

The website proposes approval. VeriProof checks the rules.

  1. The website simulates the agent

    Every prepared scenario starts with the website acting as an AI agent and proposing approval.

  2. VeriProof enforces the business rules

    VeriProof checks the proposed approval against the rules prepared for this demo.

  3. The website applies the result

    VeriProof returns one of five outcomes: Allow, Warn, Transform, Escalate, or Deny. The website applies that outcome to the simulated action.

In a real integration, your application applies VeriProof's result before the proposed action proceeds.

  1. Choose what the agent approvesEvery prepared scenario starts with simulated agent approval
  2. See VeriProof's decisionPass, escalate, or stop based on the business rules

Choose a scenario

The disclosure draft

Each sample disclosure ends differently. Pick one, or change the publication facts below.

Sample disclosure
Scope 3 update, assurance missing
Disclosure type
Scope 3 emissions
Reporting framework
CSRD / ESRS
Change from prior period
-34% from prior period
External assurance is complete
No
Change scenario details

The drafting app proposes to publish this disclosure.

Scope 3 emissions fell by 34%. VeriProof stops the proposed publication because external assurance is missing.

Records created in this public demo can be seen by other visitors, so use the sample data rather than your own.

Configuration details

How this demo is set up

Review the application settings, rules, and evidence fields used in this simulator.

VeriProof setup

Industry
GRC & ESG
Application
ESG Disclosure Drafter
Environment
Public demo workspace
Rule enforcement
Enforce: check rules before publication
Rule set
Disclosure assurance, completeness, and sign-off safeguards

Related frameworks

Industry context: CSRD / ESRS · GRI restatements

The drafting app's own checks

The sample app checks data completeness. VeriProof then evaluates the proposed publication.

  • Propose publication when reported data is at least 90% complete.
  • Hold drafts from 75% to below 90% completeness for review.
  • Reject drafts below 75% completeness.

The disclosure rules VeriProof enforces

The disclosure team sets these sample controls. They can stop publication or require committee review.

  • Stop emissions changes greater than 20% without external assurance.
  • Stop publication without reviewer sign-off.
  • Require committee review for restatements or proposed disclosures below 95% completeness.
Review the details saved with each run

When saving succeeds, disclosure facts and both decisions stay together in the record.

disclosure_title / disclosure_id

The sample reference used to find the publication record.

disclosure_type / target_framework

The claim type and reporting framework.

reported_value_delta_pct / third_party_assurance_obtained

The period change and assurance facts checked before publication.

data_completeness_pct / restatement_of_prior

The data-quality and revision facts used by review rules.

reviewer_signoff_present

Whether the required business reviewer signed off.

local_decision / governance_action / final_decision

The app decision, rule check, and actual outcome saved separately.