Treat flux camera angles as promptable composition, not a 3D camera rig.

Define flux camera angles as composition language

Specify camera angle together with distance, lens impression, subject position, and background relationship. Changing only high angle to low angle makes the comparison interpretable. Record which attributes are prompt instructions and which would require geometry or a reference editor. The official guide supports a structured brief, but a text field does not become an interactive camera or establish that the scene will rotate consistently. For a reversible workflow, preserve the reference set, and ask the source custodian to record visible continuity before the bounded test.

Use matched prompts to isolate the angle

Use one product scene and produce eye-level, high-angle, and low-angle briefs with identical lighting, subject description, crop, and material constraints; compare composition rather than style novelty. Preserve the same seed when the tested surface documents it, then review silhouette, horizon, perspective, negative space, material detail, and subject identity. This page does not submit a prompt or display generated images; it defines a reproducible comparison. For a reversible workflow, preserve the decision history, and ask the rights reviewer to record identity consent before the dated decision.

• One changed camera attribute At the next gate, preserve the decision history, and ask the release approver to record identity consent before the bounded test.
• Stable subject and lighting brief At the next gate, preserve the handoff draft, and ask the brand reviewer to record input provenance before the bounded test.
• Geometry and identity review At the next gate, preserve the input snapshot, and ask the creative lead to record camera logic before the bounded test.

Do not overstate prompt compliance

Do not call the result camera control when the source only documents prompt attributes. Reject geometry changes, product deformation, inconsistent scale, or a new scene masquerading as a viewpoint change. A source example demonstrates supported prompt vocabulary, not universal instruction following or a measurable accuracy rate. Any result claim needs its own dated, matched test, and current SEELE access must be verified independently in the workspace. At the next gate, preserve the review copy, and ask the claims reviewer to record reversal cost before the dated decision.

Keep the FLUX Camera Angles evidence ledger narrow

Black Forest Labs first-party documentation verifies camera attributes as FLUX.2 prompt structure, not a physical or interactive camera rig. Record the source owner, product or model name, verification date, surface or region, exact claim, and unresolved gap beside the test. Taxonomy eligibility and search demand explain why the page exists, but neither can be reused as proof that SEELE or another provider exposes the entire query as a current capability. At this stage, preserve the delivery checklist, and ask the creative lead to record camera logic before the acceptance review.

• Black Forest Labs documents angle, distance, focus, lens, and related camera language in structured FLUX.2 prompts. At this stage, preserve the evidence table, and ask the identity reviewer to record human approval before the workflow transfer.