Quality rules come from Rivington's own systems and are applied in layers. Firefly Workflows + Rules runs them on every asset; each layer keeps its owner and source of truth.
Market profiles are set up once and reused by every brand: sizes and placements, language, default copy variants and the compliance rule set.
One kit per brand: logo, colours, type, tone of voice and brand rules. Every campaign for that brand uses the same kit.
No brands match this search.
Illustrative. Brand names, categories and market counts need confirming in discovery. Only Lumière is set up in this demo.
Approved images and copy to reuse across brands and markets. Campaigns choose their hero here in Plan; approved variants are added back when a campaign goes live.
In this demo, Japan changes to Added when the campaign is submitted to compliance in step 6. US and France are running in parallel and remain pending.
Illustrative. Brand names, market counts and hero names need confirming in discovery.
Drop a Firefly-generated image onto each size. Filled sizes replace the mock-up in Produce variants, View all and Human review; empty sizes fall back to the hero-based mock-up. Images are saved with the project.
Systems connected to this workspace. Rivington's existing systems supply product data, approved copy and compliance decisions; Adobe Firefly Enterprise runs generation and checks.
Workspace setup for platform and brand admins. Markets, rules and connected systems are set up once and reused by every campaign.
This documentation describes the proposed system. {{ runtimeDescription }}
Start with what you need to do, explore the system map, or use the reference. Hover any underlined system name for its owner, sync and failure behaviour.
{{ docNode.what }}
{{ traceCur.text }}
{{ failInfo.text }}
Step-by-step checklists for common maintenance tasks. Ticks are saved in this browser, and each step links to the page where you do it.
Six steps. Steps 2 to 4 run on Firefly Enterprise; the others use Rivington's existing processes.
What each connected system provides, how it syncs and what happens when it is unavailable. Hover a name for details.
Layers are evaluated in order. A lower layer can tighten a rule from a higher layer but never loosen it. Campaign overrides need an approver.
Who must approve each type of change. Set in Product improvements; suggested changes follow these settings.
Legal and claims changes always need the owner and Rivington Legal. {{ docChanges }} changes are in the change log.
The system turns one approved hero image into every size, language and channel a campaign needs, then checks each asset before people review it. Everything else on this page follows from these three ideas.
Illustrative. Systems, owners and sync schedules are confirmed in discovery.
Usage data and support tickets from every campaign are grouped into suggested product changes. Governance settings decide what applies automatically and who approves the rest.
Select the brand, approved hero, markets and channels. Each market brings its own sizes, language and rules.
Product details, approved Japanese copy and market rules are pulled from Rivington's systems.
{{ produceDescription }}
10 concepts · {{ liveBatchPlan }} · three generate at a time
{{ liveStatus }}
A full batch needs 10 requests. Use Demo mode until the daily allowance resets at midnight UTC.
{{ liveError }}
{{ rule.source }}: {{ rule.text }}
Every asset is checked against brand, Japanese copy, format and market rules. Exceptions are fixed automatically or routed to a reviewer.
Creative and market reviewers approve a representative sample. Approval releases the full set.
Submit to compliance for final clearance, then publish to Japan channels.