Research standards
Editorial Research Methodology
How Remix Camera separates historical output archives from controlled image-model comparisons and verifies exact prompts, inputs, models, outcomes, and reproducibility limits.
Last updated: July 16, 2026
How to read our results
A side-by-side output grid is not automatically a controlled comparison. Older pages whose attempt-level prompt and input proofs are incomplete are labeled historical output archives and do not support model winners, identity conclusions, or moderation rankings. Only a provenance-complete run may be presented as a controlled comparison.
1. Define the question and test set
A controlled comparison starts with a bounded question, such as how a set of image models handles one frozen adult portrait input and one documented prompt, or how often controlled rows complete without a recorded block.
The article should state the number and type of cases, identify reused or newly added cases when that distinction matters, and avoid implying that a small portrait-focused set represents every image task.
2. Hold comparison inputs constant
A controlled row must freeze and record the canonical prompt plus SHA-256; input object key plus SHA-256; profile ID; aspect ratio; comparison run ID; and exact model IDs. Every request must pin exactly that one input under the same profile. A generated or published model output cannot substitute for the input frame. Missing or mismatched proof fails closed before provider calls. Provider-specific controls remain documented limitations rather than hidden equalizers.
3. Record outcomes before interpreting them
The exact legend on a comparison article is the source of truth. Our pages may use the following labels:
A controlled page may report completion or acceptance rates as accepted outcomes divided by tested outcomes. A historical archive may show raw recorded counts, but it must not rank models from them because unverified input differences can affect both output and moderation behavior.
4. Show evidence and limits together
- Show output images when they are available and keep missing, blocked, or failed cells visible.
- Expose the prompt or enough prompt detail to explain what was tested.
- Record exact model IDs, comparison run ID, and per-attempt request proof.
- Record and verify the prompt hash and input key and hash before generation.
- State sample-size, task, model-specific controls, and timing limits near the interpretation.
- Do not infer image quality from completion rate alone.
5. Prompt-guide selection
Prompt collections may be curated from public Remix Camera packs around a specific reader intent, such as mirror selfies, dating photos, or professional portraits. The article should make the intended use clear and link to the relevant pack when it is the example source.
Inclusion in a guide means the example fits that guide's stated purpose; it is not a scientific score, safety certification, or guarantee that every model will reproduce the displayed result.
6. Reproducibility limits
Image generation is nondeterministic. A rerun can differ because of sampling, model or safety-system updates, provider routing, reference-image processing, or service errors. For that reason, we preserve the recorded result as a dated snapshot. Controlled reruns reuse the input and prompt proofs while receiving a new run ID; older records without those proofs remain archives rather than being promoted to tests after the fact.
See the method in practice
These pages use the July 2026 controlled rerun. Older outputs without exact-input proof are excluded from the comparison grids rather than treated as equivalent evidence.