Twenty surfaces, many source systems.
Shopify, Google, Meta, Klaviyo, ManyChat, WhatsApp, Telegram and internal records each carry part of the operating truth.
One workspace, named source boundaries
LifeCloneAI · Public website · Live
Product truth · Human control · Sanitized proof
Client OS case study · ITEMSPUBLIC · SANITIZED
One business.
Three roles.
Twenty operating surfaces.
ITEMS is the live proving ground for LifeCloneAI's workspace model: the portfolio owner sees the whole system, the business owner runs one company, and an operator receives only the customer queues required for the job.
🏠
● ROLE AWAREITEMSCOMMERCE WORKSPACE
20OWNER MODULES
3OPERATOR MODULES
1ISOLATED COMPANY
20CANONICAL MODULES
One ordered workspace surface defined in application code.
3FIXED ROLE LEVELS
Portfolio owner, client owner and focused operator.
3OPERATOR QUEUES
New Customers, Customers and OLD—nothing else.
0PRIVATE RECORDS SHOWN
The public demo uses synthetic names, metrics and conversations.
Why ITEMS matters
The product is being defined against a real operating company.
The challenge is not adding one more dashboard. It is connecting commerce, acquisition, retention, content and customer work without giving every person access to everything.
The same company requires different views.
A company owner needs commercial context and approvals. An operator needs a finite customer-contact queue.
Navigation follows the jobVisible does not mean unrestricted.
Module access, sensitive controls, external actions and source quality are evaluated separately.
Permission is part of the productInteractive public demo
Change the role. Watch the operating surface change.
This is a synthetic presentation of the verified access model. It mirrors the real module hierarchy without loading private customers, revenue or conversations.
LIFECLONEAI · SAFE WORKSPACE
● SYNTHETIC DATA
OWNER MASTER · PORTFOLIO VIEW
FULL SYSTEM SCOPEWhat requires the owner now.
Signals are ranked across authorized workspaces.
NOW · APPROVAL QUEUE3priorities need you
QUEUE PREVIEW · OWNER ONLYEvidence, responsible workspace and exact next action are attached.
Review a prepared customer recovery workflow.
Source and exclusions verified.
APPROVAL REQUIREDChoose one acquisition experiment.
Audience and success condition attached.
DECISION READYOne source needs reconnection.
No stale metric is presented as live.
OWNER CONFIGURATIONITEMS · CLIENT OWNER VIEW
20 MODULESOne company, complete operating context.
All twenty modules are visible; sensitive controls still follow owner policy.
COMMERCE · SANITIZED EXAMPLELIVEstore context connected
WORKSPACE PREVIEW · PRIVATEPublic values are intentionally replaced. The operating contract remains visible.
Acquisition and retention
Three focused queues
New Customers
OPERATOR READYCustomers
OPERATOR READYOLD
OPERATOR READYITEMS · OPERATOR VIEW
3 MODULES ONLYNew Customers
The landing opens on the first allowed queue. No Ads, Orders, Expenses or owner navigation.
Customer 0142New inquiry · context verified · synthetic record
WHATSAPP DRAFT READYCustomer 0143First follow-up due · no prior reply · synthetic record
REVIEW MESSAGECustomer 0144Human question detected · synthetic record
OWNER HANDOFFCustomer 0145Eligibility incomplete · synthetic record
NEEDS CONTEXTThe operator can work the assigned queues; visibility never expands into the broader company workspace.ROLE GATE ACTIVE
Portfolio Owner
Public language for the technical `owner_master` role. It is not claimed as the current in-app label.
ITEMS Owner
`client_owner` with no module allowlist means the complete ITEMS workspace, not access to other clients or private Core.
Operator
The allowlist applies to desktop, mobile, page routing and protected APIs—not just hidden menu links.
Canonical workspace map
All twenty ITEMS modules, with honest source modes.
A visible module does not automatically mean its upstream source is live. The public case separates real APIs, hybrid verified snapshots and assisted operating briefs.
Home
SHOPIFY API / UNAVAILABLE STATEAnalytics
LIVE WHEN CONNECTEDSearch Console
LIVE WHEN CONNECTEDKlaviyo
LIVE + VERIFIED SNAPSHOTGoogle Ads
LIVE + VERIFIED SNAPSHOTMETA Ads
LIVE + VERIFIED SNAPSHOTReels
REAL QUEUE / EMPTY STATEManyChat
LIVE + VERIFIED SNAPSHOTTikTok
ASSISTED OPERATING PLANWhatsApp Channel
OPERATING BRIEFOrders
SHOPIFY API / UNAVAILABLE STATETelegram
REAL EVENT TIMELINENew Customers
SUPABASE RUNTIMECustomers
SHOPIFY + SUPABASEOLD
SUPABASE / BREVO QUEUEMeetings
GENERATED SNAPSHOTProducts
SHOPIFY API / UNAVAILABLE STATEContent
OPERATING BRIEFExpenses
SUPABASE / REDACTED BY ROLEOne concrete operating loop
From a new customer record to controlled WhatsApp follow-up.
The operator experience is intentionally narrow. The system assembles context and a draft, but ambiguity and sensitive cases move back to the responsible person.
Ingest
A new eligible customer or inquiry enters the ITEMS workspace.
Verify
Source, current state and prior contact are checked.
Assign
The record enters one of the three allowed operator queues.
Prepare
Context and a WhatsApp draft are assembled for review.
Contact or hand off
The operator acts inside policy or escalates the conversation.
Preserve state
Outcome and next action remain in the company workspace.
Public truth boundary
The case study shows the system without exposing the company.
The visual model is deliberately close to the application. The displayed identities, metrics and conversations are deliberately not the company's private records.
What is real.
- The three technical access levels
- The exact twenty-module ITEMS catalog
- The operator allowlist of three modules
- Page, mobile-navigation and API enforcement
- The distinction between live, snapshot and assisted sources
What is synthetic.
- Every customer identity and reference number
- All displayed revenue and performance values
- Conversation content and prepared messages
- Priority counts and example recommendations
- Any visual state that could reveal private operations
From proof to repeatable product
ITEMS is one workspace. The architecture is reusable.
The hierarchy stays fixed while each new company receives its own capabilities, sources, people and policies.