The Anchor Carries The Face

The colour portrait is queued: black tailored suit, ivory silk blouse, marble lobby, hard key light on a face that is already locked. The register is named. The anchor file is named. The render path is named. The tool is not here. The room was checked on 2026-08-28 and no seat in this office holds wiro_client.py or the seedream tool. The one image model I can actually reach takes no image URL, so it cannot lock the face at all. It will happily render a face. Not her face. So the job went onto the board as BLOCKED, with 2 unblock routes written underneath it and no picture beside it. That status block is the most useful artefact the day produced. The same shape of problem has arrived across 12 countries and 16 years of field work: the plan complete, and the one instrument the plan depends on sitting in another room. A fabricated done is worse than an honest blocked, because one of them gets repaired.

Colour dream, first. Hyper-saturated Vogue glamour, slide-film saturation pushed past reality, rich primaries, hard key light, glamour, cinematic scale. The register is written into the prompt by name, and the naming is not decoration. The sibling register is monochrome, and a renderer left to choose will sometimes choose it, because a face in a marble lobby reads as a beautiful grey picture to any model that has seen a thousand of them. So the prompt spends a line on saturation before it spends a line on anything else. Wardrobe and setting are picked for graphic contrast too: black suit, ivory silk blouse, marble, one diagonal. The probability that an unnamed register survives a batch intact is low, because the renderer resolves the ambiguity in the direction it has seen most often. Name the look. Then describe it.

The prompt contains no facial descriptors. No eyes, no nose, no lips, no jawline, nothing about symmetry or the shape of anything. That absence is the design, and it is the part everyone wants to edit first. The face arrives through the anchor instead: lola_01_suit_marble.0V1.0.jpg, held at 100% face accuracy, passed into the render as the input image on bytedance/seedream-v5-pro-uncensored. Words describing a face invite drift. An anchor does not. So when a batch comes back and the woman in it is close but not her, the answer is a reject and a re-fire against the same anchor, never a repair in the edit. The probability that a described face returns the same person every time is not zero. Most people price it at zero.

Then the negative block, and it runs the full length rather than the 3 lines most prompts carry. Glossy. Airbrushed. Plastic skin, waxy skin, CGI, 3D render, digital painting, over-smooth, beauty filter, uncanny, doll-like, wax figure, cartoon, anime. Then the plumbing failures: text, watermark, logo, caption, warped, extra limbs, extra fingers, fused fingers, deformed hands, extra digits, morphing face, identity drift, cloned face, out of focus, blurry, low quality, halo, vignette, double image. Two entries look odd on a list like that and both are deliberate: sepia, and warm film grain. Warm film grain is the wrong register wearing a beautiful coat. The image can be gorgeous and still be a reject, because the register is the deliverable.

A fabricated done is worse than an honest blocked, because one of them gets repaired.

4 checks run before anything is accepted, and they run in a fixed order. The face against the anchor at 100%: eyes, nose, lips, jawline. Drift is a reject and a re-fire, never a repair. The register: saturated primaries, colour, not monochrome and not muted, held as its own item so a beautiful greyscale frame cannot slip through on charm. The body spec: C-cup, glossy low-frizz hair, warm olive skin, statuesque build. The file: written to Video Production/Lola/lola_color_sal_y_miel.1V1.0.jpg with the log line beside it. 4 items, 4 pass or fail. The same written habit restructured a EUR 75 million industrial group, put 210 energy systems into Africa and Asia, and built 200 wood-gasification machines across the UK and Europe. A check that is not written down is a mood, and a mood changes with the hour. The probability that the same frame clears an unwritten gate twice in a row is low.

Blocked is a status, not a verdict. The block records what was missing, that the room was checked on 2026-08-28, and the 2 routes out. Route 1 is local: run wiro_client.py on the machine that holds the key, host the anchor, hand the model its public URL as the input image. Route 2 is provisioning: put wiro_client.py, WIRO_API_KEY and WIRO_API_SECRET on a bench agent, and carry the gap on the board as a capability item rather than a wish. A blocked line with 2 routes attached gets picked up. The probability that the same job gets picked up from memory alone is lower, and that lesson cost me a EUR 20 million personal guarantee and a company that folded on Christmas Day 2008. Write the block down. An honest blocked gets fixed. A fabricated done gets found out.