0062 — Trello is retired, and Smith tracks no tasks after it

• Status: Accepted 2026-10-16 (Gera, in session "trello").
• Date: 2026-10-16
• Deciders: Gera. The cut order and the slicing are the session's; recorded here per ADR-0004.

Context

Trello was the fleet's shared ticket and task store: the PropFlowAi Product board (8ChjkMJi), 3,201 cards (1,224 archived), 2,213 comments, 12,824 actions between 2026-02-23 and 2026-10-16. Smith wrote to it from several places, read from it in several more, and two of those readers fell back to Keychain credentials.

The trigger was volume. Measured on the board, 2026-09-15..10-15: 400 cards created, of which 379 were filed automatically from Zoom meeting recaps (standup_recap → standup_tasks), 7 to 30 per meeting. Gera: "Agent Smith creates tickets on Trello… I wanna stop it", then "we're gonna delete Trello entirely".

Decision

1. Trello is deleted. Before anything is cut, the whole board is archived, lossless and verified: ~/code/datasets/{raw,derived}/trello-2026-10-16/ on the mini (not a git repo, because it holds meeting quotes and customer names), and one zip in Gera's Drive. A future session reviews the archive; nobody reviews it now.
2. After Trello, Smith files nothing anywhere.
   • A bug report in a #tickets-* channel stays a Slack thread.
   • 👍 on a task proposal does nothing.
   • The per-person Tasks, Backlog and Unassigned canvases are retired, as are the #tickets-* type canvases.
   • Meeting action items are listed on the recap head and filed nowhere.
   • Gera chose this over moving them to Plate. Plate stays Trinity's surface, and this ADR does not extend Smith onto it.
3. Order of the cut — code first, credentials last, the board last of all.
   1. Every Smith path that reads or writes Trello is removed and deployed.
   2. Then the credentials go: TRELLO_* in .env.local, the trello-api-key / trello-api-token Keychain items, and the Vercel env.
   3. Then the token is revoked at Trello. That is the falsifier: a missed caller fails loudly rather than reading quietly.
   4. Only then does Gera close the board, and delete it a week later. Closing is reversible and deleting is not.

Consequences

• The order prevents a specific failure. Closing the board or pulling the key first would have turned Smith's 07:00 morning queue (trello_digest, tasks_done_sweep) into a daily alert, frozen the Tasks canvases, and made the #tickets-* intake fail at the person reporting a bug.
• Code comments that cite Trello <shortLink> stay resolvable. Look the shortLink up in the archive's index.csv.
• Watch the ✅ reaction in former ticket threads. Removing the ticket-reaction handler must not let a ✅ there reach the merge-approval fallback. That fallback once armed auto-merge on an unrelated PR (old-repo #3724). The reactions PR pins this with a test.
• trello_writes_retired() is not the lever (transcript_router.py:136, the TRANSCRIPT_ROUTER_ENABLED flag). It also arms Trinity's never-run placement routing, and on Smith's seat it never covered the meeting path. The paths are removed instead.

Implementing PRs (agent-smith)

• #1179: meetings stop filing cards; action items ride the recap head.
• #1181: unblocks main (an unrelated stale fence baseline).
• #1183: the steward stops reading This Week.
• #1185: Fede's brief drops the decision cards and Board pulse.
• Separate PRs remove the morning-queue steps and the co.propflow.trello-bridge daemon, the brain's trello_cli instructions and #tickets dispatch, and the Trello-backed reactions and routing. The remaining Trello code is deleted last.