Object removal layer reveal — peel the surface to show what the eye missed

What the technique is

One source plate. A locked frame. A masked region inside the plate. A cloud edit pass removes the masked layer and writes a physically-correct under-layer in its place. The plate outside the mask is held identical — only the masked region changes, and only to expose what would actually be under that surface.

The trick is the physical correctness of the reveal. A torn-back shingle has to expose deck and underlayment, not a marble floor. A peeled paint chip has to expose primer or bare wood, not a stranger’s wedding photo. The prompt has to be specific about what is underneath, in domain-appropriate detail.

When to use it

Any time the script makes a claim about a hidden state and needs the audience to see it. Hidden damage, hidden craftsmanship, hidden construction, hidden product engineering. The peel is the proof.

How Hybrig encodes it

The Object removal layer reveal workflow template in /studio drops three inputs and a compositor on the canvas: the source plate, the peel mask, and a prompt that describes the physically-correct under-layer state. The compositor stitches the original plate and the revealed plate into a peel-back comparison.

Removal passes are metered cloud work today. One job at a time (per [[feedback_no_batch_paid_jobs]]). The reveal is a single hero beat — do not run it on every shot in the timeline, the unit economics break. See [[project_cloud_polish_by_beat_type]].

Companion technique on the same locked plate is the object-additive buildup at /learn/object-additive-buildup. Same stage, opposite direction: buildup adds material, removal exposes what is beneath.

The render-process workflow

Five steps run in order. The clean plate and the revealed plate enter the assembly stage together so the peel transition can interpolate between them frame-accurately.

Step 1 — Source plate (clean)

Node: image-upload for a real photo, or flux-lora-still for a generated source. In: a still or a prompt describing the clean surface state. Out: the before-reveal plate — what the audience sees first. Why: the reveal only reads if the audience has spent a beat believing the clean state. The clean plate is what they have to trust before the peel breaks the trust.

Step 2 — Region mask

Node: not yet a dedicated palette node — see open questions. Today the region is keyed by hand as a bounding shape (loose silhouette with a few pixels of margin so the cloud edit can blend the edge cleanly). In: the clean plate plus the peel-region outline. Out: an alpha mask describing which pixels the removal pass is allowed to rewrite. Everything outside the mask is held identical between the clean and revealed plates. Why: the peel transition only reads if the audience can tell which area is changing. A loose, well-defined mask is what makes the change legible.

Step 3 — Object-removal cloud edit

Node: not yet a dedicated palette node — see open questions. Today the removal pass is a manual cloud handoff. In: the clean plate plus the region mask plus a prompt describing the underlying state to expose (cracked underlayment, rotted boards, internal wiring, soil, whatever the script wants the audience to see). Out: the revealed plate — identical to the clean plate outside the mask, with the under-layer state painted inside the mask. Why: single cloud edit per spot — the reveal is once-per-script by definition because you cannot reveal the same hidden state twice. Run as a single job, never batched, per [[feedback_no_batch_paid_jobs]].

Step 4 — Peel transition assembly

Node: remotion-timeline. In: the clean plate, the revealed plate, the region mask, and a peel motion parameter (linear wipe, curl, slide, fade). Out: a clip where the clean plate holds for the opening beat, then the peel motion animates across the region mask for 18-24 frames, revealing the under-layer state pixel by pixel. Why: Remotion owns the transition assembly. The wipe duration is what gives the audience time to read the change — too fast and they miss it, too slow and the dramatic tension drains.

Step 5 — Encode and emit

Node: video-output. In: the assembled peel transition from step 4. Out: an MP4 on disk tracked in /operations. Why: terminal node.

Studio workflow shortcut

The object removal layer reveal template is not yet a one-click entry in the /studio palette — the mask + removal-edit stage is a manual cloud handoff today. Once the mask and object-removal nodes land (see open questions), the template will live at /studio?template=object-removal-layer-reveal and drop the full chain onto the canvas in one click.

Example use cases

• Time-lapse construction reveals. A finished wall peels back to show the framing, the insulation, the wiring — the hidden craftsmanship the homeowner paid for but cannot see.
• Before/after restoration. A restored deck peels back in the masked region to show the rotted boards the restorer replaced. The peel is the receipt.
• Product setup tutorials. A finished product peels back its outer shell to show internal components and connections. Pedagogical x-ray without an actual disassembly shoot.
• Roofing trust beats. A clean-looking roof peels back the visible shingle layer in the masked area to expose hidden damage — the trust-building argument that the data sees what the eye misses.

Open questions

• No dedicated region-mask node lives in the Studio palette today (templates.ts has no entry). Step 2 of the render-process workflow runs by passing a hand-keyed bounding shape inline with the cloud edit job.
• No dedicated cloud-object-removal node lives in the palette today (templates.ts has no entry). Step 3 is a manual cloud handoff. When the backing node lands, the workflow template will swap to it and the chain becomes a single drag-and-drop graph.
• The peel wipe in step 4 today is a hand-keyed Remotion mask transition. A future pass could generate the wipe mask from the removal region’s bounding box automatically.