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 hosted MCP tools. An MCP connection can see only cloud-backed data that it 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 grant ownership or widen the member’s MCP connection.

Device notification scheduling, geofence monitoring, and other device-only behavior are not reproduced by a hosted integration. Attachment bytes use short-lived delegated URLs when an authorized MCP tool exposes that flow. The bytes do not pass through MCP.