Hiring & Screening — HR
Hiring decisions that survive scrutiny months later.
No Stamp → No Ship for high-impact HR decisions.
Screening flags, adverse actions, and terminations are access, income, and reputation decisions. Defensibility needs both decision-time proof and current reliance state.
- Gate high-impact actions by Status Link: not VALID → block or escalate (per programme runbooks)
- Proof that travels outside your perimeter: counterparties verify scope • expiry • signer • status by link
- Evidence Pack (IDA format) (decision-time snapshot): reusable across audits, tribunals, and partner reviews
Fail-closed•Append-only•Scope-bounded
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
Why HR buyers are moving now
Governance expectations, dispute pressure, and vendor drift are converging.
AI hiring governance expectations rising
Regulators and oversight bodies increasingly expect traceability and controllability in AI-assisted employment decisions.
Dispute, appeal, and tribunal pressure
Adverse actions, screening rejects, and terminations are challenged months later. Evidence reconstruction costs escalate.
Adverse-action workflow scrutiny
Pre-adverse and final adverse action workflows are audited for timing, notice, and decisional defensibility.
Model/vendor/policy drift risk
Background check vendors, scoring thresholds, and policy templates change silently. Prior decisions stay trusted unless you revoke.
Recourse and contestability expectations
Candidates, employees, and oversight bodies expect decision outcomes to be checkable, challengeable, and correctable.
Portable proof without exposing internals
Counterparties need to verify status without access to HRIS, ATS, or internal case files.
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 + outcome (reject/hold/escalate; adverse action steps; employment action outcome)
- Decision-time timestamp
- Signer/authority reference
- Scope boundaries + expiry
- Validity state (VALID / NEEDS_REFRESH / WITHDRAWN / EXPIRED / NOT_VERIFIED)
- Evidence window for dispute/review
Does NOT prove
- Underlying truth of candidate information
- Outcome correctness
- Certification / regulatory compliance
- Candidate PII or HRIS internals by default
In disputes: Status Link = reliance state now. Evidence Pack = decision-time snapshot for filing.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
Integration in 3 touchpoints
1
Issue
At decision issuance (screening reject, adverse action, termination) → require a Stamp.
2
Notify
In candidate notices / vendor packets / counsel bundles → include Status Link.
3
Rely
At final action / access removal → verify Status Link (fail-closed).
High-impact gating only. Everything else runs normally.
Global Coverage
Regulatory reality
What teams are asked for in practice — no compliance claims.
US
EEOC expectations, FCRA adverse-action workflows, and state/municipal automated employment decision tool rules.
EU
GDPR constraints on automated decision-making. Employment-related AI can fall into high-risk categories.
UK
ICO guidance on AI and data protection, Equality Act obligations, and employment tribunal expectations.
Canada
Ontario AI-in-hiring disclosure requirement effective Jan 1, 2026. Signals tighter governance expectations.
Australia
Privacy regulator guidance on AI products and personal information handling in employment contexts.
APAC
Governance frameworks emphasise traceability and controllability. Singapore's agentic AI governance signals best-practice.
Middle East
Public-sector and employment-governance expectations around decision traceability and authority control.
Africa
Scrutiny rising around administrative fairness, records, recourse, and privacy-aware handling of decision workflows.
Good Proof doesn't certify compliance. It makes outputs verifiable, refreshable, withdrawable by link — so disputes don't collapse into "trust us."
Jurisdictional Configuration
Country overlays can be configured per programme
Examples include programme-specific mapping for UAE, Saudi Arabia, South Africa, Kenya, Nigeria, and other jurisdictions where disclosure, retention, appeal handling, language support, and verifier-access requirements differ.
Configure scope boundaries, evidence windows, redaction matrix, and verifier checklist per jurisdiction.
Not legal advice. Final legal mapping is owned by programme counsel.
Why now
Governance expectations rising
AI hiring governance and transparency expectations rising (audits, records, contestability).
Dispute pressure increasing
Litigation + dispute pressure increasing; evidence reconstruction costs explode.
Silent drift risk
Vendor/model/policy change creates silent drift unless you gate and revoke reliance.
Good Proof doesn't decide outcomes; it makes governance verifiable at the moment it mattered — and reliance withdrawable when conditions change.
What gets stamped in this lane
High-impact action classes (examples—define per programme):
Screening & progression gates
- Reject/hold/escalate outcomes driven by screening flags
- Ranking cutoffs used to decide interviews (programme scoped)
- Eligibility gates (right-to-work, minimum requirements, regulated role checks)
Adverse action & background checks
- Pre-adverse action trigger + workflow completion (programme scoped)
- Final adverse action decision tied to report outcome
- Dispute outcomes when a background report is challenged
Employment actions
- Termination / suspension / access removal decisions (programme scoped)
- Policy breach classifications that trigger irreversible action
- Probation failure decisions (programme scoped)
Accommodations & exceptions
- Accommodation approvals/denials (scope-bound, minimal disclosure)
- Leave eligibility decisions (where duty-of-care liability applies)
- Policy exception approvals with signer authority
Vendor + model changes
- Background check vendor / dataset changes affecting outcomes
- Score threshold or screening logic updates
- Model retrain / rule pack updates that alter behaviour
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
- Works in ATS/HRIS gates and ticket workflows
IDA Evidence Pack (snapshot then)
View full details →A time-stamped snapshot you can forward, file, and cite.
- Built for audits, tribunals, disputes, and procurement
- Minimal disclosure by default (proof ≠ payloads)
- Append-only history; withdrawal does not erase
PDFs are great for filing. Status Links keep them current.
Live Status States
(what your systems can gate on)
VALID
Decision stands.
Rely on it within scope.
NEEDS REFRESH
Policy/evidence changed.
Re-verify before relying.
WITHDRAWN
Stop relying immediately.
Returned wherever checked.
NOT VERIFIED
No proof exists.
Block or escalate.
VALID = valid within scope (not a guarantee of outcome 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.
Model retrain / rule pack update / threshold change
scoring cutoffs, screening logic, risk label definitions
Policy update
adverse action workflow, templates, ban-the-box timing
Background check vendor change or dataset refresh
new provider, data source update, matching rule changes
Job requirement change
location, clearance, license, safety requirements
Candidate dispute evidence received or correction event
identity correction, right-to-work update (programme scoped)
Approval authority changes
who can sign what, and under which limits
NEEDS_REFRESH means "re-verify before you rely," not "schedule a meeting."
WITHDRAWN
Stop-rely signal. Execution must not proceed.
Court, tribunal, ombuds, or oversight-directed pause for the affected decision class
Confirmed configuration or policy-mapping defect with material impact on in-scope outcomes
Integrity failure in upstream registry/feed relied on for issuance
Authority boundary breach in delegated workflow (invalid signer or exceeded limits)
Confirmed dependency compromise where current reliance can no longer be defended
Fail-closed: Wherever the Status Link is checked, if WITHDRAWN → block or escalate.
What's inside the IDA Evidence Pack
Decision-time snapshot for disputes, audits, and filing.
Decision summary + lane scope boundary
Decision-time timestamp + evidence window
Policy/criteria identifiers + version references
Workflow/tool surface identifiers + version references
Authority reference (signer/system)
Verification transcript + timestamps
Redaction matrix (what is intentionally excluded)
Proof ≠ payloads. Raw CVs/PII/background reports are not required by default. Programme-gated access when required.
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)
Verification route and SLA
Optional: tamper-evident anchoring to Good Proof LIVE Ledger for high-assurance programmes.
Who buys this in HR
Commercial and public-sector buyers with high-impact decision accountability.
Commercial buyers
Talent Acquisition / Recruiting Ops
Pain: Screening rejects get challenged; proving "what happened" becomes manual archaeology.
Outcome: Portable proof by link + clear refresh/withdraw semantics.
Book an HR Stamp SprintHR / Employee Relations
Pain: Adverse actions and terminations are contested months later.
Outcome: Time-stamped snapshot then + authoritative status now.
Book an HR Stamp SprintPeople Operations / Shared Services
Pain: Cross-functional employment actions lack a single verification surface.
Outcome: Status Link + Evidence Pack unify proof across teams and vendors.
Book an HR Stamp SprintLegal / Employment Counsel
Pain: Disputes expand into discovery; you need defensible, scope-bound artefacts.
Outcome: Citable Evidence Pack + verifiable Status Link for filing.
Book an HR Stamp SprintCompliance / Internal Audit
Pain: Evidence retrieval for audits is slow, system-bound, and fragile.
Outcome: Fileable Evidence Pack snapshots with append-only history and redaction matrix.
Book an HR Stamp SprintHRIS / ATS Product Owners
Pain: Adding verification controls risks system-replacement overhead.
Outcome: Lane-scoped gate check at issuance, notification, and reliance points; no rip-and-replace.
Book an HR Stamp SprintCIO / CISO / AI Governance
Pain: AI hiring tools lack runtime controls for high-impact actions.
Outcome: Fail-closed gate + stop-rely semantics for model/vendor drift.
Book an HR Stamp SprintBackground Screening Programme Owners
Pain: Vendor changes, dataset updates, and matching rule shifts silently alter outcomes.
Outcome: Material change triggers NEEDS_REFRESH; stop-rely on WITHDRAWN propagates wherever checked.
Book an HR Stamp SprintExternal and public-sector buyers
Regulators and inspectorates
Pain: Oversight depends on employer-provided evidence that's hard to independently check.
Outcome: Verifier-checkable status with portable Evidence Pack for cross-agency review.
Book an HR Stamp SprintTribunal/ombuds-facing teams
Pain: Evidence bundles for proceedings are reconstructed under time pressure.
Outcome: Scope-bounded Evidence Pack snapshots with decision-time proof and redaction matrix.
Book an HR Stamp SprintOutside counsel
Pain: Litigation support requires defensible, minimal-disclosure artefacts.
Outcome: Citable verification + fileable Evidence Pack without exposing internal systems.
Book an HR Stamp SprintAuditors / assurance partners
Pain: Audit evidence is system-bound and inconsistent across employer tech stacks.
Outcome: Standardised verification surface with append-only history.
Book an HR Stamp SprintPublic-sector employer oversight bodies
Pain: Civil-service hiring decisions face multi-agency scrutiny.
Outcome: Cross-party verifiable status with configurable redaction and retention.
Book an HR Stamp SprintBackground-check counterparties
Pain: Upstream providers need to confirm how their outputs were used in decisions.
Outcome: Status-linked decision proof with scope boundaries — without exposing internal case files.
Book an HR Stamp SprintWhere budget comes from
Usually funded from existing risk, legal, and compliance lines — not new category spend.
Legal / dispute cost containment
Trigger: Tribunal filing, adverse-action dispute, or settlement escalation
Why it fits: Portable evidence + fail-closed reliance reduce reconstruction effort and dispute exposure.
Audit / remediation readiness
Trigger: Internal audit finding, regulator inquiry, or post-incident review
Why it fits: Append-only verification history with Evidence Pack snapshots for review workflows.
HR transformation / digital controls
Trigger: New ATS/HRIS rollout, process change, or AI-tool adoption
Why it fits: Lane-scoped integration at gate points; minimal validation footprint.
AI governance / model risk controls
Trigger: AI governance mandate, model retrain, or vendor-change risk assessment
Why it fits: Material change triggers NEEDS_REFRESH; status controls model/vendor drift.
Adverse-action workflow defensibility
Trigger: FCRA/EEOC scrutiny, adverse-action timing audit, or candidate dispute spike
Why it fits: Decision-time snapshot + live status make workflow checkpoints defensible.
Incident response / stop-rely governance
Trigger: Data breach, integrity failure, or vendor compromise affecting in-scope decisions
Why it fits: WITHDRAWN propagates wherever Status Link is checked — no stale reliance.
Start with one high-impact lane and prove dispute/audit friction reduction before expansion.
AI-Agent Era
AI-agent era controls
Prompts can drift. Reliance controls must not.
Material change in policy/vendor/model/thresholdNEEDS_REFRESH
Integrity or authority 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.
HR lane menu
Start with one lane. Prove it in 30 days. Expand when counterparties rely on the Status Link.
What ships every time: Status Link (authoritative now) + Evidence Pack (snapshot then).PDFs are great for filing. Status Links keep them current.
Screening Reject Gates
Make reject/hold/escalate outcomes defensible with scope + timestamp + refresh/withdraw triggers.
Book an HR Stamp SprintAdverse Action Workflow
Stamp pre-adverse and final adverse action checkpoints with signer authority and evidence windows.
Book an HR Stamp SprintTermination / Access Removal
Turn termination and access removal decisions into portable proof with stop-rely semantics.
Book an HR Stamp SprintBackground Check Disputes
When a report is challenged, stamp the dispute outcome so counterparties can verify resolution status.
Book an HR Stamp SprintAccommodation & Leave Decisions
Scope-bound verification for accommodation and leave decisions where duty-of-care liability applies.
Book an HR Stamp Sprint
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 audits, tribunals, procurement)
Minimal disclosure by default (proof, not payloads)
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
How it works (simple)
1
Define the high-impact decision class
Scope boundaries, evidence window, and what triggers refresh or withdrawal.
2
Require a Stamp
No Stamp, NOT_VERIFIED, or NEEDS_REFRESH → block or escalate (per programme runbooks).
3
Ship portable proof
Issue the Status Link and generate the Evidence Pack automatically.
4
Humans step in only when required
Guardians handle exceptions and disputes inside defined scope, with anti-rubber-stamp controls.
Procurement-ready clause
Template language for your legal team.
"For [High-Impact Decision Classes], Supplier shall issue a Good Proof Stamp prior to action. Buyer may verify status via the Status Link. Stamps returning NOT_VERIFIED, NEEDS_REFRESH, or WITHDRAWN shall block or escalate per programme runbooks."
Schedule A: Status-Link Reliance Terms (HR)
Definitions + operating rules procurement teams can copy/paste.
1. Definitions
- High-Impact Decision Class: A defined action category requiring verification (e.g., adverse action, termination, screening reject).
- Status Link: The verification endpoint returning validity state + scope boundaries.
- Evidence Window: Programme-defined period during which evidence is considered current.
- Evidence Pack: Time-stamped snapshot for filing/disputes (IDA format).
- Scope Boundary: Limits defining what the verification covers (and what it doesn't).
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.
- No execution may proceed on WITHDRAWN.
- Optional: programme hooks/notifications for stop-rely distribution.
SLA placeholders (complete per programme)
Verifier availability target: [___]%. Response-time target: [___] ms. Support turnaround: [___] hours.
Not legal advice. Bracketed variables to be completed by the parties.
Procurement pack available: architecture summary, data handling overview, subprocessors, retention options.
What you get in 30 days
One decision class, production-ready controls.
One decision class defined and documented (e.g., "background-check adverse action" or "screening reject gate")
Stamp issuance workflow integrated (staging or production)
Status Link verification route usable by external reviewers (without internal access)
Refresh and withdrawal triggers configured
Dispute-ready verifier checklist for HR/legal/audit
One redacted specimen Evidence Pack generated from your workflow
Due Diligence FAQs
Make Hiring & Screening decisions shippable.
Start with one decision class. Prove it works. Expand when reviewers rely on the Status Link.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.