🎥 Real 0S browser proof

I recorded the 0S from customer signup through owner-side proof surfaces.

This walkthrough shows the actual MetrAIyux 0S screens: customer signup, onboarding, service selection, workspace setup, billing intent, customer command routing, admin brain response, local brain retrieval, NEXUS routing, CROWN command, and the proof vault. No private `.env` values or owner secrets are shown.

8:07 proof walkthrough I use the customer menu, owner/admin command surfaces, local brain, NEXUS routing, CROWN rooms, and proof vault so buyers can see the system instead of trusting empty claims. ⚡

🧾 What the recording proves

The video follows the path a buyer actually cares about.

We show the sellable flow end to end: a customer can enter the system, pick services, generate a workspace record, create a billing intent, send work through the customer dashboard, and see that work route into brain-led operating surfaces.

01

Customer entry

Signup, onboarding, company profile, services, and workspace setup create local receipts.

02

Sellable lane

Billing intent captures plan and payment preference without charging in static proof mode.

03

Customer command

The customer dashboard routes a command into the operating brain path with approval required.

04

Owner command

The admin brain responds, records a ledger, and keeps protected actions behind approval gates.

05

Brain proof

The local brain answers from the included company corpus, while NEXUS classifies a business signal.

06

Proof vault

CROWN and the proof center frame public claims as evidence work, not unsupported marketing.

📸 Proof states

I keep the screenshots under the video so the receipts are inspectable.

The long video is the main proof. These frames are the high-signal checkpoints from the same browser-driven capture path.

🔐 Honest boundary

This proof shows the product path without leaking private controls.

Static mode creates browser-local receipts. Production mode still depends on configured Cloudflare Workers, D1/KV/Queues, provider credentials, Stripe or invoicing, Resend, and SkyeGateFS27 auth. That boundary is good: buyers see the workflow, while private keys and owner-only controls stay off the public page.