Agentic Guardrails Human In The Loop Gates Escalation

An agent has a queued task to change a patient's metformin dose from 500mg to 1000mg, classified as high-risk. Due to a fault in the orchestration layer, the EHR write-back call is dispatched without an approval token in the acti…

The data-layer enforcement interceptor (independent of the orchestration layer) hard-rejects the EHR write request before any record mutation occurs. Any partially begun state changes are rolled back atomically. A COMPLIANCE_VIOLATION event is emitted to the compliance audit log within 5 seconds, c…

An agent is processing a risk-stratified care queue of 50 patients. It obtained valid approval token TOK-001 for a care plan modification for PAT-00201. Due to a patient-iteration bug, when the agent advances to the next record i…

The enforcement layer extracts the patient identifier from the token's cryptographic binding and performs an exact match against the action's target patient_id. On mismatch, the action is hard-rejected. TOK-001 is immediately invalidated and cannot be reused for any patient or action. A WRONG_PATIE…

A care manager reviews a risk-stratified worklist and approves a care plan goal addition for patient PAT-00901. The system issues token TOK-006 cryptographically binding: action type 'care-plan-modification', patient PAT-00901, a…

The enforcement layer validates all binding parameters — action type match, patient ID match, plan delta hash match against the submitted payload, approver identity, and expiry check against server clock — and all checks pass. The EHR write for PAT-00901 executes atomically with the specified plan …