manifest.json
Input identifiers, release/rule provenance and the bounded claim boundary.
Download sampleDownloadable evidence-pack walkthrough
Inspect the shape of the handoff before you share a corpus.
These files use a fictional implementation scenario to show the evidence structure. They are not a customer case study, certification, PA acceptance result, production run or measured outcome.
Fictional scenario only
The downloadable pack models three synthetic structured invoices with an illustrative mapping gap, profile review item and re-test state. Every sample labels itself synthetic so it cannot be confused with customer evidence.
findings.csv
Normalised findings for filtering by source, rule, severity and business term.
Download samplecoverage.csv
Observed term coverage in the fictional corpus; never converted into a fake compliance score.
Download samplemapping-gaps.csv
Fictional source-to-business-term mapping gaps/conflicts.
Download samplereview.json
Explicit review/remediation state for findings that require a human decision.
Download samplesources.json
Public source provenance used to illustrate the evidence shape.
Download sampleWhat a re-test is meant to preserve
The starting state should remain visible. A bounded re-test compares resolved, new and unchanged findings instead of replacing the first report with a cleaner-looking second one.
Resolved
A fictional mapping issue no longer appears after the example correction.
Unchanged
A fictional profile review item remains visible.
New
A newly introduced finding would remain visible rather than hidden by the remediation narrative.
If the evidence shape fits the gap
Use the smallest paid corpus scope.
€490 covers one source / up to 100 representative invoices. The €1,500 integrator scope covers up to three sources / 300 invoices total with consolidated comparison and two bounded re-tests.