Exact bytes and commitment field scope
Reproduce the digest without adding fields that were never committed.
Separate byte identity, attestation, chronology, complete population and execution. A success in one layer is not a success in every layer.
Verification methods and user-led checklists. No provider has been certified by this site; declared coverage counts are not independently checked.
Separate byte identity, attestation, chronology, complete population and execution. A success in one layer is not a success in every layer.
Keep original files and a verifier transcript. Browser fixtures establish software behaviour only, not the validity of a proprietary trade history.
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.
Trace content, digest, receipt, trusted time and population coverage as separate checks instead of treating a proof badge as a complete audit.
Separate a file commitment, complete timestamp attestation, record coverage and executable trade evidence. A successful hash check establishes only its stated object.
Use an original roster and separate record rows. Equal totals can hide one repeated ID and one absent original. The packet demonstrates that case with eight rows, duplicate S002 and missing S007. A mismatched identity map does not get a quietly repaired denominator. The checker lists discrepancies and leaves coverage ratios null until the declared rows and parent graph reconcile.
Declared_pass, pending, declared_fail, unperformed and missing are states entered into a teaching or user record. The checker validates their schema consistency but does not open an .ots proof or verify a chain. Actual review completion needs genuine retained inputs and an independent transcript. Software assertions, responsive screenshots and cloud readbacks verify the release, not a trading strategy or provider history.