# ⚠️ DEPRECATED — DO NOT USE

**This file is deprecated as of 2026-02-20.**

All corrections are now stored in the structured system:
```
/agency/corrections/COR-XXX.yaml
```

## Why?

1. **Structured format** — YAML with consistent schema
2. **Indexed** — `_index.json` enables fast retrieval
3. **Triggers** — Keywords auto-surface relevant corrections
4. **Tracking** — `times_applied`, `confirmed_by` fields

## To Add New Corrections

Use the `corrections-retrieval` skill or create directly:

```bash
# Option 1: Let detection system create draft
python3 skills/corrections-retrieval/capture.py "username" "message" "context"

# Option 2: Create YAML directly
# Copy template from existing COR-XXX.yaml
```

## Migration Complete

The following were migrated to COR-027 through COR-034:
- QA Workflow Not Applied Immediately → COR-027
- Landing Page Differentiation → COR-028
- Video Style Preferences → COR-029
- No Design Research Before Building → COR-030
- Package Manager Standard → COR-031
- Production Deployment Method → COR-032
- Browser Profile Setting → COR-033
- Symphony deployment → COR-034

---

*Deprecated by: loewe + ARIA*
*Date: 2026-02-20*

### 2026-02-19 | Raven | GCP API Access
- **What I did:** Said OAuth client redirect URIs couldn't be modified via API/CLI and gave up after seeing "API not enabled" errors
- **What was wrong:** I stopped at "API disabled" instead of trying to enable it. The IAP API (iap.googleapis.com) allows creating OAuth clients programmatically
- **Correct approach:** When told "you have access via service account" — try ENABLING the relevant API first (`gcloud services enable <api>`), don't assume disabled = unavailable
- **Key learning:** IAP API (`iap.googleapis.com`) → can create OAuth 2.0 clients via `POST /v1/projects/{project}/brands/{brand}/identityAwareProxyClients`

### 2026-02-24 | Alex | Copy — Banned Sentence Patterns (Overture)
- **What I did:** Wrote "That's not churn. That's timing." and "This isn't a churn problem — it's timing." on overtureinsights.com
- **What was wrong:** Both are explicitly banned sentence patterns per CSaaS brand rules. Also included em dash.
- **Correct approach:** Say what you mean directly. "Budget pressure, not product failure." / "Budget cycle, not retention."
- **Systemic fix needed:** When a new copy rule is added, audit ALL live pages immediately — don't wait for a human to catch it.

### 2026-02-23 | System | Image Generation
- **What I did:** Used / would use DALL-E (OpenAI) for image generation
- **What was wrong:** OpenAI image generation is NOT to be used
- **Correct approach:** Use nano-banana-pro (Gemini) exclusively for ALL image generation:
  ```bash
  uv run /home/linuxbrew/.linuxbrew/lib/node_modules/openclaw/skills/nano-banana-pro/scripts/generate_image.py \
    --prompt "your prompt here" --filename "output.png" --resolution 1K
  ```
  In Next.js API routes: use `child_process.execAsync` to call the script, save to `/tmp/<app>-images/<timestamp>.png`, serve via `/api/images/[filename]/route.ts`. Text/caption generation can still use OpenAI.

### 2026-02-26 | loewe | Brandcast video scene direction
- **What I did:** Generated 6-scene Overture video mixing human + abstract + environment scenes (data glow, detection arcs, cyan-lit empty desk)
- **What was wrong:** Abstract/environment-only scenes look ugly — visually incoherent with the human scenes
- **Correct approach:** ALL Brandcast video scenes must be grounded in human presence or natural environments. No abstract data viz, no particle effects, no digital overlays, no "environment only" CTA scenes. Even the closing CTA beat needs a human in frame.
