SENTINEL
The Institutional Firewall

Data Integrity.
Absolute Neutrality.

Sentinel is not a medical device. It does not diagnose, treat, or store patient records. It is a logistical router governed by a mathematical air-gap, designed to protect both the patient's clinical data and the staff's operational privacy.

The Non-Clinical Air-Gap

Article 10 of the Constitution mandates that Sentinel's operational constraint-engine is mathematically incapable of processing clinical variables. It does not receive blood pressure, lab results, or diagnostic codes.

It processes only time, location, role, and pre-authorised priority tags. This structural separation constitutes permanent legal proof that Sentinel is a logistical router, not a medical device—eliminating FDA, CE, and CDSCO regulatory burdens.

// The Operational Constraint
f(time, location, role) only.
∀x: x ∉ {clinical_vars}

What Sentinel Processes

Room Number & Floor
Event Timestamp
Responsible Role (e.g., 'HK Supervisor')
Task State (Vacant, Cleaning, Ready)
Blocker Category (e.g., 'Linen')

What Sentinel Strictly Refuses

Patient Name
Diagnosis / ICD Codes
Vital Signs / Lab Results
Billing Amounts
Individual Staff Names (See Labor Shield)

Cryptographic Provenance

A forensic record that can be altered is not a forensic record. Article 30 mandates that every operational event is cryptographically signed and chained to the previous event, making retroactive falsification mathematically impossible.

Append-Only Event Store

Data is written once and never deleted or modified (WORM). The ledger is the ground truth.

HMAC-SHA256 Signatures

Every device generates a unique signature. Unsigned or tampered data is automatically quarantined.

Hash Chain Integrity

Each event contains the hash of the prior event, creating an unbreakable chain for forensic audits.

Article 36: The Labor Shield

A real-time operational system must protect frontline staff from surveillance and punitive use of their data. Sentinel satisfies this by separating custody of evidence from custody of identity.

Role Sovereignty (P7)

Accountability maps to a Role_ID, never to an individual name. The system records "Housekeeping Supervisor delayed response," not "Rohan delayed response."

Actor_Role_ID: HK_SUPERVISOR
Actor_Token: TKN_9F3A7C

The Prohibition on Punitive Use

Client institutions are constitutionally forbidden from using Sentinel data for routine performance management or punitive discipline. The data is for operational coordination, not for HR surveillance. If a delay occurs, the log proves whether the staff member was notified, not who to punish.

"The system cannot be used as a tool for individual performance management, making it politically deployable in unionised and government hospital environments."

Data Sovereignty & Exit

Article 7 (Stakeholder Protection) guarantees that no hospital is ever locked into Sentinel. The operational data belongs to the institution that generated it.

Freedom from Lock-in

Hospitals can export their complete operational event history in a standard, non-proprietary format (JSONL, Parquet) at any time.

Continuous Operation

Once embedded, the interruption of Sentinel constitutes an operational emergency. The infrastructure is designed for 99.99% uptime.

Read the constitutional firewall.

The Non-Clinical Air-Gap and the Cryptographic Provenance Standard are enshrined in Part I: The Immutable Core of the Constitution.

Read Article 10 & Article 30