How it works
The workflow, examples and limits behind every tool.
Household ↗
A task repeats every entered number of days from its anchor date. The first owner starts the rotation.
Example: A weekly task anchored on Monday appears every seven days.
Up to 12 members and 60 tasks. This is a local household plan without invitations or notifications.
Weekly rota ↗
With rotation on, occurrence n goes to member (first-owner index + n) modulo member count.
Example: Alex then Sam alternate a daily task when they are the only two members.
Assignments are deterministic rather than an optimized fairness score. Member-order changes recalculate rotations, including past weeks.
Completion tracker ↗
Completion belongs to the task ID and scheduled date, not a single repeating checkbox.
Example: Completing Tuesday’s dishes leaves Wednesday’s dishes unchecked.
Counts measure completed tasks, not effort or quality. There is no household surveillance or remote tracking.
Print & backup ↗
JSON retains members, task rules and dated completion records. Import asks before replacing local work.
Example: Export before clearing browser data or moving to another device.
No cloud sync. Shared-device users can see locally saved names and tasks.
Local work, explicit limits
Each workspace reports its input and file limits. Imports validate the supported format before asking to replace saved work. Plain text is displayed as text, never executed as markup. Both languages use the same tools; the root address always opens in English, with Chinese under /zh/.