Skip to main content

How to Read the Fidelity Certificate

Each analysis checks a sample of the claims made in your documentation against the source Salesforce metadata, while that metadata is still available. The result is the fidelity certificate. It tells you what was verified, how, and — just as important — what was not.

Open the certificate​

  1. In the portal's left navigation, click Coverage and fidelity (group Quality).
  2. Use the three tabs at the top:
    • Coverage — what the analysis took into account for this version;
    • Verification — the fidelity certificate itself;
    • Versions — the history of published versions.
  3. Click Verification.

The certificate belongs to the documentation version you are reading. To check another version, switch version first.

If the page says no certificate is available, it will be produced by the next analysis. If the Verification tab is missing, the certificate is not enabled for your organization.

Read the figures​

  • Verification status — for each verification mode, whether it was Measured, Not measured, an Incomplete verification, and why.
  • Artefacts audited, out of the number sampled.
  • Claims assessed as consistent and Reported discrepancies — the verdicts recorded during the analysis.
There is no single "reliability" score

The certificate deliberately does not show one overall score: checking sources does not establish that the whole documentation is complete and correct from a business point of view. Each score covers only the checks that returned a result, on the stated sample.

Understand the two verification modes​

Under By verification mode:

  • Verified without AI — claims checked directly against your org's model (fields, permissions, rules…), on the number of artefacts shown.
  • Reviewed by a judge model — narrative text reviewed by an AI model against the source.

Each mode has its own score out of 100 and its own sample size. If Incomplete sample appears on the AI-reviewed mode, some of its checks did not return a result: its score is an average over those that did.

Check the scope​

  • Verification scope lists what the score does not reach: objects for which no documentation was produced (they cannot lower the score, because they appear in no verification), and content families that no verifier samples.
  • Scope and sampling gives, per type of content, the population emitted, the number sampled and audited, the number with a divergence and whether the per-type cap was reached. View scan scope opens the Coverage view.

Look at individual claims​

The list at the bottom shows each audited item. Organize it by Verdict, Verification mode or Component type, or use Search for a component. Each claim carries a verdict — Verified, Divergence, Partial or Not verifiable — and Show source excerpt displays the metadata it was checked against, quoted as is.

A divergence is shown in full transparency: it concerns one audited excerpt and does not mean the whole population of that type is wrong.

Re-check it yourself​

At the bottom of the certificate, click Verify this document:

  1. Choose a Sample size (10, 15 or 25 rules).
  2. Draw a random sample. The Seed makes the draw replayable: keep it to replay the same sample, or draw again with a fresh one.
  3. For each rule, compare What the documentation says with the verbatim source, open the component with Open in Salesforce Setup if needed, and mark your verdict: Conform, Divergent or Could not verify.

Your marks stay in your browser; nothing is sent to aprity. If a component changed in your org since the analysis, a difference reflects freshness, not fidelity.