B5 — Teacher sends a photo

Step 1 — Capture or select

Multi-select supported (§3.5 step 1). Teacher either opens the camera in-app or picks from the device's camera roll.

Selected:

Step 2 — Tag children

Roster MUST be filtered to children enrolled in the teacher's assigned classroom(s). A child from another classroom MUST NOT appear here (§3.5 step 2).

Photo 1 — tag

• [✓] [child A] — consent: all
• [ ] [child B] — consent: solo_only
• [✓] [child C] — consent: solo_only
• [ ] [child D] — consent: none

A tagged child from outside the teacher's assigned classroom is unreachable via the UI; if reached, treated as blocking error per §3.10 error case.

Step 3 — Consent check (B-Consent §3.10) — WARNING CASE

Teacher MUST take explicit action to proceed. Solo_only single-tag = permitted, no warning (§3.10 step 3).

Step 3b — Consent check — BLOCK CASE

Separate flow: a tagged none child blocks the entire send.

I-Consent-Block (§5.1): a PhotoTag with consent_evaluation = blocked MUST NOT generate any PhotoDelivery. Zero-tolerance.

[exact copy on which child is named vs. anonymized — spec §3.10 step 1 says "without disclosing other children's consent details unnecessarily" — the mock names the blocking child because the teacher needs to act on them; calibration signal]

Step 4 — Confirm & queue

On confirmation, each photo is written to an offline-tolerant local queue and the send UI returns control to the teacher immediately (§3.5 step 4). Teacher does not wait for upload.

Optional caption / Midday Heartbeat message

[message entry mechanism — Q6 open parameter, §5.4]. Options listed in the spec: teacher_typed, library_picked, ai_generated, ai_assisted, none. Calibration signal: Nelson + Allan decide Q6 before this surface is designed.

Send

Step 5 — Background upload (teacher-facing status per photo, AC7)

Underlying entity status values: queued, uploading, delivered, failed_retrying, failed_permanent (§3.5 step 5).

AC7 (new, tot-8ba spike): the teacher send view MUST display a per-photo upload-status indicator at all times, with distinct visible states for all five entity statuses. Silent background progress is prohibited.

Per-photo upload-status indicator (concrete UI element per AC7)

[teacher-facing labels — spec notes teacher UI "MAY label delivered as 'sent'" (§3.5 step 5); other labels are inferred from enum values]

AC8 — iOS Safari "keep tab open" banner (conditional)

AC8 (new, tot-8ba spike): on iOS Safari specifically, the send view MUST display a teacher-facing note whenever at least one photo is in queued, uploading, or failed_retrying. Motivation: iOS Safari cannot resume uploads in the background (no Background Sync / Periodic Sync / Background Fetch).

inference: the mock cannot actually user-agent-sniff (static HTML, no JS). The banner is rendered visible with the explicit conditional label above. A real implementation would:

• Detect iOS Safari at runtime;
• Show the banner iff any(photo.status ∈ {queued, uploading, failed_retrying});
• Hide once all in-flight photos reach delivered or failed_permanent.

Step 6–7 — Fan-out and notify

On server-side persistence, the system creates per-recipient PhotoDelivery records for each guardian linked to each tagged child, subject to the consent evaluation performed at send time (§3.5 step 6, I-Consent-AtSend). Guardians are notified per their preferences (real-time or daily digest). See B6.

AC2 (revised 2026-04-24 per Q2 Amendment): a photo queued offline MUST reach a guardian within 10 minutes of the teacher next actively opening the Littlereach app after connectivity returns — bounded-by-web-platform form, since iOS Safari lacks Background Sync / Periodic Sync / Background Fetch (see spike tot-8ba RESULTS.md, open-questions.md §Q2 Amendment 2026-04-24).

AC3: a photo with a none-consent child tagged MUST NOT reach any guardian under any circumstances.

AC6: a failed_permanent photo is never deleted from the device until the teacher confirms.

Error — no wifi, no cellular

Photo sits in queue with status queued. Teacher sees a clear queued indicator — no silent failure (§3.5 error cases, AC7).

Upload resumes automatically when connectivity returns. On iOS Safari specifically, the upload cannot resume while the tab is backgrounded or closed; it resumes on the next active app open (AC2 revised, AC8 banner applies).

Error — upload fails after max retries

Parameter: 10 retries over 24h (spec). Status moves to failed_permanent. Teacher sees this clearly and is offered a manual retry. Local copy MUST NOT be deleted until a successful delivery is confirmed.

Audit — consent evaluation stamp (I-ConsentAudit, §5.1)

Every PhotoTag gets exactly one immutable consent_evaluation value: permitted | warned_override | blocked, stamped at send time. Queryable for audit throughout the photo's lifetime.