H.A.R.I.
Extensions / 3.2

Smart glasses & field interfaces.

The right information, to the right person, at the right moment, in the right role. Nothing else. Surveillance and facial recognition are excluded by architecture.

01The four-rights principle

The smart-glass field interface, where authorized, exists to deliver one thing: the role-bound informational payload that the wearer's role requires for the moment they are in. Four properties, all of them required:

1

Right info.

The payload is what the role's policy declares for the moment — and not the operator's full available data.

2

Right person.

Delivered to the named, authenticated wearer assigned to the role, not to a generic "user."

3

Right moment.

Within the policy-defined operational window for the role's current phase, not whenever a model fires.

4

Right role.

Bound to the role the wearer is currently fulfilling — not aggregated across the wearer's history.

02Cognitive overload prevention by design

Field interfaces fail catastrophically when they overwhelm the wearer. The architectural commitment is to under-deliver rather than over-deliver: if the policy does not call for an item to be on the surface, it is not on the surface. The kernel actively suppresses payloads that would exceed the role's per-moment information envelope. Saturation is treated as a governance failure, not as a UX inconvenience.

03Roles supported

Each role's information envelope is defined by the vertical's policy. A non-exhaustive list of roles for which the architecture is engineered:

  • Officials (referees, fourth officials, VAR officials).
  • Technical staff (coaches, performance staff).
  • Medical (team doctors, paramedics, on-call clinicians).
  • Analysts (tactical, performance, match-control).
  • Stadium safety (lead, deputies, phase coordinators).
  • Stewards (zone leads, evacuation aides).
  • Emergency operators (medical command, security command, civic liaison).

04Integration model

The field interface integrates with the underlying authorized hardware ecosystem when access is granted — federation-issued devices, league-issued devices, club-issued devices, public-safety-issued devices. The integration is governed under the same provider-management discipline as any other authorized integration. See API governance & provider management.

05Not for surveillance, not for facial recognition

The field interface is engineered explicitly against the surveillance use case. It does not perform facial recognition. It does not identify attendees. It does not feed identity payloads into the chain. Where the role's policy requires identity information (for example, the wearer's own credential), the identity is delivered to the wearer alone and is not retained beyond the active session.

Architectural commitment

The smart-glass interface is governance-output, not surveillance-input. The directional posture is structural: signals flow out to the wearer; signals do not flow in from the wearer's environment for identification, profiling, or scoring purposes.

Status

Architecture-validated for the role-bound field interface model. Pilot-ready when scoped with the operational principal whose mandate covers the deployment.

Back to top