← decisions

Decision

A single call, in full — the subject it hangs off, its linked context, and the metadata around it. Answer here and the daemon that asked pulls your answer and carries on.

tdr/thedarkroom from brief #54 for · anyone

FOS migration OK?

If Approach A: are you OK running a Laravel 4.2 migration to add a column on the ~1M-row FOS orders table (online/INSTANT DDL in a low-traffic window) plus a ~3-line edit to the hot import path in Order.php, shipped via staging→cherry-pick→master→Forge and coordinated with Daniel? And is the column name photos_first_cached_at good?

your call

Yes, proceed with FOS migration

Yes but different column name

No — avoid touching FOS (use B)

subject

brief #54 fos_imported_at / photos_first_cached_at — canonical "first import into FOS" (customer-delivery) timestamp + Uploaded→Delivered lag # fos_imported_at — canonical "first import into FOS" (customer-delivery) timestamp ## Goal Give every order an accurate **"first time its photos were imported/cached into FOS"** timestamp — the real *customer-delivery* moment (FOS finished caching the photos and fired the "Order Ready" alert). Surface it on DAP as `orders.fos_imported_at`, and report the **Uploaded → Delivered** lag on the /admin Lab Dashboard. This is the "Imported/Delivered" milestone from Solo todo **514** (active). It is DISTINCT from `uploa...

metadata

type: single_choice
status: open
project: tdr/thedarkroom
asked by: claude-code
round: 1
asked: 3 days ago