Feature: one reminder across enrolled screens #98

Open
opened 2026-09-28 22:01:48 +00:00 by aiko · 1 comment
Owner

Outcome

One Denpa-owned reminder has one logical identity across enrolled screens. Observed device availability influences where and how it is delivered; acting on it on either screen synchronizes the other.

Decisions

  • Active/idle/locked/offline are delivery signals, not an inferred sitting or seam. Operator-declared sittings and seams retain their meaning under ADR-0014.
  • Reuse authenticated device enrolment; do not confuse this with the existing broadcast tool-approval flow (ADR-0012).
  • Connected-device routing first. Native OS push when the Android application is not reachable requires a separately scoped transport decision, not an implied guarantee.

Slices

Tracked in linked child issues. Depends on the durable reminder feature. Call/screen-share privacy and speech suppression are a later feature package, not silently implemented by this one.

Done when

With desktop and Android connected, one reminder routes appropriately; an acknowledgement on either screen clears the same reminder on both. An unavailable screen does not silently mark delivery complete.

## Outcome One Denpa-owned reminder has one logical identity across enrolled screens. Observed device availability influences where and how it is delivered; acting on it on either screen synchronizes the other. ## Decisions - Active/idle/locked/offline are delivery signals, not an inferred sitting or seam. Operator-declared sittings and seams retain their meaning under ADR-0014. - Reuse authenticated device enrolment; do not confuse this with the existing broadcast tool-approval flow (ADR-0012). - Connected-device routing first. Native OS push when the Android application is not reachable requires a separately scoped transport decision, not an implied guarantee. ## Slices Tracked in linked child issues. Depends on the durable reminder feature. Call/screen-share privacy and speech suppression are a later feature package, not silently implemented by this one. ## Done when With desktop and Android connected, one reminder routes appropriately; an acknowledgement on either screen clears the same reminder on both. An unavailable screen does not silently mark delivery complete.
Author
Owner

Child slices: denpa#99 expiring desktop availability + denpatou#62 durable reminder → denpatou#65 connected-device routing/shared acknowledgement → denpatou#66 bounded mobile escalation. Native OS push, call/screen-share privacy and speech policy are explicitly separate follow-ups.

Child slices: denpa#99 expiring desktop availability + denpatou#62 durable reminder → denpatou#65 connected-device routing/shared acknowledgement → denpatou#66 bounded mobile escalation. Native OS push, call/screen-share privacy and speech policy are explicitly separate follow-ups.
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
aiko/denpa#98
No description provided.