Disconnection & Hardship — Utilities
High-impact utility decisions that survive scrutiny months later.
No Stamp → No Action for defined high-impact lanes.
When service access is at stake, regulators and ombuds don't judge your dashboard. They judge what you can prove was authorised within scope at decision time, and whether reliance stopped when conditions changed.
- Gate execution by Status Link: not VALID → block or escalate
- Counterparties verify by link: scope • expiry • signer • status
- Ships with an Evidence Pack: time-stamped snapshot you can file and cite
Fail-closed•Append-only•Scope-bounded
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
Why utilities buyers are moving now
Affordability pressure, tighter safeguards, and automation scrutiny are converging.
Affordability pressure and arrears volatility
Rising cost-of-living is increasing disconnection volumes, dispute escalations, and ombuds complaints. Decisions made under pressure need portable proof.
Tighter vulnerability safeguards
Regulators are strengthening protections for vulnerable customers. Vulnerability flag removals and hardship denials face retrospective scrutiny.
Smart meter and remote action scrutiny
Remote disconnection, prepayment forcing, and mode-switch decisions are under increasing regulatory and media attention.
Ombuds and regulator dispute volume
Complaint and escalation volumes are rising. Decision evidence needs to travel outside internal systems for review.
AI/automation policy drift risk
Automated decision workflows change silently. Policy, model, and threshold updates can invalidate prior decisions unless status is machine-checkable.
Portable proof across counterparties
Regulators, ombuds, consumer bodies, auditors, and municipal authorities need to verify without logging into your systems.
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 (disconnect/reconnect, vulnerability flag add/remove, hardship approve/deny, collections escalation, appeal outcome, remote meter action)
- Decision-time timestamp
- Signer/authority reference
- Scope boundary + expiry window
- Validity state (VALID / NEEDS REFRESH / WITHDRAWN / NOT VERIFIED)
- Evidence window for dispute/oversight
Does NOT prove
- Underlying truth of the customer's circumstances
- Outcome correctness
- Certification or regulatory compliance
- PII/case-file contents 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.
Integration in 3 touchpoints
1
Issue
At decision issuance (disconnect approval, vulnerability removal, hardship denial, collections escalation trigger) → require Stamp
2
Notify
In notices/letters/ombuds packs/regulator packets → include Status Link
3
Rely
At field execution / remote disconnect / debt handoff → verify Status Link (fail-closed)
High-impact gating only. Everything else runs normally.
Global Coverage
Regulatory reality
No hype, no compliance claims — portable proof that survives cross-border review.
UK
Vulnerability/PSR expectations + enforcement scrutiny; prepayment protections as signal
EU
Consumer protection + data governance scrutiny for automated decisions impacting people
US
PUC oversight + medical hardship protections; defensible records for disconnections and billing disputes
Canada
Seasonal disconnection bans in some jurisdictions; regulator/ombuds scrutiny
Australia
Strengthened minimum disconnection protections and payment difficulty rules
APAC
Governance frameworks emphasise traceability/controllability/bounded risk
Middle East
Utility governance expanding; defensible records for service access and hardship decisions
Africa
Energy and water regulation strengthening across regional bodies; portable verification supports cross-border reliance
Good Proof doesn't certify compliance. It makes high-impact utilities decisions verifiable, refreshable, and withdrawable by link.
Jurisdictional Configuration
Country overlays can be configured per programme
Examples include programme-specific mapping for regional vulnerability protections, winter moratorium rules, and safeguarding requirements that differ by jurisdiction.
Configure scope boundaries, evidence windows, redaction matrix, and verifier checklist per jurisdiction.
Not legal advice. Final legal mapping is owned by programme counsel.
Why Utilities is painful
Utilities is one of the few sectors where a "decision" can turn into a safety incident.
AI is now influencing disconnection, hardship, and vulnerability decisions where the real failure mode isn't "the model was wrong."
It's: we can't prove what was true at decision time — and what's valid now — without exporting half the case system.
What gets stamped in Utilities
Examples of high-impact action classes (define per programme):
Disconnection & reconnection
- Disconnection approval (electricity/gas/water)
- Reconnection eligibility and timelines
- Safe-stop / safety-related service interruption decisions
- Remote meter disconnection/reconnection gates
Hardship & vulnerability
- Vulnerability flag assignment/removal
- Priority services register (PSR) eligibility outcomes
- Hardship override approvals/denials
- Payment plan approvals/denials
- Medical dependence / safeguarding escalation triggers (programme-scoped)
Debt escalation & collections
- Escalation to collections / enforcement trigger decisions
- Benefit removal decisions that change affordability outcomes
- High-impact "final notice" automation gates
- Debt handoff gates (internal or third-party)
Appeals & dispute outcomes
- Appeal decisions (uphold/overturn)
- Complaint closure decisions where a regulator or ombuds may inspect later
- Exception handling where liability lands on a person
Smart meter & remote actions
- Remote meter action gates (mode switch, limit, disconnection)
- Prepayment meter forced installation decisions
- Firmware or configuration change gates on customer-facing meters
Operational & safety escalations
- Outage restoration prioritisation exceptions
- Fraud/tamper escalation decisions
- Water quality / safety notification escalations
- Emergency event exception lanes (storm, civil resilience)
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 contracts, runbooks, tickets, and automated gates
IDA Evidence Pack (snapshot then)
View full details →A time-stamped snapshot you can forward, file, and cite.
- Built for committees, audits, disputes, and procurement
- Append-only history; withdrawal ≠ erasure
- Excludes case files, PII by default
One Stamp produces both. PDFs are great for filing. Status Links keep them current.
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.
Policy change (disconnection rules, winter moratorium rules, hardship criteria)
Vulnerability status change (new evidence, medical dependence update, safeguarding note)
Payment posture change (plan agreed, arrears cleared, benefit status changed)
Data source change (third-party vulnerability data updates, credit/affordability model updates)
Threshold change (arrears thresholds, escalation rules, collections criteria)
Tool-surface change (automation workflow version, agent tool permissions, rule pack update)
NEEDS_REFRESH means "re-verify before you rely," not "schedule a meeting."
WITHDRAWN
Stop-rely signal. Execution must not proceed.
Confirmed data integrity breach affecting decision inputs
Safeguarding incident discovered post-decision
Vulnerability status invalidated / critical update missed
Material policy breach discovered post-approval
Incident outcome requires stop-rely pending investigation
Fail-closed: Wherever the Status Link is checked, if WITHDRAWN → block or escalate.
What's inside the IDA Evidence Pack
Programme-configured. Minimal disclosure by default.
Decision summary + lane scope boundary
Decision-time timestamp + evidence window
Policy/version references (e.g., disconnection rules, hardship criteria)
Workflow/tool surface version references
Signer/authority reference
Verification transcript + timestamps
Redaction matrix + exclusions list
Proof ≠ payloads. No PII/case files by default.
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.
Live Status States
(what the counterparty sees)
VALID
Decision is currently valid within scope under lane rules.
NEEDS REFRESH
Evidence window expired or a material change trigger fired → re-verify before relying.
WITHDRAWN
Stop relying. 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), default is NOT VERIFIED → block or escalate.
VALID = valid within scope (not a guarantee of outcome correctness).
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 rules).
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.
Example: disconnection approval
1. Check Status Link for policy version + vulnerability status + hardship criteria
VALID → proceed with disconnection
NEEDS_REFRESH → re-verify before execution
WITHDRAWN / NOT_VERIFIED → block + escalate
Who buys this in Utilities
Commercial and public-sector buyers with high-impact decision accountability.
Commercial / operator buyers
Customer Operations
Pain: Disconnection disputes escalate to regulators with no portable proof trail.
Outcome: Every high-impact decision has a verifiable Status Link that survives escalation.
Book a Utilities Stamp SprintHardship & Vulnerability Teams
Pain: Vulnerability flags and hardship outcomes get challenged; "why was this removed/denied?" becomes a crisis.
Outcome: Live status shows validity, refresh triggers on change, and supports defensible reversals.
Book a Utilities Stamp SprintRevenue Protection / Collections Governance
Pain: Debt escalation and final-notice gates lack decision-time proof when challenged.
Outcome: Stamped escalation triggers with fail-closed enforcement before handoff.
Book a Utilities Stamp SprintSmart Meter Operations
Pain: Remote actions (disconnect, mode switch, forced prepayment) face media and regulatory scrutiny.
Outcome: Gate remote actions on VALID status; status travels with the decision for review.
Book a Utilities Stamp SprintField Service Operations
Pain: Field execution of disconnection/reconnection relies on internal system state that doesn't travel.
Outcome: Status Link checked at point of execution; not VALID → block or escalate.
Book a Utilities Stamp SprintRegulatory Compliance / Internal Audit
Pain: Oversight requires proof of what was true at decision time — without exporting sensitive case data.
Outcome: Evidence Pack is the time-stamped snapshot; append-only history for audit trail.
Book a Utilities Stamp SprintLegal + Procurement
Pain: Contract clauses lack machine-checkable verification semantics for high-impact decisions.
Outcome: Procurement-ready clause template + Schedule A with status-linked operating rules.
Book a Utilities Stamp SprintCIO/CISO / Digital Risk / AI Governance
Pain: Automated decision workflows change silently; no portable verification surface for AI-assisted decisions.
Outcome: Lane-scoped gate checks with fail-closed semantics; no rip-and-replace.
Book a Utilities Stamp SprintPublic-sector and external buyers
Utility regulators / commissions
Pain: Enforcement actions require portable proof of what was authorised at decision time.
Outcome: Verifier-checkable status with Evidence Pack for cross-utility review.
Book a Utilities Stamp SprintOmbuds / dispute bodies
Pain: Complaint adjudication relies on utility-provided screenshots and exports.
Outcome: Independent verification by Status Link; Evidence Pack for filing.
Book a Utilities Stamp SprintMunicipal utility authorities
Pain: Oversight of disconnection and hardship decisions across providers lacks consistency.
Outcome: Standardised verification surface with scope boundaries and fail-closed semantics.
Book a Utilities Stamp SprintPublic service ministries
Pain: Policy enforcement on vulnerability protections is hard to verify at scale.
Outcome: Status-linked governance evidence with configurable redaction and retention.
Book a Utilities Stamp SprintEmergency management / resilience authorities
Pain: Emergency exception decisions (storm, outage prioritisation) need defensible records.
Outcome: Scope-bounded verification for emergency lanes with withdrawal propagation.
Book a Utilities Stamp SprintCritical infrastructure assurance bodies
Pain: Assurance of high-impact utility decisions across operators is fragmented.
Outcome: Portable verification surface for cross-party reliance with stop-rely controls.
Book a Utilities Stamp SprintWater Quality Incident Operations
Pain: Water quality and safety notifications involve decisions that face public and regulatory scrutiny.
Outcome: Stamped notification escalation decisions with fail-closed status and Evidence Pack for review.
Book a Utilities Stamp SprintWhere budget comes from
Usually funded from existing compliance, customer protection, or audit modernisation lines — not new category spend.
Compliance / remediation budget
Trigger: Regulator enforcement action, audit finding, or recurring complaint patterns
Why it fits: Portable evidence + fail-closed reliance control reduce reconstruction effort and repeat findings.
Customer protection budget
Trigger: Vulnerability safeguard failures, PSR compliance gaps, or hardship dispute spikes
Why it fits: Decision-time proof for vulnerability and hardship outcomes; defensible under ombuds review.
Audit modernisation budget
Trigger: Manual evidence reconstruction for regulator/ombuds requests or internal audit
Why it fits: Evidence Pack snapshots replace ad-hoc system exports with append-only, programme-configured records.
Digital transformation / controls budget
Trigger: AI/automation rollout, smart meter programme, or workflow modernisation
Why it fits: Lane-scoped gate checks at decision points; minimal integration footprint, no rip-and-replace.
Incident governance budget
Trigger: Data breach, safeguarding incident, or post-decision discovery requiring stop-rely
Why it fits: WITHDRAWN propagates wherever the Status Link is checked; fast blast-radius reduction.
Dispute cost reduction budget
Trigger: Rising ombuds/regulator complaint volumes or litigation costs
Why it fits: Portable proof reduces dispute cycle time and evidence production cost.
Start with one high-impact lane and prove dispute/audit friction reduction before expansion.
Public-sector fit
Useful where utility decisions require defensible records across operators, regulators, and review bodies.
Cross-party verifiability
Regulators, ombuds, and consumer bodies verify by Status Link without system access. No portal, no NDA for default verification.
Minimal disclosure by default
Evidence Packs exclude PII and case files unless programme-gated. Proof travels; sensitive payloads don't.
Fileable decision-time evidence
Time-stamped snapshots built for filing, committees, and dispute adjudication. Append-only history for audit trail.
Fail-closed status semantics
Timeout/unreachable = NOT_VERIFIED. Block or escalate — never assume validity. Withdrawal propagates wherever checked.
Programme counsel defines jurisdictional mapping, retention, and disclosure boundaries.
AI-Agent Era
AI-agent era controls
Prompts can drift. Reliance controls must not.
Material change in policy/threshold/workflow/vendorNEEDS_REFRESH
Integrity or safeguarding 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.
OUR MOAT
We Care Defensibly
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)
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
Procurement-ready clause
Template language for your legal team.
"For any defined high-impact utilities decision (disconnection, vulnerability flag removal, hardship denial, collections escalation, remote meter action), 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 Action Class: the defined decision lane (e.g., disconnection approval, vulnerability removal, hardship denial, remote meter action) requiring verification.
- Status Link: the verification endpoint returning validity state + scope boundaries. Host MUST match the official verifier domain (HTTPS only, no redirects).
- Scope Boundary: the policy/vulnerability/hardship 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 (IDA format).
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. Anti-spoof controls
- verify_url host MUST exactly match the official verifier domain.
- HTTPS/TLS required; no insecure overrides.
- Redirects strictly forbidden. Domain mismatch → NOT_VERIFIED.
4. 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 (if required).
5. SLAs (placeholders — programme-defined)
Verifier availability target: [___]%. Response-time target: [___] ms. Support turnaround: [___] hours.
6. Evidence retention defaults
Evidence Packs retained per client retention policy and applicable jurisdiction/programme needs (e.g., regulatory lifecycle + dispute window).
Not legal advice. Template language for your legal team. 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 high-impact decision class defined (scope + evidence window + triggers)
Stamp issuance workflow integrated (staging or production)
Status Link verification route ready for counterparties
Refresh and withdrawal triggers configured
Dispute-ready verifier checklist produced
Optional Guardian exception route (programme-scoped)
Due Diligence FAQs
Make high-impact utility decisions shippable.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.