Each prompt below exists because a condition written down in advance holds in this dataset version. It is a reason to look, not a finding, a recommendation of business action, or evidence of a real-world condition.
Nothing here claims a cause. A rule states that a condition holds and shows the exported values that made it hold; why it holds is what the drill-through is for.
The queue is stateless. It is rebuilt from the data every time the export is regenerated, so it holds no history and carries no acknowledgement, assignment, completion or due date. Reloading this page reconstructs the same queue; nothing remembers what was clicked.
No language model, learned model or scoring heuristic takes any part in producing it. Every word of every prompt comes from a rule template and every number from an exported column, so any action can be recomputed by hand from files in the repository.
12 of 30 permanent rules are enabled. The other 18 are retained and switched off, each with the audited reason the project cannot evaluate it honestly — the evidence is absent, it exists only at a different grain, or the condition is one an earlier data-quality gate already prevents.
Every threshold this register owns is a project default for a fictional dealer group. None is an industry benchmark, an OEM standard, a best practice or a compliance requirement.