Truthound · All articles · 4/24
Evidence-led Truthound Core guidance on data contracts, check inputs and operational limits.
480 articles
A new capital-mobilization method needs a reporting transition ledger
Keep methodology changes separate from newly mobilized money.
One infrastructure loan does not put every energy and data-center asset at the same stage
Compare parallel and sequential delivery using the prerequisites of each asset.
A payment approval is not the money a merchant has received
Keep authorization, settlement and confirmed receipt separate in the merchant's transaction view.
Shared GPU access and a national data center need the same billing boundary
Compare a defined workload's total commitments, not just its advertised GPU-hour price.
Do not turn tourism pageviews and coupon redemptions into merchant sales
Testing a new app requires separating observable platform actions from transactions the platform cannot verify.
Do not apply merchant-only features to an individual credit applicant
Alternative-data features need an explicit population and missingness contract before their absence can be interpreted.
Align forecast issue time and valid time before power-aware AI workload shifting
A workload-placement comparison becomes misleading when power, price and compute inputs refer to incompatible time meanings.
Pin the replacement EDI layout before interpreting acknowledgements
A corrected instruction still requires separate treatment of layout versions and acknowledgement meanings.
Do not promote a standards proposal into a production data contract
Discussion, decision, release and implementation are different states in a standards change.
Do not erase historical X2P1 transactions when payment service values change
Preparing a transition means preserving historical meaning as well as considering a new category.
Start cross-border supply-chain interoperability with explicit contract versions
Exchanging a file and exchanging the same business meaning are different achievements; versions and traceability definitions need explicit agreement.
What evidence turns a staff AI prototype into an institution-operated service?
A successful demonstration and an operational handover require different decisions and shared evidence.
A UK data-transfer review is not an issued equivalence decision
A policy review and an operative decision are different states; a transfer inventory should preserve that distinction.
A secure research zone does not remove dataset reuse boundaries
Approval of a processing environment and permission for a particular dataset use require different evidence.
Require recipient authorization and approved-version evidence before a data export
An export manifest and a secure transfer process perform different controls; keep their evidence separate.
Reconcile downtime records and rescheduled appointments after a healthcare outage
Technical restoration and administrative reconciliation are different stages; preserve the meaning of appointment changes.
Keep patched systems distinct from systems using compensating safeguards
Different remediation states create different follow-up obligations; a completed flag should preserve the control type and evidence.
Do not turn a data-centre capacity condition into measured green-energy share
Capacity, metered energy and a supply commitment are different measures with different field boundaries.
Separate current compute supply evidence from 2030 demand forecasts
Current availability and long-term demand assumptions need different evidence records and different decision boundaries.
Give legal, procurement and finance teams the same evidence for emergency-contract payment exceptions
A date mismatch raises a shared review question; it does not establish fraud or illegality.
