| Always Approved State | — | CONFLICT — kept, not resolved (Open Items Register territory). Reading A (this corpus, Clarity Engine Glossary): a binary flag — CURRENTLY_ACHIEVABLE (>=1 program qualifies at confidence >= 0.70) vs. NOT_CURRENTLY_ACHIEVABLE. Reading B (PRD V7 #18, "Always-Approved (no denial state)"): a named three-state outcome — Qualified / Near-Miss / Pathway-Required — never a denial; Near-Miss and Pathway-Required disclose the exact gap and what would close it, in the same session. V7's two-way split of "not currently achievable" into Near-Miss vs. Pathway-Required has no defined mapping back to the glossary's single NOT_CURRENTLY_ACHIEVABLE value — that gap is the substance of the conflict. See also qualification-status (same conflict, program-level enum) and always-approved-tier / always-approved-statement (a related-but-distinct tiering lens, not itself in conflict). - approval-confidence
|
| Qualification Status | — | CONFLICT — kept, not resolved (Open Items Register territory). Reading A (this corpus, Clarity Engine Glossary): qualification resolves to one of 11 raw enum values, four of them INELIGIBLE_* (INELIGIBLE_DTI / LTV / CREDIT / WAITING_PERIOD) — explicit denial-shaped outcomes. Reading B (PRD V7 #18, "Always-Approved (no denial state)"): every verified qualification resolves to exactly one of three named states — Qualified / Near-Miss / Pathway-Required — and never a denial ("a not now"); Near-Miss and Pathway-Required disclose the exact gap and what would close it, in the same session. V7 doesn't say how, or whether, the glossary's INELIGIBLE_* values map onto Near-Miss vs. Pathway-Required — that undefined mapping is the substance of the conflict.
|