Stores an account's fraud rule customisations, one JSON document per rule, in a fraud directory in the account's queries repository. Rules shipped by apps are instantiated on demand from their providers and are never written here, exactly as app-provided index queries and anomaly detectors are, so this store only holds what an account has changed or added: an override is a partial document naming only the fields the account altered, so that retuning one weight does not freeze the rule out of later improvements to the default's logic, title and evidence, while a custom rule is a complete document with no default behind it. Deleting an override restores the default, which is why a disabled default is stored as enabled: false rather than by removing anything. Fraud policy is kept in the queries repository rather than blob storage, alongside index queries, metrics, reports and agent definitions, because that repository is version controlled per branch and a security policy benefits from being able to see who changed a threshold and when.