HEART ai.answer-rejected H-07009
Brain answer rejected. A brain answer was refused: unsigned, wrongly signed, for another request, or outside the lease.
| Code | HEART ai.answer-rejected; inside a message "code": "ai.answer-rejected" |
|---|---|
| H-number | H-07009: area 07, code 009 |
| Area | ai: AI providers, models, budgets |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Products with a brain lease |
Likely causes
- An answer that is not signed, or signed with the wrong key.
- An answer meant for another request, or an old one sent again.
- An answer outside what the lease allows.
- Someone trying to send the product false answers.
How to fix or prevent it
- Check the signing keys on both sides.
- Check the clock on both sides.
- If answers keep failing, treat it as possible tampering.
What the HEART does by itself
It refuses the answer and acts on none of it, records why, and raises a warning. It does not lower its checks.
When to call service
If it keeps happening with correct keys and clocks: it may be an attack.
Related codes
ai.output-rejectedH-07006: AI output rejectedsecurity.anomalyH-11007: Security anomalyai.brain-revokedH-07008: Brain revoked
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)