← 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

Approach A vs B

FOS-first (add photos_first_cached_at to FOS + null-guard root-fix + backfill there, DAP copies) vs DAP-only (DAP derives from FOS audit_logs, no FOS change)? A is canonical/permanent but needs a FOS prod deploy; B touches no legacy code but leaves the overwrite bug in place. Recommend A given you liked it and the brief lives in the FOS project.

your call

A — FOS-first (recommended)

B — DAP-only

Start B now, do A later

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