reminders: codify architecture in design docs #190

Closed
opened 2026-04-06 20:58:59 +00:00 by barrettruth · 1 comment
barrettruth commented 2026-04-06 20:58:59 +00:00

Summary

Update the design docs and decisions to reflect the approved reminder architecture.

Scope

  • supersede the earlier deferred-notifications stance
  • document reminders as a task subsystem
  • document channel/adapter split
  • document DB-backed worker and Signal beta status

Blocked by: #189

## Summary Update the design docs and decisions to reflect the approved reminder architecture. ## Scope - supersede the earlier deferred-notifications stance - document reminders as a task subsystem - document channel/adapter split - document DB-backed worker and Signal beta status Blocked by: #189
barrettruth commented 2026-04-06 22:32:03 +00:00

Completed in the local reminder design docs (.ai-docs/design.md and .ai-docs/decisions.md, including D042-D045) alongside the reminder backend rollout.

Completed in the local reminder design docs (`.ai-docs/design.md` and `.ai-docs/decisions.md`, including D042-D045) alongside the reminder backend rollout.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/delta#190
No description provided.