ENGINEERING INDEX / ENTRY 16
CASE 16 / CARE COORDINATION / IDEMPOTENT GENERATION
A nudge should not multiply.
Care needs recur, but rerunning a scheduler should not turn one stale item into a pile of duplicate reminders.
Source project: A Place to Show UpFocused integration tests passedReviewed September 25, 2026
How does a shared care reminder avoid creating duplicate work every time the generator runs?
02 / THE SYSTEM
Where the handoffs happen.
The tested generator creates one stale-size need and two reminders for two active connections. Repeating the same run creates neither a new need nor new reminders; children with no active connection are skipped.
- 01Inspect confirmed state
- 02Create one need occurrence
- 03Fan out to active team
- 04Skip repeated occurrence
What the record earns.
Stale need, team fan-out, repeat-run, and inactive-team checks passed.
- Observed receipt
- On September 25, 2026, APTSU reminder-generation tests passed within a 33-test integration/security batch.
- Source and scope
- APTSU app/services/reminder_generation.py and tests/integration/test_reminder_generation.py; dirty checkout HEAD 930369a at inspection.
04 / THE LIMIT
What this does not prove.
These SQLite fixture checks do not prove timed delivery, notification receipt, or absence of every duplicate under concurrent workers.
Where the work goes next.
Run a scheduler-and-dispatch rehearsal with restart/concurrency conditions and capture a private delivery receipt.