Guinness Product Overview
What is Guinness
Guinness is an AI platform by 4D that keeps a project's wireframes, designs, and code in continuous sync. Rather than treating the three as separate artifacts that drift apart, Guinness provides 6 bidirectional conversion tools โ one per edge of the WF / Design / Code triangle โ so that updating any one of them can generate or update the other two.
The product is referred to as GenAI-PJ in internal system slides; "Guinness" is the project name used in repositories, documentation, and tickets.
Triangle Workflow
flowchart LR
Design(["๐จ Design<br/>(Figma)"])
Wireframe(["๐ Wireframe<br/>(Figma)"])
Code(["๐ป Code<br/>(jsx / html)"])
Design ==>|"Des2Code (live)"| Code
Code ==>|"Code2Des (in dev)"| Design
Wireframe -.->|"WF2Des"| Design
Design -.->|"Des2WF"| Wireframe
Wireframe -.->|"WF2Code"| Code
Code -.->|"Code2WF"| Wireframe
Solid lines are live; dashed lines are not yet started. Each edge has 2 tools (forward and reverse):
| Edge | Forward | Reverse |
|---|---|---|
| Wireframe โ Design | WF2Des | Des2WF |
| Design โ Code | Des2Code | Code2Des |
| Wireframe โ Code | WF2Code | Code2WF |
Why It's Needed
- No fixed delivery order. Design can finish before Wireframe; Code can finish before Design. Filling gaps (generating missing Wireframes or Designs) before delivery happens constantly.
- Site renewals and competitor research. Projects start from an existing site, requiring reverse-conversion of live Code into Wireframe or Design.
- Gaps found in design review. Even when Code is complete, reviews frequently surface missing pieces. Teams want to add or update only the Design quickly, not rebuild everything.
Tool List and Current Status
| Tool | Direction | Status | Owner |
|---|---|---|---|
| Des2Code | Design โ Code | Live (updating) | 4D + NDVN |
| Code2Des | Code โ Design | In development | 4D |
| WF2Des | Wireframe โ Design | Not started | NDVN |
| WF2Code | Wireframe โ Code | Not started | TBD |
| Des2WF | Design โ Wireframe | Not started | TBD |
| Code2WF | Code โ Wireframe | Not started | TBD |
Architecture Strategy
- Thin Client Model โ Client tools are ideally responsible for I/O only. The UIs (ui-admin, ui-user) hold no conversion logic themselves.
- API-First Logic โ Conversion and orchestration live behind the API. Centralizing logic on the API side allows the same capabilities to be delivered across multiple surfaces: web, apps, AI-agent MCP servers, and future SDKs / CLIs.
The Guinness runtime consists of the following apps:
- api-admin โ Operator-facing backend (PostgreSQL + Cognito admin pool)
- api-user โ End-user-facing backend (PostgreSQL + Cognito app pool; currently hosts Des2Code)
- mcp-v2 โ MCP server; exposes conversion tools to AI agents
- ui-admin โ Back-office for 4D staff (Next.js)
- ui-user โ End-user web client (future)
Team
- 4D (Fourdigit) โ Product, backend API, infrastructure, admin UI
- NDVN (NTT Data Vietnam) โ AI conversion engines (WF2Des, Des2Code AI backend)
- Plabs โ Collaboration partner on specific features