E1 — Decision Outcome Journal (follow-up tracking)

[ColdByDefault]

Context

Decisions are logged but never revisited. A real chief-of-staff tracks whether decisions turned out to be correct and learns from them. This builds a personal accuracy log over time.

Schema changes

Add to Decision model:

followUpAt      DateTime?   // When to review this decision
outcomeRating   Int?        // 1-5: how good was the decision in hindsight
actualOutcome   String?     // What actually happened
reviewedAt      DateTime?   // When the review was completed

New tool: review_decision

• Parameters: decisionId, outcomeRating (1-5), actualOutcome (string), optional followUpAt
• Updates the decision record
• minTier: "pro"

Nudge integration

The overdue nudge cron should also check for decisions where followUpAt has passed and reviewedAt is null, and emit a notification prompting review.

Files

• prisma/schema.prisma — add fields to Decision + migration
• lib/decisions/review.logic.ts
• lib/tools/registry/decisions.registry.ts — add review_decision
• lib/tools/handlers/decisions.handler.ts — add handler

Acceptance Criteria

• User can log "the mobile-first decision turned out to be the right call, 5/5" via the LLM
• followUpAt triggers a notification via cron
• Outcome rating (1-5) is stored and visible in the decisions UI
• Reviewed decisions show a visual indicator in the UI

[ColdByDefault]

Soft dependency on: #80 (C1 — Implement overdue tasks nudge logic)

E1's follow-up nudge (notify when followUpAt has passed) hooks into the same overdue cron loop built in C1. E1 can be developed independently but the nudge integration requires C1 to be merged first.