Skip to content

Proof

Inspect the evidence behind a funding decision.

Actual Valty interfaces use illustrative data to show the product. The separate fictional worked example shows how an estimate, assumptions, evidence lineage, confidence, freshness, and claim limits can be reviewed together. Neither is a customer outcome.

See the worked example

Illustrative control-evidence example

Follow one recovery gap from evidence to review.

Fictional record REC-EXAMPLE-01 shows the review logic for one payroll database. It is an illustrative workflow, not a screenshot, an executed Valty test or an observed customer outcome.

  1. Source recorded

    A backup configuration exists.

    The fictional record names one payroll database and a configuration snapshot showing backups enabled. It records source, scope and capture time; it is not a restoration test.

  2. Evidence gap open

    Recovery is still unverified.

    No restoration test artifact is supplied. The reviewer keeps that gap visible instead of treating an enabled setting as proof that the database can be recovered.

  3. Action proposed

    An owner prepares a controlled test.

    The proposed task identifies the system owner, isolated test scope, approval, recovery criteria and due date. No change or test is represented as executed.

  4. Verification pending

    Closure needs a separate result.

    The reviewer would need the executed test record, observed result, source and time, and a check against the agreed criteria. Until then, the gap remains open.

Evidence integrity answers whether a record is attributable and unchanged. Control effectiveness requires relevant validation; third-party acceptance is a separate decision. This example establishes none of those outcomes and assigns no loss-reduction credit.

The actual Valty interface below contains illustrative data and is separate from this fictional record. The financial worked example separately shows how a funding decision can retain its assumptions and claim limits.

Review control-validation scope →Use the renewal worksheet →
Proof Pack product surface
Proof PackActual Valty interface with illustrative data. This capture is independent of the separate fictional worked example and is not a generated report from it.Open full-size product view ↗

Inside the proof pack

Every number is tied to source evidence, confidence, freshness, and the audience receiving it.

  • Board report and IC / diligence memo builders
  • SOC 2 and ISO 27001 evidence packs
  • OSCAL 1.1.2 SSP, SAP, SAR, and POA&M package generation
  • Control and finding evidence chain with confidence and freshness
  • Evidence snapshot, serving model version, and public-prior citations
  • Reviewed-output replay and formula-node challenge provenance
  • Unsupported claims blocked before they reach any export
  • Export preview for board, IC, auditor, insurer, or assessor

Reproducible proof

A reviewer can recompute the number, challenge a node, and see what remains unsupported.

The Proof Pack carries more than a source list. It binds the displayed figure to an evidence snapshot, serving model version, public prior rows, and the publication state that controlled the export.

Snapshot

Evidence state is pinned at publication

A later source refresh cannot silently rewrite the basis of a previously reviewed figure.

Model card

The serving model version travels with the figure

Public prior rows cite study, year, sample, and license; dormant licensed sources cannot silently contribute.

Recompute

The printed P95 replays to the cent

A mismatch blocks the pack from claiming reviewed and writes the result into provenance.

Unsupported

Missing evidence never becomes a confident zero

Blocked claims and unsupported companies remain visible with the next evidence action needed to advance them.

Replay chain

Every reviewed figure keeps its replay state.
Replay matched
01SnapshotPinned
02ModelPinned
03ReplayMatched
04ReviewRecorded
Public example

This page shows the review grammar with static example data. Replay and node-level challenge operate inside entitled workspaces and reviewed exports.

Read the reproducibility method

Proof matrix

What you can safely share

See which claims are ready to share, which need access controls, and which stay blocked until the evidence is current.

ClaimSourceConfidenceFreshness
Board claimEBITDA bridge + evidence packModel-based, source-linkedReviewed before export
Audit claimControl catalog + proof cardEvidence-backedFreshness visible
Insurance claimRisk scenario + control proofDecision-support onlyRequires current source coverage
Blocked claimMissing or stale evidenceNot publishableRequires owner action