Public sector
Public bodies apply published rules to whole populations and must explain every outcome to the person affected. Helixor applies those rules exactly and records which one decided. It improves them from appeals and outcomes through a gated loop, and it runs where data must stay in the site.
The situation#
Agencies decide eligibility, triage casework and schedule inspections at volume, under published criteria and with a duty to explain. The same facts must produce the same outcome for every applicant, and when criteria change, the change must be deliberate and testable. Many environments also require that data stays in-country, inside an accredited network, or on a network with no internet access at all.
Helixor's deterministic core evaluates in process, verifies its license locally and makes no network calls, so it runs in all of those environments. The learning loop, reasoning and solvers are hosted and optional; sovereign sites can run the core alone and bring learning in through reviewed pack releases.
Decisions that fit#
| Decision | Platform parts | Learning loop learns from | Status |
|---|---|---|---|
| Benefits eligibility: eligible, ineligible or refer, against published criteria | Core (criteria, reason, counterfactual remedy), outcome memory, learning loop | Appeal outcomes, caseworker overrides, later eligibility corrections | Planned |
| Explaining a refusal: which criterion failed and what would have changed it | Core remedy, counterfactual analysis | Not learned; derived from the decision | Planned |
| Case triage: priority and team for incoming cases | Core, reasoning for unclear cases, human review | Reassignments, escalations, time to resolution | Planned |
| Inspection scheduling: which sites, which inspectors, which week | Solvers over risk priorities and inspector constraints, learning loop | Findings per inspection, missed deadlines, manual reschedules | Preview |
| Air-gapped and sovereign deployment of the decision core | Core, local license verification, local compilation | Through reviewed pack releases carried into the site | Available |
Rows marked Planned depend on a pack you author from your published guidance. The data-protection pack that ships today can also screen documents for structured identifiers before public release.
Not legal advice
Helixor helps you apply published criteria consistently, explain each outcome and gate every change. It does not by itself satisfy an administrative-law, records, privacy or accreditation obligation. Ask your own counsel and accreditor.
Recommended deployment#
For sites without internet access, use pattern 4, air-gapped, with the core deployed as pattern 1, 2 or 3 inside the site. The wheel, the license and packs cross the gap once. You compile playbooks inside with helixor-pack compile and no --remote, deny egress, and keep hosts on the site's time source. Where controlled connectivity exists, hybrid escalation (pattern 5) adds reasoning, solvers and the learning loop for the data you decide may leave. See Deployment patterns and Security.
Golden set and outcomes to capture#
- Golden set: the worked examples in your published guidance, each with the expected outcome and the criterion that decides it, plus past appeal cases. They double as the specification, and every proposed change is replayed against them.
- Outcomes: appeal results, corrections, inspection findings and time to resolution.
- Overrides: caseworker overrides with a reason code.
- Linkage: the receipt and pack version on every decision, kept for your retention period.
Honest limits#
- Eligibility and triage policy must be authored as a pack; domain packs are Planned in the catalog.
- The core does not learn during evaluation. In an air-gapped site, learning arrives only as reviewed pack releases carried in.
- Reasoning, solvers and the learning loop run on the hosted Helixor platform and are in Preview and are unavailable inside an air-gapped site.
- Licenses cannot yet be host-bound or revoked (Planned). The decision service's own authentication is one shared token over plain HTTP; put an authenticating proxy with TLS in front of it.
Next steps#
- Pick one published rule
Write one eligibility or triage rule in the Playbooks format, with its worked examples as the golden set.
- Plan the site
Read Deployment patterns and the Production checklist.
- Pilot
Follow Evaluating fit.