Back to the evidence view

SOURCE VERIFICATION / RELEASE REQUIREMENTS

How the evidence
should hold together

The full source-fidelity approach, in one place.

SEPARATE SOURCES, CONNECTED UNDERSTANDING

Make the connections and keep the evidence

Different formats and systems, brought into one traceable picture. Datasets Frontier is being built to connect the information you already hold while preserving its origin, version and context.

DocumentsThe original wordsDatasetsStructured recordsDatabasesThe systems you use
Datasets FrontierConnect · contextualise · trace
A traceable viewSource links, relationships,
changes and point-in-time context

01 / OUR RELEASE STANDARD

Quoted word for word, or marked as not verified

THE GUARANTEE WE REQUIRE

A clause is quoted only when its exact wording and original source can be verified.

The first page or clause reference shown must resolve to the requested code or standard, the correct edition and the precise source location. A plausible match is not enough.

If that match cannot be established, the result must be marked Not verified. Missing words must never be reconstructed from memory or silently filled in by AI.

This is our product release requirement. The connected retrieval service must demonstrate it before a result can carry a verified label.

CLEARER PRESENTATION, UNCHANGED EVIDENCE

A modern layout that keeps the original meaning

A clearer interface must never become a different record. Source quotations, interpretation and proposed changes belong in separate, clearly labelled layers.

01

Source text

Exact wording, punctuation, units, qualifiers and referenced notes. Preserve the original page alongside the modern view.

VERBATIM
02

Explanation and analysis

Clearly labelled interpretation, linked to the evidence it relies on. Never presented as the source’s own words.

DISTINCT
03

Changes and proposals

Show what changed, where it changed and the documented reason. Proposed wording stays separate from published requirements.

TRACEABLE

02 / THE EVIDENCE TRAIL

Every layer leads back to the original

Our verification design follows the complete path from source identity to the words displayed. An OCR score or a confident answer cannot substitute for checking the source.

  1. 01

    Identify

    Match the document, publisher, code, edition, jurisdiction and relevant date.

    THE RIGHT RECORD
  2. 02

    Preserve

    Keep the original file and page image, with a stable file identity and provenance.

    THE ORIGINAL EVIDENCE
  3. 03

    Compare

    Check extracted words, tables, symbols, units and footnotes against that source.

    EXACT SOURCE FIDELITY
  4. 04

    Reconcile

    Check edition changes, cross-references and discrepancies across verification layers.

    VISIBLE DIFFERENCES
  5. 05

    Deliver

    Present the quote with its source link, clause, page, edition and verification status.

    A REPRODUCIBLE TRAIL
Exact quotation and correct applicability are separate checks.

A source may be transcribed perfectly yet be the wrong edition for a particular place or date. Both must be resolved before presenting it as the applicable requirement.

03 / KNOW WHAT CHANGED

What changed, where, when and why

Keep historical wording and current wording connected without blending them together. A change should be inspectable, not buried inside a summary.

THE CHANGE RECORD STANDARD
What
Original and revised passages, shown side by side.
Where
Document, edition, clause and page for both versions.
When
Publication and effective dates, kept distinct.
Why
The cited amendment note or documented rationale.
Evidence
Links back to the originals and the verification record.

If the source does not explain why, say “Reason not documented”. Do not invent a rationale.

04 / KNOWLEDGE THAT WORKS WITH YOU

Works across industries and alongside your systems

Datasets Frontier is being built to connect standards, codes and technical evidence with the data-management tools organisations already use.

01

Understand a point in time

Find the relevant edition, trace changes and keep historical, current and proposed requirements distinct.

02

Improve the information

Organise records, identify gaps and duplicates, and modernise presentation while retaining original evidence.

03

Reduce the admin load

Connect systems, improve workflows and automate repetitive administration with traceable results.

Industry coverage, source verification and software integrations are developed and validated individually. This page describes the required behaviour, the product direction and the release standard. It does not establish that the connected retrieval service has passed these checks, and it is not a claim of universal coverage already delivered.