Execution Plan

Last updated: February 11, 2026

This replaces the old schedule with a traceable, checkbox-driven execution plan. Primary near-term objective is pregnancy-specific requirement integration with safe runtime behavior on real G7 + DASH hardware.

Working Constraints

Closed-loop guardrail: algorithm-driven dosing only (no manual bolus controls in study mode).

Done Criteria

A work item is only considered done when all are true: - Code is implemented. - Relevant tests are added/updated and executed. - Related docs are updated (Architecture, Requirements, RiskAnalysis, Docs/Quality/* trace docs).

Workstream A: Pregnancy Requirements Integration

A1. Algorithm parameterization for pregnancy mode

[ ] Confirm final pregnancy configuration constants with algorithm owner (targets, meal behavior, safety limits).
[ ] Implement target-set support end-to-end (90/100/110 policy as approved) with explicit runtime mapping.
[ ] Implement/verify meal controller pregnancy behavior (90% learned meal requirement) in algorithm path.
[ ] Verify insulin concentration and delivery quantum constants against DASH operational limits and study insulin assumptions.
[ ] Add requirement IDs and test coverage links in Docs/Quality/SoftwareRequirementsSpecification.md and Docs/Quality/TraceabilityMatrix.md.

A2. Input parity and degraded-mode behavior

[ ] Complete Marjorie parity slice for required input fields (including unavailable sentinels where intended).
[ ] Add explicit BG/fingerstick fallback path requirements and implementation decision (in scope this phase).
[ ] Define BG entry mapping into algorithm BGval and persistence/expiry policy for BG values used by runtime.
[ ] Define BG-triggered doWork behavior as a separate wake cause (bgCheck) with no future-step borrowing.
[ ] Validate CGM sanitization policy (<39 / >401 -> -1) against step-0 and step>0 behavior.

A3. BG check entry path (new)

[ ] Add Home BG-check UI flow (Enter BG) with guarded numeric entry, explicit submit, and clear validation messaging.
[ ] On submit, trigger runtime doWork for current due step only (expectedStep), never nextStep + 1.
[ ] Ensure BG check path is compatible with meal path but has no borrow semantics.
[ ] Define BG freshness window for runtime use and reject stale manual BG values.
[ ] Ensure BG source labeling is preserved in telemetry (manual BG vs CGM).

Workstream B: Runtime Reliability on Hardware

B1. Pump/CGM restore and reconnect behavior

[ ] Validate recent PumpStatusObserver reconnect refresh fix on real device across app relaunch + reconnect cycles.
[ ] Ensure home pod card reflects true state transitions without visiting Pod settings.
[ ] Verify G7 manager ownership/single-manager behavior after setup + relaunch.
[ ] Confirm no duplicate central-manager initialization side effects in startup/setup flows.

B2. Cadence and step continuity

[ ] Validate anchored step cadence behavior overnight with real CGM events.
[ ] Validate skip/catch-up semantics after wake gaps and relaunch.
[ ] Verify reset semantics always create a true fresh session.
[ ] Validate BG-check-triggered step execution when CGM wake is missing and cadence would otherwise stall.
[ ] Validate BG-check-triggered step execution when CGM wake exists but CGM values are unusable for algorithm input.

Workstream C: Safety and Fallback Logic

C1. Meal announce safety

[ ] Keep meal announce pump-ready gating explicit and tested (pump known, not delivering, borrow window valid).
[ ] Add test coverage for all meal unavailable reasons shown in UI.
[ ] Keep BG-check policy explicitly separate from meal borrow policy (BG check cannot borrow future slots).

C2. Pump-unavailable strategy

[ ] Finalize and document command-block behavior while continuing algorithm step execution with unavailable pump input.
[ ] Decide and implement policy for prolonged comm loss fallback mode transitions.

C3. Offline fallback (proposed feature)

[ ] Convert proposal into formal requirements (entry criteria, max duration, user messaging, recovery behavior).
[ ] Define fail-safe constraints before implementation.

Workstream D: Data, Telemetry, and Visualization

D1. Step data integrity

[ ] Ensure per-step records include required input/output/command/reconciliation fields for review and export.
[ ] Validate that zero-dose steps are retained and rendered correctly in charts/scrub and step listings.
[ ] Confirm meal-announced doses remain distinguishable in telemetry and charts.

D2. Export/collection path

[ ] Keep local CSV export as temporary development path only.
[ ] Define secure cloud telemetry upload requirements and phased migration plan.

Workstream E: Quality and Regulatory Readiness

E1. Traceability system

[x] Create Docs/Quality foundation (RA, SRS, SDD, SVVP, RTM, cybersecurity plan, SOP).
[ ] Add formal scoring and acceptance criteria to quality RA register.
[ ] Populate RTM with concrete evidence links for each completed feature/test.
[ ] Create STP and STR templates for repeatable execution/reporting.

E2. Cybersecurity and compliance

[ ] Build initial threat model and map controls to SRS-SEC-* and RA-* IDs.
[ ] Define PHI/PII handling expectations for telemetry and exports.
[ ] Add dependency/SBOM process notes for release-bound builds.

Workstream F: UI/UX (Separate Track)

[ ] Define stable IA for Home, CGM, Pod, and Settings flows with reduced setup dead-ends.
[ ] Confirm default landing behavior for CGM and Pod modal flows (setup vs settings) based on actual manager state.
[x] Restore explicit startup Cancel path for CGM and Pod setup modals, including persisted-manager/no-active-pod Pod case.
[ ] Document navigation/state transitions for onboarding, re-onboarding, and recovery paths.

F2. Status and interaction UX

[ ] Finalize Home card state language set and keep wording aligned with runtime logic (SRS-UI-001, SRS-UI-002).
[ ] Finalize meal-announce unavailable messages and retry timing wording (SRS-MEAL-003).
[ ] Ensure status cards and critical controls remain readable and actionable in light/dark modes.

F3. Visual and chart UX

[ ] Finalize chart behavior spec (range presets, scrub behavior, edge clipping, zero-dose visibility).
[ ] Finalize color/contrast targets for CGM, insulin, and meal-dose overlays for light/dark modes.
[ ] Add visual regression checklist for major Home chart/status layouts.

F4. Input ergonomics and accessibility

[ ] Validate profile-entry UX (weight lbs input, clear affordance, keyboard dismissal) against SRS-VAL-001.
[ ] Add VoiceOver labels/traits for status cards, chart scrub pills, and critical action controls.
[ ] Add Dynamic Type and minimum hit-target review checklist for primary screens.

F5. UI verification and traceability

[ ] Add/expand UI tests for critical safety states (No CGM, No Pod, Armed, Active, Aging, Stale).
[ ] Add manual usability test protocol IDs and link them in Docs/Quality/TraceabilityMatrix.md.
[ ] Capture screenshot evidence for each clinical-facing major UI state in test reports (STR-*).
[x] Auto-cancel meal composer on app background transition and verify with automated test (TV-UI-004).
[ ] Define and implement deterministic Xcode UI test fixtures (launch arguments/environment) for key runtime/UI states.
[ ] Add accessibility identifiers for all controls and state labels used by UI automation.
[ ] Add an automated UI smoke suite that covers navigation, setup modal dismiss/continue, settings entry, and meal announce sheet open/cancel paths.
[ ] Add automated verification for state-driven messaging and gating text (for example meal unavailable reasons).
[ ] Run UI automation in CI or pre-release gate with xcodebuild ... -only-testing:BionicLoopUITests test.
[ ] Define explicit UI automation boundaries (what remains manual/system-only on real hardware).

Workstream G: User Alerts and Escalation

G1. Alert source inventory and normalization

[ ] Build canonical alert inventory for OmniBLE, G7SensorKit, algorithm/runtime, and app safety policy alerts.
[ ] Define normalized alert model fields (source, severity, title, message, recommendedAction, timestamp, ackState, dedupeKey).
[ ] Define source-to-normalized mapping table and store in Docs/Quality/SoftwareDesignDescription.md.
[ ] Identify which alerts are informational vs actionable vs safety-critical.

G2. Alert presentation and UX behavior

[ ] Define delivery channels by severity (in-app banner, blocking sheet, persistent home card state, optional local notification).
[ ] Define alert precedence and suppression rules to prevent masking critical alerts.
[ ] Define debounce/coalescing rules for noisy transient events (for example normal DASH reconnect churn).
[ ] Define acknowledgement requirements (auto-clear vs explicit user acknowledgment).

G3. Clinical and protocol alignment

[ ] Map protocol-required alerts and response guidance to app alert IDs.
[ ] Add wording review pass for clinical readability and non-ambiguous action statements.
[ ] Define escalation path for unresolved critical states (including fallback mode messaging handoff).

G4. Verification and traceability

[ ] Add SRS-ALERT-* requirements and RA-011 hazard mapping in quality docs.
[ ] Add TV-ALERT-* unit/integration/system tests for alert generation, suppression, and clearing.
[ ] Add manual alert-drill test protocol (STP-ALERT-*) and evidence capture plan (STR-ALERT-*).
[ ] Add release checklist gate: no unresolved critical alert regressions.

Immediate Next 2 Weeks

Week of February 10, 2026

[ ] Validate hardware reconnect/state-refresh behaviors (pump + CGM) with logs.
[ ] Lock pregnancy parameter decisions with algorithm stakeholders.
[ ] Implement first pregnancy parameter slice (target mapping + tests).
[ ] Fill RTM entries for completed runtime safety policies.
[ ] Draft initial cross-source alert inventory (Omni, G7, algorithm/runtime).
[ ] Define first deterministic UI fixture set and accessibility-ID backlog for automation.
[ ] Draft BG-check requirements (BGval mapping, trigger behavior, no-borrow policy) and add to quality trace docs.

Week of February 17, 2026

[ ] Complete meal/pump unavailable policy tests on device.
[ ] Run overnight cadence verification and summarize outcomes.
[ ] Draft cloud telemetry migration requirements.
[ ] Prepare TestFlight-ready baseline checklist for clinical team preview.
[ ] Implement normalized alert model and first-pass Home alert presentation rules.
[ ] Implement first Xcode UI smoke suite and map TV-UI-* evidence in RTM.
[ ] Implement BG-check runtime trigger path and core test matrix for missing/invalid-CGM edge cases.

Parking Lot (Not Current Sprint)

[ ] Extended fallback execution (offline basal) implementation.
[ ] Expanded clinical dashboards and study-report exports.