Files

2.5 KiB

Naming conventions

Names are differentiator-first so a folder sorts into its matrix and a display tool can key on the tokens.

Canon frames (table-facing)

<Time> <Weather> <Letter> Exterior <Place> [<View name>].jpg
<Time> <Weather> <Letter> Interior <Place> <Room>.jpg
  • Time: Day | Sunset | Night (add Morning only where a view's day light is a morning by decision).
  • Weather: Dry | Rain | Snow (light) | Snow (medium) | Snow (heavy) | Blizzard | Heavy Blizzard | Ice Fog. Files already named plain Snow are Snow (light) and are not renamed.
  • Letter: the camera, A, B, C ... stable for the life of the place. Letters can change at promotion if a review set used working letters; record the mapping in the place's truth file.
  • Examples: Day Dry A Exterior Library Approach.jpg, Night Snow (heavy) B Exterior Stonehaven Lodge.jpg, Evening Packed A Interior Grimfrost Taproom.jpg (population cells use <Hour> <Density> in the Time/Weather slots).

Working files (lane folders)

plates/<V>_mass.png  _depth.npy  _oid.png  _cls.png  _cam.json  _people.json  _landmarks.json
out_<tag>/<V>_<pass>_t<k>.png        pass = day | sunset | night | Day-Rain | Sunset-SnowLight | Morning-Packed ...
out_<tag>/qc/gate_out_<tag>.json, <id>_geo.jpg, <id>_figs.jpg, <id>_figzoom.jpg, CORNERS-<tag>-<pos>.jpg
jobs_<tag>.json + jobs_<tag>_PROMPTS.md
picks.json                           {"V": {"day": "<id>", "sunset": "<id>"}}
REPORT.md                            the lane's deliverable; the hand-off is its path

View keys <V> are <Letter>_<slug>: A_first_view, C_gate_approach, R02_hall_from_door.

Place folders (canon)

<Place>/
  <place>-truth.md          what is canon (map-derived), what is PROPOSED, the camera letters and their meaning
  Exterior/                 the matrix frames
  Rooms/<Room>/             empty masters, population cells, scenes
  .sources/<DATE>-<lane>/   plates, picks, gate JSON, the prompts used, the REPORT (so a ruling is one edit + re-render)

The report

Every run writes REPORT.md first and hands back its path. Sections, in order: Problem (one paragraph); Why (two levels); What was built (every number a named constant and where it lives); Picks with their gate numbers; Failures found and fixed; PROPOSED items (each with "if you rule otherwise, change X and re-render Y"); Open questions; Not done and limits; Cost (scripts/cost.py: calls accepted and rejected, dollars, API minutes, local GPU minutes); How to re-render after a ruling (the exact command chain).