01BUSINESS OWNERHUMAN ENTRY

IDENTITYAccountemail · verification · secure session

BUSINESSCompany profilename · phone · location · vertical

INTENTPlain-language briefservices · customers · differentiators

LAUNCHPreferred domainbrand name · local market · availability

02 / IDENTITYCONTROL PLANE

One owner. One operating business.

Verified account ownership protects the site, domain, leads, analytics and billing state.

EMAILVERIFIEDPASSWORDARGON2IDSESSIONJWTSITE OWNERSHIPSCOPED

03 / ONBOARDINGOWNER SURFACE

Questions a business owner can answer.

No design system, SEO settings or infrastructure decisions. Just the facts of the business.

WHAT YOU DOWHEREWHO FOR

04 / DEVICESCONTROL PLANE

Owner devices

Registered endpoints connect account identity to web and mobile notifications.

WEB SESSION
MOBILE TOKEN
LAST ACTIVE

05 / GENERATION REQUESTAI PIPELINE

Business context becomes a structured brief.

The input is validated and normalized before it reaches generation, so the output remains editable product data.

OWNER WORDS→SITE BRIEF

06 / AI ORCHESTRATIONGENERATION

Copy, structure and local intent.

Generate the page hierarchy, service language, calls to action, trust content and business-specific SEO fields as one typed response.

010203

VALIDATE → REPAIR → REJECT UNSAFE FALLBACK

07 / GENERATION CACHEOPERATIONS

Identical work is reusable.

Shared cache prevents repeated generation requests from spending time and model budget twice.

08 / SITE BLUEPRINTSTRUCTURED OUTPUT

Not HTML. A business-shaped model.

Hero, proof, services, projects, contact details, CTA, SEO and visual preferences remain structured and independently editable.

HEROSERVICESPROOFPROJECTSCONTACTSEO

09 / VERSIONED CONFIGSOURCE OF TRUTH

Every meaningful edit has a stable version.

Published HTML is an artifact. The canonical website remains structured config plus template and renderer versions.

SITE CONFIGCONTENT JSONCONFIG HASHTEMPLATE IDRENDERER VERSION

10 / EDITOROWNER SURFACE

Change the business, not the code.

Text, services, examples, imagery and contact details can change without a developer.

DRAFT SAVEDVERSION 07

11 / MEDIA PIPELINECONTENT

Originals stay private. Published variants stay fast.

Uploads are validated, stored once and transformed into active WebP variants immediately before publishing.

ORIGINALCROP SLOTWEBP

12 / PUBLISH JOBCONTROL PLANE

Publish is an auditable state change.

A job records the requested version, outcome and active snapshot. Failed rendering never replaces the live site.

REQUESTEDV07STATUSQUEUEDACTIVEV06

13 / RENDERERDELIVERY

Config becomes a deployable website.

The selected vertical and template produce deterministic HTML from the saved version, without another AI call.

CONFIG + TEMPLATE→STATIC HTML

14 / SEARCH ARTIFACTSDELIVERY

Robots, sitemap and page metadata.

The public surface ships with crawlable structure and business-specific search signals.

ROBOTS.TXTSITEMAP.XMLSCHEMA

15 / SNAPSHOT STORESYSTEM OF RECORD

Immutable live artifacts.

Each published version receives its own object key. A current pointer moves only after rendering succeeds.

V05 / ARCHIVEDV06 / CURRENTV07 / READY

16 / REBUILDOPERATIONS

Fix the renderer. Rebuild without AI.

Stored config can be rendered again after a template or renderer improvement.

17 / DOMAIN DISCOVERYOWNER SURFACE

A usable address, inside the launch flow.

Availability, registration and renewal prices are checked against product ceilings before an option is shown.

protrade-austin.comAVAILABLE

18 / DOMAIN SERVICECONTROL PLANE

Register, bind and verify.

Provider automation is sandbox-first, budget-capped and linked to the immutable site identity rather than a mutable slug.

REGISTRATIONCAPPEDDNSCONFIGUREDOWNERSHIPVERIFIED

19 / EDGE ROUTINGDELIVERY

Only approved domains resolve.

The edge asks the application whether a hostname is known and allowed before serving the current snapshot.

DNS + TLSACTIVE

20 / PUBLIC WEBSITECUSTOMER SURFACE

The business is live.

Fast static delivery handles customer visits while forms and behavioural events return to the operating platform.

WEBCONTENTSEOINDEXCTALEADS

21 / OPERATING COREONE BUSINESS IDENTITY

SHARED BUSINESS STATEONE BUSINESS.
ONE OPERATING VIEW.

The website, customers and owner actions resolve against the same record.

SITELEADSCRMMETRICS

LIVE SITE1published version

OPEN LEADS08owner action required

CONVERSION3.6%rolling 14 days

01 / PRESENCESite · domain · versionsvertical / template / live pointer

02 / OFFERServices · prices · visibilitycopy / order / media reference

03 / PROOFProjects · locations · categoriesportfolio / service context / assets

04 / CUSTOMERSLeads · messages · statussource / owner / chronology

05 / MEASUREMENTVisits · calls · formssession / event / day / retention

22 / ENTITLEMENTSCOMMERCIAL CONTROL

Subscription state controls costly actions.

Publish, rebuild and domain operations are allowed from server-side entitlement state, not a client-side button.

PLANACTIVEPUBLISHALLOWEDDOMAINALLOWEDPERIODCURRENT

23 / BILLINGSTRIPE

Checkout, renewal and cancellation.

Webhook events update customer, subscription and entitlement records idempotently.

CHECKOUTCREATEDWEBHOOKVERIFIEDENTITLEMENTSYNCED

24 / LEAD CAPTUREPUBLIC → PRIVATE

Every enquiry becomes a customer record.

Website forms create a scoped lead with contact details, service context and source metadata.

NEWEmergency plumbing2 MIN AGO

25 / LIGHTWEIGHT CRMOWNER OPERATIONS

Lead status stays visible.

New, contacted, qualified, won or closed. The owner sees the customer history rather than another disconnected inbox.

JOHN S.NEWQUOTEWONSARAH J.NEWCALL—

26 / CONVERSATIONSOWNER SURFACE

Context stays with the customer.

Messages are attached to the lead chronology so follow-up is not split across memory and tools.

CUSTOMER / Need a quote this weekOWNER / Available Thursday at 10:00

27 / EVENT INGESTIONMEASUREMENT

Visits become usable signals.

Page views, phone clicks and form events are retained as scoped raw events before daily aggregation.

PAGE VIEWACCEPTEDPHONE CLICKACCEPTEDFORM SUBMITACCEPTED

28 / ANALYTICSBUSINESS SIGNALS

Traffic connected to outcomes.

Daily summaries join visitors, leads and conversion rather than reporting vanity traffic alone.

51TODAY8LEADS3.6%CVR

29 / NOTIFICATION ROUTERDELIVERY

The right signal reaches the owner.

New leads and system events become in-app or device notifications with read state.

NEW LEADDELIVERED

30 / OWNER DASHBOARDWEB SURFACE

Website and customer activity, together.

Visitors, conversion, leads and conversations share the same daily operating view.

51VISITORS8LEADS3UNREAD

31 / OWNER COMPANIONMOBILE SURFACE

New business, wherever the owner is.

Notifications and customer context move with the account.

NEW LEAD
VIEW CUSTOMER
FOLLOW UP

32 / VERTICAL CATALOGPRODUCT SCALE

One platform. Different business grammar.

Contractors and legal services can use different templates, page rules and structured-data types without changing the publishing core.

CONTRACTORSLEGALCLINICSAUTOPROFESSIONAL

33 / BACKGROUND WORKERSOPERATIONS

Slow work leaves the request path.

Email delivery and other retryable tasks run through locked queues so multiple workers can scale without duplicate ownership.

QUEUE CLAIMROW LOCKEDRETRYBOUNDEDDELIVERYOBSERVED

34 / EMAIL OUTBOXDELIVERY

Verification and customer mail.

Transactional messages are queued, leased and acknowledged independently of API response time.

35 / PLATFORM HEALTHOPERATIONS

The launch system watches itself.

API, database, Redis, billing, domains and publish jobs expose enough state to distinguish customer problems from platform failures.

APIREADYDATABASECONNECTEDPUBLISH JOBSTRACKEDDOMAIN CHAINTESTABLE

36 / PRODUCTION CONTROLSENGINEERING STANDARD

Built to survive the second publish, not only the first demo.

Immutable versions, atomic pointers, idempotent billing events and server-side permissions keep expensive operations controlled as the customer base grows.

ATOMIC DELIVERYLive pointers move only after a complete render.

SCOPED DATAEvery lead, event and asset belongs to an owned site.

REBUILDABLEStored config can produce a corrected artifact without regeneration.

PRICE GUARDSDomain actions respect enforced registration and renewal ceilings.

IDEMPOTENT BILLINGDuplicate provider events do not duplicate state transitions.

OBSERVABLE QUEUESBackground delivery has explicit claim, retry and result states.