Plan a shoot end to end in one place — concept and shot list, model and location bookings, call sheet, budget and release status. The project record seeds every downstream .shock module.
Drop a plan-*.json here to open it. Everything stays local — projects live in the shared Suite store, and you can save them to a real file on disk, export CSV, or print the call sheet.
A project takes a minute to set up and becomes the spine every other module reuses.
One row per setup. Mark priority and whether it needs a model or a location.
Name, role, call time and fee. Toggle confirmed once locked.
Everything stays on your machine. The JSON project record is what downstream modules (camera.shock, cull.shock and the rest of the Suite) inherit.
Local-first shoot planning. A working prototype of .plan.shock — it merges briefing and production into one project, linked to release.shock.
Projects persist in the shared Suite store (dotshock-suite → projects) — the same spine camera.shock, cull.shock and release.shock read. Save a project to a real file on disk (Ctrl+S) to keep a copy or hand it off. Clearing browser data removes the local copy. Auto model/location suggestion and face-matching need the local Dotshock Engine on port 7788; they don't run in web mode.
One item per row. Tick it off as you pack.
Set how many credits Imla charges per generated image. 1 credit = $0.01.
Sets this project as the active shoot for the Suite, then opens the chosen module. The plan, bookings and releases are read from the shared spine — nothing is re-entered.
Paste crew names + their availability. AI checks against your shoot schedule.