Exact bytes and commitment field scope
Reproduce the digest without adding fields that were never committed.
Retain original identities, failed checks and version relationships so a declared record can be inspected again.
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.
Stable IDs, first versions, amendment links and terminal states permit a complete-period review.
Declare gross/net costs, fill convention and return aggregation. Another reviewer should be able to follow the same ledger without filling gaps by assumption.
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.
An original-ID list and a proof-to-ID map make coverage inspectable. The packet's equal-count discrepancy repeats S002 and omits S007. Checking totals alone misses both. The checker lists missing, duplicated and unexpected originals before exposing exact fraction pairs. Those pairs remain declared-state diagnostics, not independently tested provider coverage.
Retain unsuccessful operations, pending receipts, unperformed checks, source versions and inaccessible originals. A corrected packet receives a new identity rather than overwriting the discrepancy. Amendment links need retained parents and no cycles. The archive-export guide shows how to keep originals and derivatives distinct without redistributing private documents unlawfully or manufacturing a complete account ledger.
Freeze eight originals before counting proof files. The duplicate/missing packet retains eight record rows yet repeats S002 and omits S007. The missing original stays in the denominator, the repeated row is not selected for convenience, and ratios remain null until the membership problem is resolved. Equal totals therefore do not justify a complete-period label.
The orphan amendment points to S003-v0, which is not retained. Record the parent request rather than attaching the amendment to whichever visible version looks similar. A corrected packet and the original discrepancy should receive separate identities. The base is a teaching reference, not a reconstruction of an actual absent provider file.
A genuinely re-checkable record would need authentic originals, exact proof attachments, performed checks and lawful access for another reviewer. The browser workbench can preserve those questions but does not perform the operations. Keep delivery and economic accounting separate even after an identity map becomes internally consistent.