v0.5 teaches the method. PRZEM Art Director Pro proves the method over time. Keep that one line in mind and the rest of this makes sense.
How to use it — step by step
- Stage your scene. Set up the scene the way you'd actually shoot it.
- Run Benchmark Preview. Read what's already known about how this combination tends to behave before you commit a generation to it.
- Check Risk Readout. Look for any flagged risk on your current SREF/settings combination.
- Export your prompt (Standard or Lean) and generate in Midjourney.
- Score the batch with Manual Scorecard. Be honest about what came back — not what you expected to come back.
- Read the sample-size note, if one appears. If your batch is small, treat a clean result as encouraging, not conclusive. The only way to know if it holds is to run it again.
- Optional: look at the Cast Swap Demo if you're curious how changing the cast might shift the outcome — it won't run the test for you in v0.5, but it shows you what that kind of finding looks like.
What's inside
Benchmark Preview
A look at how your staged scene is expected to perform before you spend a generation on it — based on what's already known about how the SREF and settings you're using tend to behave.
Manual Scorecard
After you generate, you score the batch yourself against the benchmark. This is the core of the loop: you're not asking PRZEM to grade your work, you're logging what actually happened so the pattern becomes visible. If your batch is small, the Scorecard will say so rather than letting a 4/4 feel more conclusive than it is.
Risk Readout
A plain-language flag for where your current setup is showing risk — drawn from known behavior patterns for the SREF and settings in play, not from a guess.
Cast Swap Demo
A static, worked example showing how changing cast (the figures/subjects in a scene) can affect whether a result holds or fails — using a real documented case, not a hypothetical.
Lean Mode
A single-export mode. No persistence, no comparison history, no caching. Each export is its own self-contained result — by design, not as a limitation. If you want a saved history you can compare over time, that's a Pro capability.
Why this exists
PRZEM isn't a prompt generator. It's a testing system for discovering which visual ideas are actually controllable in Midjourney — and which ones only look controlled because you got lucky on a single batch.
That second part matters more than it sounds. A setup can score clean 4/4 in one batch and still reveal weaknesses once you run it again. We found this firsthand: one SREF looked locked-in after a single clean batch, then revealed a true hold rate closer to 14 out of 16 once we ran it across four batches instead of one. The setting wasn't actually unreliable — but trusting one batch would have told us the wrong story either way.
v0.5 exists to put a version of that discipline in your hands, scoped to a single session: stage a scene, preview the benchmark, read the risk signals, export your prompt, generate in MJ, score what actually came back, and see — explicitly — when your sample size is too small to trust the verdict.
What this is not
v0.5 is session-level and single-batch. It will not tell you whether a setup holds up across multiple batches, across time, across different casts, or across a range of style settings. That kind of evidence — saved histories, automated cast-swap testing, stability testing across conditions, exportable benchmark reports — lives in PRZEM Art Director Pro.
This boundary is intentional, not a missing feature. The whole point of v0.5 is to show you how to ask these questions on your own setup. Pro is for when you want the system to keep asking them for you, automatically, over time.
A note on reading your own results
A clean batch is a data point, not a verdict. The most useful habit you can build from v0.5 is treating "it worked once" and "it holds up" as two different claims — and noticing which one you actually have evidence for before you build on top of it.
