Exact bytes and commitment field scope
Reproduce the digest without adding fields that were never committed.
Define inspected objects, performed checks and source status before making a bounded verification claim.
A practical method note with explicit evidence limits.
Verification methods and user-led checklists. No provider has been certified by this site; declared coverage counts are not independently checked.
The site title does not certify its directory. A conclusion needs a reviewer identity, inspected population and retained artifacts.
A mismatch, pending receipt and missing original each have their own meaning. Keep them visible rather than averaging them into a star score.
Documentation establishes the stated mechanism, not tested trading performance. Checked 9 October 2026; a later version can differ.
Reproduce the digest without adding fields that were never committed.
Keep calendar acceptance, completed proof and chronology interpretation separate.
Reconcile identities and status rules before interpreting a proof percentage.
State the exact offer, version, original-ID population, object, operation and review date. Distinguish the source's assertion from the reviewer's performed check. For a file comparison, retain both bytes and expected digest origin. For an attestation, retain the real proof and verifier transcript. For a delivery or fill claim, supply the separate access and broker records. A single green label cannot meaningfully replace all those objects.
Publish unresolved IDs, repeated identities and unavailable parents. Keep old releases when a denominator or representation changes. A late correction should not rewrite the original instruction as though its improved fields were always present. A formal assurance opinion needs an actual engagement and scope; a completed checklist is not that opinion. The practice packet demonstrates record rules with fictional labels and leaves real-world validation absent.