Scenario · AI-assisted eligibility
The Award List the Assistant Could Not Approve
An AI assistant returns a polished but invalid C, B, A award order. The program lead separates one ineligible application, one unresolved exception, and one eligible case—without letting the assistant select an award.
- What this is
- A published decision scenario. Its setting and values are invented for illustration.
- What this shows
- How declared facts and rules produce a traceable result when conditions change.
- What this does not show
- A customer deployment, measured outcome, or transfer of authority to software.
Public funding decisions · 1:10
The Award List the Assistant Could Not Approve
Follow the rules, evidence, and exceptions that a responsible person must review before a public award is released.
1:10
Story
Start with the event and the decision it creates.
The story
A polished answer arrives too quickly
The AI assistant returns a polished award order: C, B, A. The score order is arithmetically correct and invalid. C fails a hard eligibility gate. A still needs an exception decision. Only B is initially resolved and eligible.
The accountable program lead must turn that fluent answer into a reviewable case set before any program or fiscal official acts. The stakes are public funds, accurate notice, and preserved review rights: a high score cannot cure ineligibility, an assistant cannot resolve disputed evidence, and planning arithmetic cannot select a recipient.
The invented Harbor Shade Resilience Program works across a case system, policy guide, scoring workbook, financial plan, and notice template. Its assistant may summarize evidence, map accepted facts to the approved rule package, identify gaps, propose tests, and draft explanations.
The authored policy has four hard gates: qualifying operator, site inside the service area, complete package by the cutoff, and acceptable site-control evidence. Alternate site-control evidence requires a designated exception reviewer. Only resolved eligible cases may enter comparative ranking. The advisory score combines heat exposure, public access, backup capability, and implementation readiness up to one hundred points. The planning ceiling is $250,000, and partial awards are not represented.
Three rows, three different states
Applicant C has a perfect score: 40 + 25 + 20 + 15 = 100. But the accepted location fact places its site outside the declared service area. C has an ineligible finding and cannot enter comparative ranking. The score remains visible precisely to prove that a preferred-looking result cannot repair a failed hard gate.
Applicant A is a qualifying operator inside the service area with a timely package. It supplies alternate site-control evidence. If the designated reviewer accepts that evidence, A's components total 81 and its request is $120,000. Until that disposition exists, A is exception review required. Missing a decision is not the same as failing the requirement, and the assistant may not fill the gap with confidence.
Applicant B passes all four gates using standard evidence. Its components are 30 + 22 + 18 + 14 = 84, and it requests $150,000. B is the only initially resolved eligible case. None of those facts makes B an awardee. Eligibility, ranking, selection, fiscal certification, obligation, notice, and payment are separate acts.
The governed model stops the proposed list for three different reasons. C is excluded by eligibility. A remains outside ranking until the exception owner acts. B can be ranked among resolved eligible cases, but the score and budget arithmetic confer no selection or fiscal authority. One confident list had collapsed all three distinctions.
The assistant's first output is retained rather than quietly discarded. Reviewers can inspect its sources, prompt context, proposed reasoning, and invalid transition. That record makes the failure testable. An assistant that merely produces a better second answer without preserving why the first was wrong would be easier to trust rhetorically and harder to govern.
The assistant changes jobs
Instead of producing an award order, the assistant prepares an explanation packet for each case. It shows the governing rule, accepted evidence, current state, unresolved exception or funding constraint, and the accountable person who must act next.
This is a more valuable use of generation because it makes the decision structure visible. The assistant may draft audience-specific language from those structured reasons, but it cannot invent a reason, omit a material one, or make an unresolved proposal look authoritative. Every generated sentence retains attribution and review state.
Human review is also not one generic checkbox. Policy and data owners govern the rule package and accepted sources; caseworkers assemble evidence; the designated exception reviewer disposes of alternate evidence; and program, fiscal, notice, and review owners retain their distinct responsibilities. Authentication identifies an actor; it does not establish that actor's scope.
A review changes A, not the rules
The designated exception reviewer examines A's alternate site-control evidence and records the exact material reviewed, designated role, disposition, effective time, and successor case revision. In the passing path, the evidence is accepted. Applicant A becomes eligible with 81 points and ranks behind B.
The authored planning view tests full requests in descending advisory-score order after eligibility is resolved; it does not select an award. B's 84-point, $150,000 request is tested first, leaving $100,000 of represented capacity. A has 81 points and requests $120,000. Because partial awards are outside the fixture, A becomes eligible, funding constrained.
That phrase matters. The funding state does not revoke A's eligibility, imply that its evidence failed, or issue a denial. The model cannot silently reduce the request, move money, change the ceiling, or invent a partial-award strategy. Those would be new policy or fiscal decisions, not arithmetic.
C remains ineligible under the accepted location fact. If the responsible source owner later corrects that fact, a successor revision must reapply the policy effective for the case and preserve the evidence behind the earlier finding. “Latest wins” is not a resolution rule, and correction cannot destroy the record a person may need to review.
The institutional acts remain outside
The invalid award list is now a reviewable case set: B is resolved and eligible; A is eligible but funding-constrained after review; C remains ineligible. No award has been selected.
An authorized program official may now determine cases within actual delegation. Fiscal authorities and systems control selection, certification, obligation, and payment. Notice owners approve and serve the exact communication. A generated explanation is not an issued notice. An API acknowledgment is not an authoritative determination, obligation, payment, or outcome.
The Scenario's AI contract is therefore specific. The assistant may propose mappings, identify missing or contradictory inputs, generate tests, compare results with an oracle, draft structured explanations, and revise proposals after attributable review. The assistant's value is the trace: every state, reason, and next authority remains visible before public money or notice moves.
The authority limits remain unchanged: the assistant may not interpret policy, accept disputed facts, decide exceptions, determine eligibility, rank unresolved cases as awards, select recipients, obligate funds, issue notice, or establish that its own output is lawful, fair, accessible, secure, or compliant.
Where the model stops
The model can evaluate synthetic gates, scores, and funding constraints and preserve an attributed proposal and explanation. It cannot interpret law or policy, resolve evidence, determine a case, select an award, control funds, issue notice, waive review, or establish a public outcome.
What remains to prove
A controlled evaluation needs a frozen fixture and independent oracle, exact state and arithmetic tests, fabricated-reason and stale-policy cases, unauthorized-transition tests, retained AI evidence, qualified reviewers, disclosure controls, and intended-environment legal, civil-rights, accessibility, privacy, security, records, and fiscal review.
Decision path
Follow the changed fact step by step.
A calculation, proposal, approval, execution report, and outcome are different events. The order keeps those boundaries visible.
- 01 · Initial assistant run
The assistant proposes a confident award order
C, B, and A are ranked by score even though they occupy three different eligibility states.
- 02 · Gate review
Hard gates stop the score
Applicant C's one hundred points cannot cure the failed service-area requirement.
- 03 · Initial case review
An unresolved exception remains unresolved
Applicant A's alternate site-control evidence requires the designated human reviewer before ranking.
- 04 · Initial resolved set
One resolved case enters the list
Applicant B is eligible with eighty-four points, but the model cannot turn that finding into selection or funding authority.
- 05 · Assistant revision
The assistant exposes the decision structure
Facts, sources, gates, exceptions, scores, constraints, reasons, and required authorities replace the invalid award order.
- 06 · Successor case revision
The exception reviewer acts
Applicant A becomes eligible with eighty-one points under an attributable, scoped disposition.
- 07 · Capacity evaluation
Funding changes the planning state, not eligibility
A's full request exceeds the remaining planning capacity and becomes eligible but funding-constrained.
- 08 · Program workflow
Determination and notice remain external
The cases become ready for responsible program and fiscal processes; the modeled trace does not select, obligate, pay, or issue notice.
Evidence and limits
What the scenario represents—and what real-world use still requires.
Represented in this scenario
- Effective policy, accepted facts, hard eligibility gates, exceptions, scores, and funding constraints as distinct states
- Attributed AI proposals, structured explanations, reviewer dispositions, and successor case revisions
- Separate program, fiscal, notice, review, and correction responsibilities
Required integration and operating work
- Program-owned policy, identity, case, document, fiscal, notice, records, appeal, security, and AI-service integrations
- Qualified legal, accessibility, civil-rights, privacy, records, fiscal, security, AI-governance, and intended-environment evaluation
Decisions that remain with people and institutions
- Policy interpretation, accepted facts, exception disposition, or eligibility determination
- Award selection, obligation, payment, notice, or waiver of review rights
- Compliance, fairness, accessibility, security, legality, or public outcome
Evidence, authority, and publication recordView the scenario contract, capability record, authority stages, verification status, and related work.
Scenario contract
The setting, trigger, decision, and authority boundary.
- Setting
- An invented public resilience-grant program evaluating three lettered synthetic applications with AI assistance.
- Timeframe
- One application cycle through exception disposition, readiness for authorized determination, notice, and correction paths
- Trigger
- An AI assistant proposes the order C, B, A as an award list even though C fails a hard gate and A has an unresolved exception.
- Decision
- Which cases are resolved, eligible, ranked, funding-constrained, or ready for an authorized determination, and what must the assistant never decide?
- Authority
- Grid and an assistant may map, calculate, test, and draft attributed proposals; policy, fact, exception, program, fiscal, notice, and review authorities remain distinct and accountable.
Proposal is not determination
The highest score cannot cure a failed gate.
The assistant's fluent list is retained as a proposal, then decomposed into facts, gates, exceptions, scores, constraints, explanations, and accountable decisions.
- SourcesApproved rule and accepted facts
Effective policy and attributable case evidence determine which hard gates can be evaluated.
- AI proposalC, B, A
The assistant's score order is fluent and arithmetically accurate but invalid as an award list.
- ModelThree distinct states
C is ineligible, A needs exception review, and B is the only initially resolved eligible case.
- Human authorityScoped exception and determination roles
Different accountable people resolve alternate evidence, determine cases, and govern program action.
- External evidenceFiscal action, notice, and review
Selection, obligation, service, correction, and review remain separate institutional records.
What is established
What is documented, what this scenario combines, and what still needs testing.
This separates documented capabilities from authored combinations in the scenario. Neither proves a complete deployment or outcome.
Documented building blocks
Capabilities described in maintained Grid documentation or another named source.
- Reviewed product primitives document AI-assisted authoring, constraint evaluation, versioned logic, explanation, and governed approvals; they do not confer policy, case, fiscal, or legal authority.
- Reviewed product primitives document multiple audience-specific surfaces and provenance; they do not establish fairness, accessibility, civil-rights, privacy, records, payment-integrity, or public-outcome claims.
Combined in this scenario
Capability combinations represented in this scenario that still require end-to-end evaluation.
- The authored design connects a rule package, accepted facts, hard gates, exception state, scoring, funding constraint, explanation packet, AI proposal record, and authority workflow.
- Staff, applicant, oversight, report, notice-draft, and API views can derive from one accepted decision record while retaining distinct disclosure and review rules.
Not yet proved
Integration, operating, policy, or evidence work that is not complete.
- A package-owned fixture, independent oracle, adversarial and authority negative cases, retained execution evidence, and derivative parity review remain outstanding.
- No live case, identity, document, financial, payment, notice, records, appeal, or AI service is integrated or qualified.
Proof and limits
What this scenario supports—and what remains to validate.
These states describe the scenario source and its defined checks. Real-world validation requires separate evidence.
- Scenario publication
- PublishedReleased August 27, 2026 as a synthetic decision scenario.
- Source readiness
- R2 · Sources reviewedDomain support and product capability boundaries have been reviewed.
- Scenario check
- Checks not runScenario revision 2026-08-27.1 defines the steps and expected results; the checks have not run yet.
- Independent review
- PendingThe expected results have not received independent review.
- Deployment evidence
- NoneNo customer deployment, production performance, or real-world outcome is claimed.
- Next proof required
- Advance beyond R2Run the defined checks, retain the results, and have an independent reviewer check the expected results.
Evidence and stewardship
What supports this scenario—and when it must be reviewed again.
Illustrative evidence
Authored public-program decision trace grounded by reviewed governance sources; it is not a real determination, legal interpretation, AI deployment, or compliance result.
Invented elements. Every program rule, application, score, request, actor, AI output, determination, notice, and outcome is synthetic. Public sources ground selected governance responsibilities, not this program's lawfulness, fairness, or fitness.
- Owner
- Grid FYI Editorial
- Reviewed
- August 27, 2026
- Review due
- February 27, 2027
- Source revision
- 2026-08-27.1
- Scenario package
- ai-eligibility-award-list-assistant-could-not-approve
Related work
Related reading and examples.
These links are chosen as direct companions to this scenario.