Vinci
Creative Studio

Vision document · Architecture overview · Roadmap
From manual design pipelines to an AI-native creative operating system.

01 Origin & Problem

Why Vinci exists

10+
Banner formats in scope
2
Languages per asset (EN + AR)
0
Self-serve paths (before Vinci)
∞
JIRA tickets, no system
02 Where Vinci sits

The broader creative pipeline

Vinci is one node in a larger content production chain. Understanding where it sits · and what it doesn't own · is critical to scoping it correctly.

Curie
Event Calendar
Campaign triggers: Ramadan, Black Friday, category sales
Curie
Page Layout
Defines page structure: hero slots, carousels, tile rows
▶ Vinci
Asset Generation
Generates banners & tiles in EN + AR per spec
▶ Vinci
Asset Storage
GCS bucket → page assembly and publishing
Live
Onsite / CRM
Customer-facing placements across channels

Curie handles the upstream decision of what goes on a page and where. Once a page slot is confirmed · a hero banner, a category tile row, a product carousel · Vinci takes over and produces the visual asset. In a future state, Curie can invoke Vinci programmatically, making the entire flow event-driven.

03 Evolution

Past → Present → Future

Before
Manual era

Manual, ticket-driven design

  • · JIRA ticket → brief interpretation → manual Figma build → export
  • · No AI, no templates, no feedback loop
  • · Every asset bespoke, even when it didn't need to be
JIRA-gated No self-serve Manual Figma export No performance data
V1
Shipped

Designer-led AI generation

  • · 3-step brief: format · vibe · review
  • · Figma guidelines + approved assets as generation context
  • · Hero banners + category tiles, EN + AR, all ratios
  • · Composites hero images or SKUs without distortion
  • · Built-in eval QCs output against the original brief
Hero banners EN + AR Category tiles EN + AR Desktop formats all format sizes Built-in evals
V2
Next

Full asset coverage + stakeholder self-serve

  • · JIRA removed · category, DM, and CRM teams self-serve directly
  • · Full banner ratio coverage + DM and CRM creatives
  • · Usage analytics: request logs, model breakdown, daily cost, time-in-funnel
[V1] Built-in evals Desktop banners Logo and brand assets design guidelines Stakeholder self-serve
V3+
Long term

Creative OS for noon

  • · Single source of truth for all brand assets, logos, and guidelines
  • · Curie integration · page-layout decisions auto-trigger asset generation
  • · Emailer, translation pipelines, and SKU-level image generation in-house
  • · "Suggest Me" mode for campaign-ready work with minimal input
  • · Shared creative infrastructure across noon Food, noon Daily
[v1+v2] Usage analytics Admin logs Curie integration Emailer Cross-vertical (food/minutes) Chatbot Design system hub Suggest Me mode
04 Architecture

How Vinci is built

Modular pipeline · each layer upgrades independently without touching the others.

01

Brief Interface

3-step input: format · vibe · review. SKU/URL, custom uploads. Brand constraints enforced invisibly.

02

Intent Decoder

Translates brief into a generation spec: dimensions, language pair, hero subject, background, overlays, CTA.

03

Rules Engine

Figma-sourced tokens: fonts, spacing, radii. Rulebook for CTAs, offer tags, and standard elements.

04

Asset Repository

Approved assets with performance metadata. Few-shot context so new outputs inherit past top-performers.

05

Generation Layer

Composites hero onto background, applies text and elements. EN + AR from a single brief.

06

Eval + Storage

QC against brief + guidelines before surfacing. Stored on GCS. Performance feedback loops into rules engine.

05 User Evolution

Who uses Vinci, and when

The tool's user base expands in deliberate phases · each stage unlocking a new group while the previous one remains supported.

Phase
Primary User
What they can do
Now (V1)
noon Core Designers
Generate EN + AR banners and category tiles from a guided brief. Download PNG. Refine with feedback.
V2
Category, Onsite, DM & CRM Teams
Submit asset requests directly · no JIRA ticket, no design team intermediary. Full asset coverage.
V3+
All noon verticals
Access Vinci as shared creative infrastructure. noon Food, noon Daily, external marketing teams.
06 The Vision

Where this goes

Vinci is not a banner generator. It is the creative infrastructure that lets noon operate at the speed of commerce · where a campaign brief becomes a production-ready, brand-consistent, bilingual asset in minutes, not days.
· Vinci Product Vision · 2026

The long-term bet is that design bottlenecks are a solved problem at noon. Any team, for any campaign, in any language, gets production-ready creative in minutes · not days. The design team's role shifts from execution to governance: owning the rulebook, curating the repository, and setting the creative direction that the system executes against.

Vinci's integration with Curie is the final unlock: a world where a category manager creates an event, Curie lays out the page, and Vinci auto-generates every asset in the layout · all without a single JIRA ticket.