0S Sovereign Client App Factory

Valley intake to shipped client app, workspace, proof, and payout lane.

Clients

Pick a Valley client and build the app from their real surfaces.

The factory should feel like an operator tool: queue, inspect, run, verify, and ship, all without dropping the live build pipeline.

Operations

Track the current client from intake through proof.

This is the factory control desk: state progression, generated outputs, and the release paths that matter.

Pipeline states

Where this client stands now.

Latest output

What the factory has already produced.

Generated routes

Open the live package instead of hunting through folders.

Clients

Import from Valley or correct the client record before build.

This is the first-class workflow. Pick a business, import it, run the factory, and stay in the same operating surface.

Client record

Source of truth before generation.

Valley Verified

Click a business and turn it into an app run.

Scanner

Inspect routes, media, app files, and path risk before we trust a run.

Current scan

Run the scanner against the active client packet.

The scanner inventories source folders, upgraded app files, media, route coverage, PWA files, and completion-gate risk before release.

Run scripts/factory-scan.mjs or use the backend scan route to load the latest report.

Asset Vault

Keep every logo, video, poster, proof file, and provenance note tied to the client.

Design Lab

Use real product DNA instead of stamping one generic style onto every client.

Factory Run

Run core, enhance, verify, or the full lane from one workbench.

01 Core

Clone the white-label base, stamp client data, and package the app shell.

02 Enhance

Pull live surfaces, generate bespoke media, and inject niche-specific upgrades.

03 Verify

Audit routes, artifacts, and release gates before anyone calls the run done.

04 Full Factory

Run the whole chain and move the client into proof-ready state.

Stage console

Live response from the pipeline.

Select a client record, then run a stage or the full factory.

Path manifest

Current generated folder map.


          

Workspace

Track the client handoff, leads, workspace messages, and continuation readiness.

The live counters and allowance summary stay pinned in the inspector so they are visible during every build. This room is where the client handoff stays clear: what their app captures, where the lead persists, and how the owner uses the workspace after launch.

  • Preview access stays tied to the selected client.
  • Workspace tester days and command allowance stay visible during build and proof.
  • Client app requests write FS27 lead, contact, activity, source, campaign, and workspace metadata.
  • Relay13 opens the client-specific thread and ConnectLog mirrors the relationship event for follow-up.
  • Continuation discount timing stays connected to SkyePay instead of drifting into notes.

Client use

What they can do after you ship.

  • Share the app link or QR code from the nav download button.
  • Capture quote, contact, booking, service, and support requests from mobile.
  • Open their workspace to see new requests in one company lane.
  • Reply manually or assign follow-up without losing the relationship trail.

Response policy

Local brain first, paid AI only on purpose.

  • Local routing classifies the request at no provider cost.
  • AI drafts stay off unless SkyePay shows the add-on active.
  • Starter is $35/mo with 125 included AI response messages plus a 31-message backup bucket.
  • Response Plus is $79/mo with 425 included messages plus a 76-message backup bucket.
  • Managed AI Inbox starts at $149/mo with 1,000 included messages plus a 222-message backup bucket.
  • After the paid and backup buckets are exhausted, lead capture still persists and the workspace falls back to local/manual mode.

Starter

Relay13 AI Response Starter

$35/mo · 125 + 31

Owner-reviewed AI drafts for low-volume teams that want help replying without turning on unmanaged provider spend.

Response Plus

Relay13 AI Response Plus

$79/mo · 425 + 76

Higher-volume response routing with expanded FAQ tuning, priority alerts, and the same no-loss backup behavior.

Managed AI Inbox

Relay13 Managed AI Inbox

From $149/mo · 1,000 + 222

AI triages, labels, drafts, sends allowlisted routine replies, starts follow-up timers, and escalates risky messages to a human.

SkyePay

Keep the preview-to-paid lane attached to the same client workflow.

Offer package

What continuation includes.

  • 7-day tester workspace
  • 7 scans included
  • 25 workspace commands included
  • Six-month continuation discount ready
  • Optional AI lanes: Starter $35/mo, Plus $79/mo, Managed AI Inbox from $149/mo
  • Backup buckets protect the owner from silent lead loss if a workspace has a traffic spike

Auren

Keep a live client-build copilot inside the factory.

Auren should understand the current client, the current reports, and what still needs work, then help us fix it without losing the operator thread.

Operator chat

Ask what is broken, what to improve, or what to ship next.

Proof

Browser proof, screenshots, receipts, and client-readable evidence.

Factory workflow recording

The proof reel is created by Playwright while the browser runs the factory flow: Valley import, factory pass, route map, scanner, and proof room checks.

Surface captures

Desktop and mobile proof from this exact served app.

Desktop screenshot of the Client App Factory operating surface
Desktop operator surface
Mobile screenshot of the Client App Factory operating surface
Mobile operator surface

Deploy

Review publish target, then ship without losing the trail.

Release lane

The inspector carries the live gate and publish target.

The deploy console stays visible in the right-hand inspector so you can cross-check publish folders and final QR targets while you’re still working.

Deployment note

Use the generated package and proof room together.

Before ship, open the packaged app from Operations, confirm the proof room is green, and only then promote the final route and QR target.

Wiring

Keep the repo, MCP, payment lane, and deployment path explainable.