Audit evidence that never leaves the institution that produced it.
Galinstan is built to produce control testing and gap analysis evidence inside your own hardware boundary, with each finding citing where it came from.
A different standard is possible when the software runs inside the institution. The inputs never leave. The version that produced the result sits on the institution's own disk. Nothing is rewritten between the calculation and the report by a service neither party controls.
Galinstan's evidence is built around that: control testing and gap analysis against the US liquidity rules and the bank's own control framework, with the evidence for each finding citing where it came from, and with the model and method that produced it recorded beside it rather than described afterwards.
Because the calculation is deterministic, a model validator can re-perform it: same inputs, same parameters, same result. That is the evidence a validation file needs: conceptual soundness, outcomes analysis, and ongoing monitoring, documented in the bank's own model risk framework.