Pimp My IDE / garage dispatch
Back to garage
October 2, 2026 | image models / provenance

The picture is not the receipt.

A model can follow a box layout, search the web, edit a region, and return a polished image. Keep those actions visible after the pixels arrive.

If a generated image matters, save the prompt, inputs, retrieval setting, composition controls, model route, output file, and review result as one work record.

Layout control creates more state to save.

Black Forest Labs says FLUX 3 Image accepts bounding boxes for composition, up to ten reference images, edits to specific details, and output resolutions through 4K.[1] Its API documentation defines each box as [top, left, bottom, right] on a 0 to 1000 grid.[2]

That is useful control. It also means the text prompt is no longer the whole instruction. A reviewer needs the reference order, each box, the aspect ratio, the requested resolution, and the exact edit instruction.

Save the controls that shaped the image, not a screenshot of the controls.

Grounding is an input route.

The current FLUX 3 Image documentation lists grounding as true by default. It describes this setting as web and image search before generation.[2] That makes the output dependent on a retrieval step as well as the prompt and model.

A useful receipt records whether grounding was requested. A stronger receipt also records what the generation service exposes about retrieval. If no query, source list, or snapshot comes back, write that gap down. Do not present a grounded result as if the source trail were complete.

Availability has several meanings.

The API page names a live endpoint and a polling flow. It says the result URL must be downloaded within one hour.[2] The product page also advertises commercial weights for companies that contact the vendor.[1]

The public black-forest-labs/flux repository we inspected describes minimal inference code for its listed FLUX.1 open-weight models. That repository does not prove a public FLUX 3 self-host path.[3] API access, commercial weights, and a public open-weight release are different routes.

Provenance needs a file binding.

A sidecar text file can help a team reproduce a run, but it can separate from the image. The C2PA specification defines manifests, assertions, ingredients, actions, timestamps, signatures, and bindings to content.[4] Those parts support a stronger handoff when the tool writes and validates them.

Do not claim Content Credentials from a homemade checklist. Record whether a C2PA manifest exists, which validator checked it, and the validation result. If the generator supplied no manifest, keep the run receipt beside the file and say that it is an unsigned work record.

Use one review packet.

  1. Save the exact model route, prompt, reference order, aspect ratio, resolution, safety setting, and grounding setting.
  2. Save every composition box and region edit in machine-readable form.
  3. Download the output before its delivery URL expires. Hash the retained file.
  4. Record the human review result and any C2PA validation separately.

The lightbox below drafts that packet. It does not call FLUX 3, search the web, generate an image, inspect a manifest, or validate a file.

Sources read

Source log and evidence boundary
  1. Black Forest Labs, "FLUX 3 Image" product page, read October 2, 2026. This is the vendor source for bounding-box composition, up to ten references, editing claims, native 2K and 4K output, and commercial-weight availability.
  2. Black Forest Labs, "FLUX 3 Image" API overview, read October 2, 2026. This supplies the endpoint, parameters, default grounding setting, box coordinate format, polling flow, and one-hour output-download window.
  3. Black Forest Labs, public flux repository, read October 2, 2026. The page we inspected describes minimal inference code and lists FLUX.1 open-weight models. We use it only to distinguish that public repository from the FLUX 3 API and commercial-weight routes.
  4. C2PA Technical Specification 2.2, read October 2, 2026. This supplies the manifest, assertion, ingredient, action, timestamp, signature, content-binding, and validation concepts. The lightbox does not implement or validate C2PA.
  5. Black Forest Labs, "FLUX 3: Real World Models", read October 2, 2026. This provides the vendor's multimodal model and launch context. Its evaluation claims are preliminary and come from the model publisher.
  6. Hacker News item 49925974, "FLUX 3 Image", resolved through the Hacker News API and read October 2, 2026. This was the discovery signal. It supports none of the product claims.

Evidence boundary. We read vendor product, documentation, launch, and repository pages plus the C2PA specification and discussion record. We did not call the FLUX 3 endpoint, request commercial weights, inspect an output file, test prompt grounding, compare image quality, or validate Content Credentials. Vendor capability and evaluation statements remain vendor claims.