Eligibility & Sanctions — Education & Aid
Eligibility and sanctions decisions that survive challenge months later.
No Stamp → No Ship for aid denials, eligibility removal, sanctions screening holds, and disbursement decisions.
Appeals, funders, auditors, banks, and oversight bodies judge what you can prove was authorised within scope at decision time — and whether reliance stops when conditions change.
- Gate high-impact actions by Status Link: not VALID → block or escalate (per programme rules)
- Proof that travels outside your perimeter: counterparties verify scope • expiry • signer • status by link
- Evidence Pack (IDA format): reusable across audits, appeals, and funder reviews
Fail-closed•Append-only•Scope-bounded
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
Why education & aid buyers are moving now
Appeals pressure, sanctions scrutiny, and funder due diligence are converging.
Appeals become authority disputes
"What was authorised then, under which criteria, and is it still valid now?" — appeals panels need portable evidence, not portal screenshots.
Policy drift silently invalidates approvals
Criteria, thresholds, and vendor/model changes happen mid-cycle. Prior eligibility decisions keep executing on stale assumptions.
Sanctions and payment controls create escalation risk
Bank de-risking, funder hold requirements, and sanctions screening create compliance escalation pressure that needs defensible records.
Screenshot-based evidence is fragile
Portal screenshots and exported PDFs don't carry status, scope, or expiry. They can't be verified independently and are expensive to reconstruct.
Cross-border programmes need portable proof
Funders, banks, oversight bodies, and partner organisations need verification without system access or VPN credentials.
Withdrawal must propagate instantly
When a decision is compromised or reversed, all relying parties need to see WITHDRAWN wherever they check — not "pending update."
Repeat investigations consume capacity
Rebuilding decision records for audits, appeals, and funder reviews drains compliance and casework teams repeatedly.
Good Proof provides scope-limited verification evidence and stop-rely semantics. It is not a certification.
What a Stamp proves (and what it doesn't)
Proves (within lane scope)
- Decision class + action (approve/deny/hold/release/remove/reinstate/sanctions hold/appeal outcome)
- Decision-time timestamp
- Signer/authority reference
- Scope boundaries + expiry/evidence window
- Policy/rule-pack identifier + version reference (lane-scoped)
- Validity state (VALID / NEEDS REFRESH / WITHDRAWN / NOT VERIFIED)
- Verification transcript + timestamps (minimal disclosure)
Does NOT prove
- Underlying truth of the case
- Outcome correctness or model correctness
- Certification or regulatory compliance
- Student/beneficiary PII, documents, or raw case notes by default
In disputes: Status Link = reliance state now. IDA Evidence Pack = fileable snapshot for decision-time record.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
Why this lane exists
In Education & Aid, disputes are authority + process defensibility disputes.
These decisions don't just change an account status — they change housing, food security, attendance, and a person's future. The failure mode is not "the system was wrong."
It's: "was it permitted, under what criteria/version, and should reliance continue now?" — without exporting half the system.
Good Proof converts high-impact decisioning into a contract-referenceable gate.
What gets stamped in Education & Aid
Examples of high-impact action classes (define per programme):
Eligibility & disbursement
- Eligibility approve/deny + reason class
- Disbursement hold/suspension/release decision
- Eligibility removal/disqualification + reinstatement decision
- Award amount changes, clawback/reclaim triggers (programme-scoped)
- Attendance/SAP/progress outcomes that affect funding access (education programmes)
Sanctions, fraud & restrictions
- Sanctions screening hold/release (financial sanctions lists)
- Diversion-risk / fraud flags that block payment or access (programme-scoped)
- Partner/beneficiary eligibility blocks tied to restricted geographies or lists (programme-scoped)
Appeals & exceptions
- Appeal outcomes + final review closure
- Exception grants / hardship overrides requiring duty-of-care evidence
Delegated authority
- Delegated approval scope + expiry windows
- Identity recovery lockouts affecting programme access
If the decision affects funding, access, or safety at scale, it belongs in a stamped lane.
Integration in 3 touchpoints
1
Issue
At eligibility decision / disbursement hold / sanctions hold / removal → require a Stamp.
2
Communicate
In letters, notices, funder packets, partner/bank comms → include the Status Link.
3
Rely
At disbursement/release/removal/enforcement → verify Status Link (fail-closed).
High-impact gating only. Everything else runs normally.
What you get (two artefacts, one standard)
Status Link (authoritative now)
A counterparty-verifiable link that returns current validity within scope.
- Returns: status, scope, expiry, verified_at, signer, verify_url
- Fail-closed: unreachable = NOT_VERIFIED
- Built for letters, portals, funder reports, and automated gates
IDA Evidence Pack (snapshot then)
View full details →A time-stamped snapshot you can forward, file, and cite.
- Built for appeals, audits, disputes, and funder reviews
- Append-only history pointer; withdrawal ≠ erasure
- Excludes PII/case files by default
PDFs are great for filing. Status Links keep them current.
If it gets challenged, does it survive?
(what the counterparty sees)
VALID
Valid within defined scope under lane rules (not a guarantee of outcome correctness).
NEEDS REFRESH
Evidence window expired or a material-change trigger fired → re-verify.
WITHDRAWN
Stop relying. Validity revoked. WITHDRAWN is returned wherever the Status Link is checked.
NOT VERIFIED
Treat as unverified. Also returned when verification can't be performed (fail-closed).
Fail-closed rule
If verification can't be performed (timeout/unreachable/error), the response is NOT VERIFIED. Block or escalate — never assume validity. VALID means valid within scope, not guaranteed correctness.
When status changes — and what it means
Status triggers define when a Status Link moves to NEEDS_REFRESH or WITHDRAWN. Understanding these ensures fail-closed enforcement at execution time.
NEEDS_REFRESH
When any of these occur, re-verify before you rely.
New documentation (income, residency, dependency, caregiver status)
Attendance/SAP status changes or is corrected
Appeals evidence added or reversed
Policy/criteria/rule-pack version change
Vendor/data source change (identity verification provider, fraud model update)
Threshold change (award limits, eligibility thresholds, sanctions thresholds)
Sanctions list update / screening vendor change
Donor/corridor constraint change
Payment rail/corridor requirement change
Evidence window expiry
NEEDS_REFRESH means "re-verify before you rely," not "defer."
WITHDRAWN
Stop-rely signal. Execution must not proceed.
Confirmed integrity breach on eligibility determination
Fraud/sanctions match confirmed post-approval
Partner/programme eligibility revoked
Case reopened with material reversal evidence
Critical incident requiring stop-rely pending investigation
Fail-closed: Wherever the Status Link is checked, if WITHDRAWN → block or escalate.
Global Coverage
Regulatory reality
No hype, no compliance claims — portable proof that survives cross-border review.
EU
AI governance pressure around education access and essential benefits eligibility; privacy constraints on automated decisioning.
UK
UK GDPR + funding oversight and complaint/appeal expectations; charity-sector sanctions obligations.
US
Federal/state audit and programme integrity scrutiny for aid eligibility/disbursement; sanctions screening obligations.
Canada
Automated decision oversight expectations for public programmes; strong privacy governance norms.
Australia
Growing governance frameworks; cross-border donor/bank scrutiny for aid programmes.
Asia
Emerging governance for benefits eligibility; traceability expectations in cross-border programmes.
Middle East
Expanding governance and sanctions compliance expectations; defensible records for programme decisions.
Africa
Aid programme governance strengthening across regional bodies; portable verification supports cross-border reliance.
Good Proof doesn't certify compliance. It makes high-impact eligibility and aid decisions verifiable, refreshable, and withdrawable by link.
Jurisdictional Configuration
Country overlays can be configured per programme
Configure scope boundaries, evidence windows, redaction matrix, verifier checklist, disclosure/retention/appeal handling, language support, and verifier-access requirements per jurisdiction.
Examples include programme-specific mapping for UAE, Saudi Arabia, South Africa, Kenya, and Nigeria where requirements differ.
Not legal advice. Final legal mapping is owned by programme counsel.
What counterparties can verify
No login. No portal. Just a link that fails closed.
Live validity state: VALID / NEEDS_REFRESH / WITHDRAWN / NOT_VERIFIED
Scope boundaries and expiry window
Signer authority reference (system or Guardian panel)
Verified_at timestamp
Forwardable IDA Evidence Pack
Optional signed verify responses (programme-scoped)
Optional: tamper-evident anchoring to Good Proof LIVE Ledger for high-assurance programmes.
Funder-safe and privacy-safe by design
- Proof ≠ payloads: minimal disclosure by default
- No mandatory external access to case systems
- Evidence Pack includes a configurable redaction matrix
- Optional programme-gated sealed annex for legally required disclosure, with auditable access trail
What's inside the IDA Evidence Pack
Programme-configured, dispute-ready.
Action summary + lane scope boundary
Decision-time timestamp + evidence window
Policy/rule-pack identifier + version references
Signer/authority reference
Verification transcript + timestamps
Redaction matrix (what's excluded by design)
AI-Agent Era
AI-agent era controls
Prompts can drift. Reliance controls must not.
Material change in policy/vendor/model/configNEEDS_REFRESH
Integrity or boundary breachWITHDRAWN
Timeout/unreachable verification routeNOT_VERIFIED (fail-closed)
Exception lane requiring human finalityGuardian path (optional)
Good Proof does not decide outcomes; it controls whether high-impact actions are safe to rely on.
Who uses this in Education & Aid
Financial Aid / Programme Ops
Pain: Denials and removals get appealed later; "the system said so" isn't evidence.
Outcome: Portable proof by link + time-stamped snapshot that survives audit.
Book a Stamp Sprint
Student Services / Casework
Pain: Hardship and exception decisions get challenged months later.
Outcome: Scoped, defensible trail without oversharing case internals.
Book a Stamp Sprint
Compliance / Audit
Pain: "Rebuild the record" work consumes cycles and introduces risk.
Outcome: Append-only history pointer + citable IDA Evidence Pack.
Book a Stamp Sprint
Legal / Appeals
Pain: Appeal panels and ombuds require evidence of what was authorised at decision-time, not narrative reconstruction.
Outcome: Status Link = reliance state now. IDA Evidence Pack = fileable decision-time record.
Book a Stamp Sprint
Funder / Donor Assurance
Pain: Grant disbursement reviews need portable evidence without system access.
Outcome: Counterparty-verifiable Status Link + Evidence Pack for programme reporting.
Book a Stamp Sprint
Payment Partners / Banks
Pain: De-risking and sanctions compliance require defensible decision records, not screenshots.
Outcome: Machine-checkable verification with scope + expiry + withdrawal propagation.
Book a Stamp SprintExternal Verifiers
Pain: Auditors, regulators, ombuds, and oversight bodies need to verify without portal access.
Outcome: Status Link + IDA Evidence Pack — verify by link, cite in filings.
Book a Stamp SprintBudget reality
Where the budget sits, what triggers buying, and why now.
Appeals operations / casework
Trigger: Rising appeals volume or tribunal/ombuds escalation
Portable decision-time evidence reduces reconstruction effort and repeat review cycles.
Compliance / audit
Trigger: Funder audit finding, programme integrity review, or recurring record gaps
Append-only verification trail + Evidence Pack snapshots replace manual record rebuilding.
Sanctions / payment controls
Trigger: Bank de-risking pressure, sanctions screening escalation, or corridor payment hold
Defensible decision records with WITHDRAWN propagation for sanctions-related holds.
Legal defensibility
Trigger: Complaint escalation, tribunal referral, or litigation preparation
Status Link + Evidence Pack provide citable, verifiable decision-time records.
Funder / donor assurance
Trigger: Grant reporting burden, programme integrity review, or funder due diligence
Portable verification surface for cross-party reliance without system access.
Vendor / procurement risk
Trigger: Third-party provider change, vendor audit, or screening model update
Material change triggers NEEDS_REFRESH; stop-rely on WITHDRAWN propagates wherever checked.
Incident response / reversals
Trigger: Post-approval fraud discovery, eligibility reversal, or case reopening
Immediate WITHDRAWN propagation + append-only history prevents unsafe reliance.
How it works (3 steps)
1
Stamp the decision
Define scope boundaries, evidence window, and criteria/version at decision time.
2
Gate high-impact execution
Pre-execution Status Link check at disbursement/removal/enforcement. Not VALID → block or escalate.
3
Revoke fast when risk changes
Set WITHDRAWN on compromise/invalidation. Stop-rely propagates wherever the Status Link is checked.
Make the gate machine-checkable, not meeting-checkable.
Procurement-ready clause
Template language for your legal team.
"For any defined high-impact Education & Aid decision class, Provider shall obtain and maintain a Good Proof Stamp with an active Status Link. Actions taken with a status of NOT_VERIFIED, NEEDS_REFRESH, or WITHDRAWN shall be treated as unverified and must be blocked or escalated per programme rules."
Schedule A (template — programme terms)
Definitions + operating rules procurement teams can copy/paste.
1. Definitions
- High-Impact Decision Class: the defined action lane (e.g., eligibility removal, sanctions hold, disbursement hold) requiring verification.
- Status Link: the verification endpoint returning validity state + scope boundaries.
- Scope Boundary: the programme/policy/criteria configuration covered by the Stamp.
- Evidence Window: the programme-defined period and inputs considered for decision-time verification.
- Evidence Pack: the fileable, programme-configured snapshot for disputes/audit/procurement.
2. Required states
- VALID→ may proceed within scope.
- NEEDS_REFRESH/ NOT_VERIFIED / WITHDRAWN → must block or escalate per lane rules.
- Fail-closed:timeout/unreachable ⇒ NOT_VERIFIED.
3. Withdrawal / stop-rely semantics
- WITHDRAWN is returned wherever the Status Link is checked.
- History is append-only; WITHDRAWN ≠ erasure.
- Optional: programme hooks for downstream stop-rely notification.
4. SLA placeholders
Verifier availability %, p99 latency, Evidence Pack export window, time-to-propagate WITHDRAWN — populated per Order Form.
5. Evidence retention defaults
Retention windows configured per programme and jurisdiction. Default Evidence Packs exclude PII and raw payloads. Jurisdictional overlays define what surfaces, who can access it, and for how long.
Technical safeguards
- HTTPS-only verifier endpoint
- Official verifier host allowlist (verify_url host must match)
- Redirects forbidden; timeout/unreachable ⇒ NOT_VERIFIED
Not legal advice. Template language for your legal team. Bracketed placeholders to be completed by parties in Order Form or Exhibit.
A Global Human Layer
Our Mind Chill Guardian Story
A global human layer that software can't fake.
When liability lands on a person, the sign-off should too.
Conflict-checked · Rotation-based · Audit-traceable · Programme-scoped
When Guardians are used (only when required)
Most decisions remain automated. Humans step in only where human finality is required: exception approvals, disputes, high-risk overrides, or post-incident outcomes with human liability.
Mind Chill Guardians provide programme-scoped human finality for exception lanes only, minimizing sensitive payload handling, with anti-rubber-stamp controls: conflict checks, rotation, sampling audits, and multi-review thresholds for high-risk lanes.
From calming minds to defending outcomes
Mind Chill began in 2017 as immersive art built to reduce anxiety and create calm at scale. Then the same feeds that buried calm and rewarded outrage started training the systems that now make real decisions. We didn't want more rhetoric. We wanted receipts.
The moment it clicked
A message arrived: someone's child felt safer because of what they experienced. Around the same time, lived experience inside our own community made one thing obvious: the nuance that matters in high-impact decisions can't be reliably reduced to a prompt. So we designed a human layer for the edge cases—structured, scope-bound, and auditable.
Guardians are not a "panel." They're a network.
Mind Chill Guardians come from different countries, backgrounds, and lived realities. That diversity is not branding—it's risk reduction. It makes decisions harder to game, easier to challenge, and more credible under scrutiny. Guardians do not "run the system." They review only what the lane requires humans to own.
Receipts over rhetoric
Operational Guardians plug into Good Proof lanes as a controlled finality mechanism: conflict checks, rotation, multi-review where required, and an audit trace tied to a Status Link. Minimal disclosure by default. If a decision is appealed months later, you can show what happened, within scope, without dumping sensitive payloads.
Why buyers choose Guardians
Lived experience at the edge cases (not a generic helpdesk)
Conflict-checked + rotation-based (anti-rubber-stamp by design)
Multi-review on high-risk lanes (when the programme requires it)
Audit-traceable outcomes (defensible in disputes, audits, procurement)
Minimal disclosure by default (proof, not payloads)
What you get in 30 days
One decision class, production-ready.
One decision class defined (e.g., "eligibility removal", "sanctions screening hold/release", "disbursement hold/release")
Scope boundaries documented
Pre-execution gate integrated (staging or production)
Refresh + withdrawal triggers configured
Counterparty verification route tested end-to-end
One redacted IDA specimen generated from your workflow
Go/no-go rollout recommendation
Due Diligence FAQs
Make Education & Aid decisions shippable.
Start with one decision class. Ship one gate. Expand when counterparties rely on the Status Link.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.