H.A.R.I. Deterministic Governance ENIT Propose a use case
For federations, leagues, clubs and match officials

Every consequential decision in football, taken on evidence — and reconstructible years later.

H.A.R.I. is a deterministic governance layer that sits between your data, your protocols and the people who decide. It never guesses: it answers ALLOW, DEFER — or names exactly what is missing. Football is the flagship vertical; the same kernel applies to other high-stakes domains.

Propose a use case See a worked example ↓
No NDA needed to start · Initial evaluation in writing · Reply within 5 working days
Deterministic kernel — live trace replaying
{{ kernel }}
same input → same output hash {{ hash }}
Who it is for — and what you can do today
01

Federations & leagues

Priority problem: contested decisions you cannot fully reconstruct afterwards — which evidence was seen, by whom, under which protocol.

Do now: pick one review protocol (VAR, disciplinary, return-to-play) and submit it as a use case.

Decision governance module →
02

Clubs & medical staff

Priority problem: return-to-play and squad-welfare decisions where protocol, load data and medical sign-off live in different places.

Do now: share your current protocol steps (no player data) for a written gap analysis.

Welfare & squad module →
03

Match officials & VAR units

Priority problem: the right angle, at the right second, to the right person — with a record that it happened.

Do now: request the Field Lab brief — role-based delivery on smart glasses, tested with amateur officials.

Smart glasses & field interfaces →
Worked example · simulated case

A VAR review, from input to recovery, in four steps.

Illustrative policy and data — not a real match. What matters is the shape: the kernel never produces a verdict without evidence, and never stops at “no” without saying what would turn it into ALLOW.

STEP 1t = 00:00

Input

Episode 71′ — possible handball. Bound to the episode: camera A, camera B, the review protocol (policy v4.2) and the named official on duty.

cam_A ✓ bound
cam_B ✓ bound
policy v4.2 ✓
official: named ✓
STEP 2t = 00:02

Missing evidence

Camera B's frame at the touch moment fails its integrity check — the feed dropped two frames. One precondition cannot be evaluated.

cam_A ✓ verified
cam_B ✗ integrity fail
policy v4.2 ✓
official: named ✓
STEP 3t = 00:02

SYSTEM_UNVERIFIED

The kernel does not guess from camera A alone. It emits a state, not an opinion — and writes to the chain exactly which input failed and why.

missing: cam_B @ touch
required: verified frame or
authorized alt. source
trace #01043 · signed
STEP 4t = 00:41

Recovery → DEFER → ALLOW

Broadcast angle C is an authorized source; it is bound and verified. The kernel re-runs: evidence complete, decision reserved to the named official (DEFER). On their signed call: ALLOW.

cam_C ✓ bound · verified
DEFER → official
ALLOW · signed
replayable from chain
Scope of “same input, same output”

Determinism holds for a fixed tuple: policy version, kernel configuration, input schema and the bound evidence set. Change any of these and you get a new, equally reproducible trace — never a silent drift.

States vs. advisory analysis

Only the kernel emits ALLOW / DEFER / SYSTEM_UNVERIFIED. Modules that read context — welfare, review quality, situational risk — return advisory indications to a named human. None of them produces a ranking or a score that the kernel acts upon.

Now try it yourself

Remove a piece of evidence. Watch the decision — and the way back.

Same illustrative policy as above. Toggle the preconditions; the kernel re-evaluates deterministically and names what is missing.

Scenario
Preconditions · {{ scenarioAction }}
Kernel outputpolicy v4.2 · deterministic
{{ outState }}

{{ outSummary }}

{{ recoveryTitle }}
{{ r.n }}{{ r.text }}
authority: {{ authority }}trace · signed · hash-chained
What it is

A deterministic governance layer.

Middleware between AI systems, data, sensors, APIs and the actions they affect. Same input, same output — by architecture, not by promise.

Read the full definition →
What it is not

Not a chatbot. Not a model. Not a scoring engine.

Not autonomous, not a surveillance system, not a consumer product. It is an institutional layer that preserves human authority.

See every negation →
Where it stands

Sealed core. Pre-audit in progress. Pilot not yet granted.

Copyright registered, architecture timestamped (SOV-2026-02-26), 13-point stress test passed, TÜV SÜD pre-audit under way. Field Lab: smart-glasses delivery tested with amateur officials. Stated plainly, nothing more.

Full status and what each claim means →
Flagship vertical

H.A.R.I. Football — governed intelligence across the entire game

Decision governance on evidence, forensic match review, multi-angle evidence fusion, smart assistant referee, welfare and squad, referee training and VAR quality review. VAR is one module among many. Reads context. Does not profile people.

Open the Football vertical →
Beyond football

The same kernel, other consequential domains.

Each reuses the same deterministic kernel, forensic chain and human-authority guarantees. Stated as potential where they are potential. All domains →

{{ v.tag }}

{{ v.title }}

{{ v.body }}

Open →
Extensions

Modules that extend the kernel without bypassing it.

SLAM XP Dormant value activationSponsor-funded environmental and territorial programs, governed by the same chain. FIELD Smart glasses & field interfacesRole-based information delivery for officials and responders. Context, not surveillance. API GOV API governance & provider managementEvery external provider enters through an authorized, audited integration.
Low-threshold first step

Propose a use case for an initial evaluation.

Not a commitment, not a sales call. Describe one decision you would like to govern on evidence; we reply in writing with whether and how the kernel applies, and what a scoped pilot would require.

Share without NDA
  • The decision you want to govern and who takes it today
  • Which protocol or rulebook applies
  • Which evidence sources exist (type, not data)
  • Your role and organisation
Requires mutual NDA
  • Kernel internals and policy encoding
  • Integration specifications and test results
  • Any real match, player or patient data
  • Pilot scoping and commercial terms