Folder Recipe
A blue-hour photographic archive room leading toward a single amber folder marker

Local archive protocol

The right recipe,
waiting in the folder.

Stop carrying processing intent in your head. Put the editor profile and the reason beside the photographs—plain text, portable, inspectable.

Install the CLI Inspect a manifest

Reads folder metadata. Never alters originals.

One small manifest

Any editor explicitly mapped

Zero pixels changed

Archive rhythm

Decide once. Verify in context.

Each folder can set its own rule or inherit the nearest parent. You can see which one applies before opening an editor.

  1. 01

    Record

    Map editor names to exact profiles and note why this shoot differs.

    folder-recipe init ./shoot …
  2. 02

    Inspect

    See direct versus inherited intent alongside extensions, count and size.

    folder-recipe inspect ./shoot/selects
  3. 03

    Carry

    Export a checked list for a mixed archive before the first import.

    folder-recipe checklist ./archive

Browser light table

Read the intent. Nothing uploads.

Choose or drop a `.photo-recipe.json`. Parsing happens in this tab and the file is never stored.

Place a manifest on the table

JSON only · processed locally

Waiting for a manifest

No recipe on the light table

Select the sample to see mappings, heuristics and the folder note in one view.

Start local

A small tool, not another catalogue.

terminalfolder-recipe 0.1.0
cargo install --git https://github.com/B-Divyesh/sf-folder-recipe-switcher

folder-recipe init ./portraits \
  --name "August portraits" \
  --map rawtherapee="Portrait neutral v3" \
  --camera "Fujifilm X-T5"