How Frame works

The thirteen things, named.

AI carries the deterministic eighty per cent of post-capture. The five to ten per cent that's actually creative stays human. What follows is every step, numbered, with the part the agent decides on one side and the part you own on the other.

Pipeline · shape

Read it like a table of contents that's been edited. Stages 0–2 are gates— they reject heavily so the rest of the pipeline never sees most of the day's frames. Stages 3–5 are filtering, ranking what survives. Stages 6–7 are enrichment — adding metadata and develop settings. Stages 8–9 are the human hop. Stages 10–12 are delivery. Discover is stage zero because it precedes ingest and never touches pixel data; you can re-run it any time without consequence.

#stagewhat it doesstatus
00discoverWalk a library, propose events from EXIF — never copy a byte.real
01ingestMaterialize an accepted event: copy RAW, write sidecars, build previews.stub
02cullFirst-pass binary reject — out-of-focus, blown exposure, accidental capture.stub
03groupCollapse bursts. Pose-aware — left-looking and right-looking go to separate groups.stub
04scoreOne to three stars on the survivors, weighted by genre.stub
05heroPromote a few to four and five stars — memorable, story-defining, print-worthy.stub
06keywordAuto-keywords. Privacy flag on unidentified minors by default.stub
07developGenre baseline preset. Anchor-and-sync clusters. XMP only — never pixel writes.stub
08refinePer-hero refinement, interactive. The 5–10% the human owns.stub
09retouchConditional pixel-level cleanup — zoo fence, portrait skin. Genre-gated.stub
10sequenceNatGeo arc — opener, build, hero peaks at two-thirds, quiet close.stub
11exportRender per output preset — web, print, social, slideshow.stub
12deliverUpload to gallery host, seal the event, archive.stub

This page suite will grow as each stage lands real implementation. Today, only discover is documented in depth — the rest exist as design notes in the agent repo and will land here one by one as the code does.