Integrity

The rules behind the result.

Heist's usefulness depends on whether users can trust how a result was produced. These commitments apply to product alerts, rankings, explanations, and the public Record.

Commitments

Facts first. Context visible. You decide.

Evidence is required

Every material claim points to public evidence or a documented attribution source. Transaction claims include the relevant reference.

Detection is deterministic

Versioned code evaluates published event rules. A language model does not set critical severity or authorize a transaction.

Payment cannot change a result

No paid placement. Payment cannot increase confidence, reduce severity, hide evidence, or suppress a correction.

Conflicts are disclosed

Relevant Heist, partner, affiliate, and employee interests are disclosed. Employees are restricted from trading around material alerts.

Corrections do not erase history

When an explanation changes or an error is corrected, the earlier record remains visible with its timestamp and reason.

Alert volume is constrained

Severity and notification limits are designed around relevance, not engagement. Quiet periods remain quiet.

Users approve every trade

An alert never becomes an automatic transaction. Every future trade requires a fresh review and explicit approval.

Limits remain visible

Heist publishes coverage, freshness, outages, known misses, and relevant methodology changes.