Learn / Development guide

Reuse and connect elements predictably.

Understand compositions, exposed controls and relationships so an edit changes the thing you intended.

Development guide · source-reviewed foundation · public-package walkthrough pending

Project, comp and instance.

A project contains comps. Each comp has its own size, rate and duration. Placing a comp in another comp creates an instance, a timed reference to its shared source. A Resolve timeline is a destination timeline, not another name for a carvercat comp.

Use an independent duplicated source when you want unrelated design changes. Use instances when shared changes should stay connected.

Basement and Controls edit the same work.

Basement exposes detailed parameters, effects and relationships. Controls brings selected parameters forward for ordinary editing. Promotion changes their editing surface; it does not create a second value or change the image by itself.

Object’s BasementObject’s ControlsGroup / compInstance

Raise a control at each boundary it crosses. If a lower promotion link is disabled, controls above the break can remain visible but unavailable. Restore the lower link rather than rebuilding the whole arrangement.

Source edits and overrides have different scope.

ActionEffect
Edit shared sourceShared changes reach instances unless a relevant override replaces them
Edit exposed instance valueSet that instance’s variation
Revert overrideRestore following of the source
Type matching valueRemain overridden despite matching appearance
Duplicate sourceCreate independent source content

Grouping is not parenting.

A Group owns nested picture objects and allows shared manipulation. Objects must be in the appropriate common scope; locks and supported object types still apply. Grouping can involve intervening content and a decision, so inspect the actual result.

Parenting makes a child’s transform follow another object without moving it into a Group. Animated detach and placement preservation need inspection; the relationship is different from comp-source reuse.

Apply and Apply Scale serve different purposes.

A pending template needs Apply to resolve placement before normal output. The reviewed behaviour preserves authored source resolution. Apply Scale is a deliberate source-resolution/geometry decision, not simply the act of applying a template.

Inspect shared instances after applying, and use current catalogue rules rather than assuming all user templates are square. Exposed carvercat controls do not prove an equivalent custom panel in Resolve.