# issue
This home names every way one recipe can be refused and states, once, how each refusal reads, what it observed, and the one repair it offers.
The declarations hold the issue roster, the two exact-function seats that share one signature refusal, and the refusal carrier that pairs an issue with the captured token it points at.
The nucleus is the one road that builds a carrier and the readers that hand its issue and token back.
The contracts classify every issue exhaustively, so a new issue cannot be added without saying what it observed and how it is repaired, and they project the carrier as a diagnostic under the recipe family.
The capture and account roads build refusals here; nothing here reads a recipe or decides one.