Glossary¶

Key terms used across fxquinox and these docs.

Project: The top of the tree. Holds show-wide settings (code, fps, dates) and scopes everything beneath it.
Episode · Sequence · Shot: The production hierarchy. Episodes (optional) group sequences; sequences group shots; a shot is a single continuous piece of footage with cut-range and frame-handle fields.
Asset: A reusable element (Character, Creature, Environment, Prop, Vehicle, and so on). Its type is a configurable, workflow-scoped enum.
Task: A unit of work on a shot, asset or other container: one pipeline step with assignees, a priority, bid hours, a status and dates.
Step: A pipeline or department stage (Layout, Animation, FX, Lighting, Compositing, and so on). Tasks carry a step; workflow schemas scope which steps are available per project.
Status: The state a record is in — for example Waiting to Start, In Progress, Pending Review, Final. Statuses carry a state (not_started / in_progress / blocked / done / cancelled), a colour, and flags such as is_wip, is_feedback and is_done that drive app-wide behaviour. Status codes are camelCase (waitingToStart, inProgress, pendingReview, final, onHold, omitted).
Priority: A sortable urgency level on a task or version (None, Low, Medium, High, Urgent). Priorities have a numeric value that drives sorting and reporting.
Product: A named output of a task (such as lightingMain) — the stable identity that a chain of versions shares.
Version: A numbered iteration of a product, with an author, comment, frame-range metadata, and the input versions it was built from.
Representation: A concrete form of a version (for example exr or mov), with files, tags and a for_review flag.
Workfile: The DCC scene a version was published from (path, software, version number).
Site · FileLocation: A storage location, and where a representation actually lives on it — the basis for multi-site sync.
Lineage: The graph of which versions were built from which, recorded by a version's inputs. You can walk it in both directions.
Publish: Recording a task's output as a Product → Version → Representation chain. See the publish chain.
Schema: The metadata layer that defines entity types, fields, statuses and steps. Editing it changes what exists, with no code change.
Workflow schema: A named bundle assigned to a project that scopes which statuses, steps and asset types are available, so different projects can run different pipelines.
Detail panel: The slide-over inspector that opens when you click any record. It has tabs for Notes, Info, Activity, and (on tasks) Time, Links and Dependencies. Shots, assets and tasks also have a Versions tab. User records lead with an Assignments tab.
The One Law: One canonical core and API; every surface (web UI, desktop, DCC plugins, CLI, SDK) is a client of that API with zero privileged access.