Skip to content

STP-ALERT-001 Alert Drill and Notification Protocol

Status: Final draft prepared for handoff (pending review)
Version: 0.9
Owner: BionicLoop engineering
Prepared by: BionicLoop engineering Reviewer: ____
Approver: ____
Decision date: ____
Effective date: ____
Baseline freeze SHA: ____
Last updated: 2026-04-06 15:20 EDT

Revision History

Version Date Author Summary of Changes
0.1 2026-03-27 Engineering Initial alert protocol draft
0.9 2026-04-06 BionicLoop engineering Added handoff-ready document-control metadata for the software package

1. Purpose

Define the manual/system protocol for alert wording, escalation, background notification behavior, and operator-observed alert handling.

2. Scope

This protocol owns alert checks that require operator observation or live notification behavior rather than pure deterministic code execution.

Primary focus:

  • TV-ALERT-005
  • TV-ALERT-012
  • TV-ALERT-013

Supporting system/manual execution may also cover selected aspects of:

  • TV-ALERT-006
  • TV-ALERT-007
  • TV-ALERT-008

3. References

4. Roles

  • Author: BionicLoop engineering
  • Executor: engineering / QA / clinical operator
  • Reviewer: quality / design assurance
  • Approver: submission-quality owner

5. Prerequisites

  • Real device with notification permissions enabled
  • Baseline phone for study hardware runs: iPhone 17e
  • Ability to induce or simulate required alert conditions safely
  • Known alert inventory baseline and expected wording

6. Procedure

6.1 Protocol-Required Alert Presence

  1. Trigger or otherwise enter each required alert condition.
  2. Verify correct title, message, severity, and recommended action.
  3. Verify user-facing response guidance is actionable and consistent with protocol language.

6.2 Background Notification Behavior

  1. Put app into the appropriate background state.
  2. Trigger alert conditions requiring notification.
  3. Verify:
  4. notification is or is not delivered per policy
  5. duplicate/throttled behavior is correct
  6. tap-through returns to the correct app surface

6.3 Algorithm Stepping Interrupted

  1. Induce step interruption for longer than the approved threshold.
  2. Verify alert timing and visible blocker detail.
  3. Verify stronger native CGM/pump alerts remain primary where required.
  4. Restore stepping and verify clear behavior.

7. Pass / Fail Criteria

  • Pass when alert presentation, timing, and notification behavior match protocol and requirements.
  • Fail when wording, delivery, precedence, or clear behavior diverges.

8. Evidence to Capture

  • screenshots of active alert state
  • screenshots of Alert Center / recent-clear state if applicable
  • notification screenshots
  • tap-through routing notes
  • timestamped operator log
  • STR target path:
  • Docs/Quality/Evidence/Formal/STR-ALERT-001/<run-label>/

9. Traceability

TV-* ID Alert Topic
TV-ALERT-005 Protocol-required alert presence/actionability
TV-ALERT-012 Step interruption issue/clear without masking stronger alerts
TV-ALERT-013 15-minute interruption timing and blocker detail