EXPLANATIONS OPTIMIZED FOR HUMAN READABILITY 

​

01 Control – General Control Policies

List of Policies

• Change disclosure expectations

• Execution and reproducibility responsibility

• Exclusion of OS- and tool-specific instructions

• Scope of builder responsibility vs. verifier responsibility

• Treatment of appendices (human-only, non-authoritative)

 

02 Control – Data Integrity Control

Some analyses and datasets are pulled into or stored in Excel.

Excel data is inherently fragile and can be easily modified, deleted, or overwritten.

To detect unintended changes in Excel, the builder designed this data integrity control.

Control Steps

• Builder defines explicit data boundaries (cell, row, column, or defined range).

• A sha-256 computation is applied to the bounded data.

• The resulting computation value serves as a deterministic data “total.”

• A static compuation value is stored as the control reference.

• A live sha-256 computation is performed on the same bounded data.

• The static and live hash values are compared using a defined formula.

• If the underlying data changes, the live hash value will necessarily change.

• A difference between static and live hash values signals a detected change.

• Builder reviews control results to identify and reconcile unintended data changes.