Product model

Tasks and Lists

A Task is the main unit of work. A Task may have one level of steps, represented by child Tasks. Notes, reminders, comments, tags, attachments, settings, and prayer-aware schedules each have their own rules.

A List groups Tasks and can be shared. Existing wire identifiers retain categories:read, categories:write, and category-shaped implementation names. In public prose, the resource is a List. This naming difference does not change a scope or wire field.

Comments are flat. A comment does not create a nested reply tree.

Local and cloud behavior

The app reads and writes local data first. Personal data that remains only on a free account’s device is absent from REST, MCP, Event Log, and webhooks. An external integration can see only cloud-backed data that its connection is authorized to read.

A free member may participate in another person’s shared cloud-backed List when the product’s sharing rules allow it. Hosting and attachment storage follow the List owner’s paid entitlement. Membership does not transfer the owner’s retained event history to the member.

Device notification scheduling, geofence monitoring, and other device-only behavior are not reproduced by a hosted integration. Attachment bytes use delegated signed URLs when a contract exposes that flow. They do not pass through MCP, and no REST byte path is implied without a generated route.