MRGI FLUX / WORKFLOW FIELD GUIDE
Create a family of quarterly motion graphics
Use approved numbers in repeatable graphics while keeping data and creative exceptions visible.
01 / FROM INPUT TO HANDOFF
Follow the decisions.
This walkthrough describes the intended MRGI product behavior. The browser demo illustrates a small part of the workflow; it does not run the complete application.
- 01
Define the fields
- Start with
- A fictional title and metric template.
- Work through
- Declare accepted values, units, ranges, and timing.
- Result
- A bounded template contract.
- 02
Bind the snapshot
- Start with
- A reviewed quarterly dataset.
- Work through
- Map source fields and reject missing or unsuitable values.
- Result
- A candidate set of bound compositions.
- 03
Inspect the run
- Start with
- Text fit, range, and timing findings.
- Work through
- Review exceptions and approve the intended graphic variants.
- Result
- A reviewed render recipe.
- 04
Deliver the collection
- Start with
- The recipe and outputs.
- Work through
- Record the template and data versions used for each variant.
- Result
- A traceable graphics collection.
02 / INPUTS & INTERCHANGE
What travels with the work.
These are foundation formats and intended handoff contracts. Support and fidelity must be confirmed for each released build.
| Artifact | Role | Review consideration |
|---|---|---|
| Approved data | Grid handoff | Units and allowed ranges must match the template contract. |
| Composition / assets | Motion design inputs | External assets, fonts, and expressions need controlled versions. |
| Rendered graphics | Motion delivery | Frame rate, alpha, color, and codec behavior need destination tests. |
A deliberate cross-app boundary
Use approved Grid data and Line brand tokens to prepare graphics for Motion delivery.
The intended handoff should identify the selected resource, its version, the destination, and the user’s authorization. A linked application should not inherit unrestricted file access.
Explore the connected applications ↗03 / BOUNDARIES & READINESS
Know what this example establishes.
- The browser example animates a single synthetic metric.
- No production composition or codec engine runs here.
- Data correctness and communication quality need separate review.
Development status
The source foundation is imported. Dataset constraints, render records, and the pictured production interface are planned.
Before a production release
Validate real-file behavior and platform support, implement the stated authorization and review rules, and document the tested acceptance scope. The interactive website is a product demonstration, not a release candidate for the application.
04 / PRODUCT QUESTIONS
The details that matter.
Can any spreadsheet drive a template?
The proposed model accepts only fields that match the template’s declared contract. Arbitrary columns should not bind silently.
Why is manual animation scrubbing useful?
It exposes the relationship between a value and a frame without requiring continuous motion or autoplay.
Open-source foundation
Compositions, keyframes, expressions, rendering/export, and automation exist in EffectCraft. Approved-data production governance is the proposed MRGI focus. Read the credits and foundation mapping.
Keep exploring Flux.
Return to the product breakdown or try the local interactive example.