What a task actually contains

Confirmed against the production database schema.

Repeat: never, daily, every weekday, weekly, twice a month, monthly, yearly, or a custom interval like every 2 weeks

Stored but never shown or editable:

Category: action_item or follow_up. Set by the AI, surfaced only as a separate section on a recording's Actions tab ("Follow-up Required"). Cannot be filtered, changed or seen anywhere else.
Execution order: the AI's dependency ordering. Only used by the Actions tab's "Order" sort.
Transcript timestamp / segment: powers the "jump to this moment" button on the Actions tab.
Completed by / completed at: shown only on the recording's Actions tab ("Completed by <name>").
Section: a project-section link that no current screen writes to.
Email source fields: subject/from/snippet from an email-sourced task; nothing renders them today.
Source: where the task came from (transcript_extract, rant, ai_agent, support_agent, or blank for hand-made; older rows can carry a legacy external-agent value). Only visible indirectly, as the little sparkle icon on AI-created rows.
Three legacy reminder columns (reminder_enabled, reminder_minutes_before, reminder_sent_at) that the current app ignores completely: reminders live in a separate list field.

There is no: start date, estimate/time tracking, dependency link between tasks, attachment, custom field, or per-task permission.