design: Orbitals pattern -- task/maintenance countdowns that restart from completion #120
Labels
No labels
accessibility
backlog
beta-feedback
bug
duplicate
enhancement
feature-request
help wanted
invalid
needs-design
needs-triage
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Circuit-Forge/kiwi#120
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background
Spotted in r/audhd: a builder working on "Wallo", an anti-engagement habit app for ND brains. Their "Orbitals" mechanic is directly aligned with Kiwi's no-debt philosophy.
Orbitals definition: If a recurring task is set for "every 7 days", the countdown starts from when you actually do it, not from the scheduled date. It never accumulates debt. It just waits.
Thread: https://www.reddit.com/r/audhd/comments/1smxzje/i_got_sick_of_habit_apps_triggering_my/
Magpie opportunity: #2 (pending review -- reply drafted)
Kiwi relevance
Kiwi already applies this principle implicitly to expiry tracking -- "days remaining" counts from now, never shows accumulated overdue debt. But we don't have an explicit maintenance task layer yet.
Potential applications in Kiwi:
Design options
A. Implicit (no UI change): Treat all Kiwi time-based suggestions as orbital by default -- already true for expiry. Document this as a design principle, no new feature.
B. Explicit maintenance tasks: Add a lightweight task layer (separate from pantry items) where users can define orbital maintenance habits. Countdown shown in a widget or dashboard section. No streak, no debt, no calendar grid.
C. Orbital recipe cadence: Suggest "you haven't made [recipe] in X days" where X is measured from last cook date, not a fixed interval. Gentle, not guilt-inducing.
Notes