Vidalux OS is the AI-powered, human-led platform ContentWorks is building to run the business end to end … customer support, the product catalogue, reviews, social commerce, marketing, analytics and pricing … every part grounded in one Product Brain so nothing gets invented. v1 is live now: the content & visual engine, your own AI Studio … 18 creative tools and a six-person board, handed over 27 August … a SOP Factory that turns a voice note into a filed procedure, and a daily Manager that surfaces what's waiting on you. Since then Facebook and Instagram posting, search rankings, sales reporting, the FAQ hub and your reviews on product pages have gone live, and customer video has started. What is left is a shorter roadmap. This page is the map: what each part does, and exactly where it stands.
Vidalux OS isn't a content tool … it runs the whole business. Each domain does one job. The Knowledge Brain is the spine every other domain grounds on. Here's the honest status of each … what's built, what's in testing, and what's still on the build.
In your hands now: the Content & Visual engine (the article, image-suite, repurposing and publishing skills, all checked against the Product Brain); the AI Studio, handed over 27 August … 18 creative tools plus your own six-person board; the SOP Factory, which turns a voice note into a structured, filed procedure; and the daily Manager, which posts one roll-up of what's shipped, overdue and waiting on you. Since then: Facebook and Instagram posting, the Search rankings page, the sales-by-channel Sheet, 27 new FAQs, your 216 reviews on product pages and Posh descriptions. Customer video has started (UGC Fridays packs and the first range video are with you). Still ahead: live chat on the main site, shops, the marketing bot, analytics reporting and pricing.
Product R&D has a card (#175) and you have parked it for now: the new China colleague goes first and the process starts by hand. And a dedicated promotions engine is still only partial … sales reporting now has a channel-by-channel Sheet, your Sales Timeline sets the weekly offer, and a promo calendar is in place, but there is no engine on top that triggers offers by itself. Worth deciding whether it becomes a domain in its own right.
Note · Vidalux comes first, and Posh is already on the same engine: 102 product descriptions, a traffic-recovery plan and a PPC plan are under way … one engine, two brand brains.
Click any capability to see what it does, when to reach for it, what to give it, and … if it's built … exactly what to type. Roadmap items show what they'll do and which board cards they come from. Filter by domain below.
The OS is built in dependency order … the Brain first, because every bot grounds on it, then the domains that earn or save the most. This is the honest sequence, not a finished platform.
The build sequence above is what gets built. This is the other axis … who operates it, and how that changes over time. You're not signing up to pay us to run this forever. We document every job as it stabilises, with the automation doing the recurring work underneath. ContentWorks runs the engine; you approve the work and do the hands-on steps (imports, swaps, pastes). When you bring in a VA, these procedures are what they work from.
Everything starts as a card on your AI Board. You ask, you approve … ContentWorks produces every output. The job of this stage isn't handover, it's trust: making the request-to-output loop reliable across every type of work.
As each type of job stabilises, the SOP Factory, already live, files the repeatable version: owner, trigger, steps, quality check. Thirteen procedures are filed so far. The newer recurring jobs (customer clips, FAQ batches, the weekly corrections run, the sales Sheet and the monthly outreach list) get theirs next. They are what makes handing a job to a VA possible without us in the room.
The board splits into lanes by owner. Automation carries the recurring work. When you bring in a VA, they can pick up the documented jobs, working from the procedures and not from us, and run the day-to-day. ContentWorks keeps strategy, net-new builds and brand-risk work.
ContentWorks runs the engine; you approve the work and do the hands-on steps (imports, swaps, pastes). When you bring in a VA, the filed procedures are what they work from, job by job, as each one has a proven process behind it. The automation does the repetitive part (formatting, uploading, pasting into WordPress, resizing images), so a person's time goes on the work only a human can do: shooting install photos, chasing supplier files, talking to people. What gets handed over is a documented business your team can run.
You don't memorise commands. You describe what you want and the OS routes you to the right tool. Four habits make you fluent … and they hold as new domains come online.
Describe the job in normal words. The OS picks the right tool for you.
Paste the product data, a URL, or upload a reference. It never invents specs … it works from the Product Brain.
Copy runs through Brand Guard. If a claim isn't verified, it gets flagged or removed … not guessed.
Everything lands as a draft for a human to approve. AI-powered, human-led … always.