Tasks, status & identity

Features and tasks

Plan in features, then nest tasks under them.

• Feature — a slice of product value
• Task — an executable unit

{
  "features": [
    {
      "title": "User profile settings",
      "planned_at": "2026-08-07T15:00:00Z",
      "started_at": null,
      "in_review_at": null,
      "done_at": null,
      "blocked_at": null,
      "deferred_at": null,
      "cancelled_at": null,
      "notes": "Settings page + API.",
      "tasks": [
        {
          "title": "Add profile API endpoint",
          "local_id": "task-add-profile-api-endpoint",
          "cloud_id": null,
          "planned_at": "2026-08-07T15:00:00Z",
          "started_at": null,
          "in_review_at": null,
          "done_at": null,
          "blocked_at": null,
          "deferred_at": null,
          "cancelled_at": null,
          "notes": null
        }
      ]
    }
  ],
  "tasks": []
}

planned_at set = planned work. planned_at: null = discovered mid-flight.

Titles and notes (reduce ruthlessly)

Peacae is status and orientation, not a document store. Prefer less text on the board.

• title — One short action line (aim ≤ 80 characters). What to do, not how.
• notes — Default to null. Only when timestamps aren’t enough: blocker + need; one-phrase review; decision pending.
• Hard cap — One short phrase or one sentence (aim ≤ ~120 characters). No paragraphs or history dumps.
• Do not paste PRs, chat, logs, or file contents into title / notes. Replace or clear (null) — never append.

Status = latest timestamp

Seven columns; current status is the most recent non-null one. There is no separate status string.

Do not overwrite history, delete rows, or invent status strings.

Identity

Never rename or duplicate local_id. Treat cloud_id and synced as Peacae-managed.