# DECISIONS.md - Cron Override Checks

This file tracks decisions that should override scheduled cron actions.

## How It Works

Before any cron job takes an **external action** (sending emails, posting to social, making purchases), it should check this file first. If there's a matching override, skip the action.

## Active Overrides

```yaml
# Format:
# - action: "description of what to skip"
#   reason: "why"
#   expires: "YYYY-MM-DD" or "permanent"
#   added: "YYYY-MM-DD"

overrides: []
```

## Example Usage

```yaml
overrides:
  - action: "prospect_email:acme_corp"
    reason: "Rob spoke to them directly, no outreach needed"
    expires: "permanent"
    added: "2026-02-14"
  
  - action: "social_post:tradeify_launch"
    reason: "Delayed until DNS sorted"
    expires: "2026-02-20"
    added: "2026-02-14"
```

## Cron Implementation

Crons that send external messages should:
1. Read this file
2. Check if their action matches any override
3. Skip if matched, log that it was skipped
4. Proceed if no match

## Why This Exists

**The Dory Problem:** Cron jobs have no memory of main session conversations. If Rob says "don't email that prospect" in chat, the morning outreach cron doesn't know. This file bridges that gap.

---

*Added 2026-02-14 based on r/LocalLLaMA patterns*
