May 27, 2026 · Bob's Smoke Shop · SkyeNet · Relay13 · SkyePay · sovereign client app proof

Bob's Smoke Shop is live on SkyeNet. That changes the pitch.

The important thing about Bob's build is not only that the app looks better. The important thing is that the client-facing promise is now a real lane: a local business can receive a branded landing experience, a workspace handoff, live team chat, QR-ready flyers, and a production route hosted through my own 0S SkyeNet surface.

This is the sales line I can stand behind: I am not handing a business a random WordPress page or a loose Netlify preview. I am handing them a live client app on the MetrAIyux 0S SkyeNet lane, with receipts.

The client-facing promise is simple.

When I walk into a local business, I can say: I personally built you a landing experience, I provisioned your workspace lane, and I can show you the live app before asking you to buy anything. If you like it, we activate it. If you do not like it, we edit it or take it down. That is a cleaner pitch than selling abstract software first and hoping the owner imagines the value.

Bob's Smoke Shop now has that shape. The app has an age gate, cinematic smoke-shop hero video, inventory and local SEO surfaces, blog routes, share controls, workspace preview, flyer lane, and a client-facing handoff that points back to Media Over London contact instead of stale private preview contact details.

Bob's public handoff links
  • Live SkyeNet app: https://metraiyux-0s-full-system.graylondonskyes.workers.dev/skyenet/bobs-smoke-shop/
  • Review pitch page: https://metraiyux-0s-marketing.pages.dev/bobs-smoke-shop-free-pilot
  • Print flyer page: https://metraiyux-0s-marketing.pages.dev/bobs-smoke-shop-free-pilot-flyer
  • Workspace login handoff uses the shared 0S lane, not an app-local password.
  • The flyer gives Bob the option to request a better SkyEmail handle before activation.

The proof is not vibes.

The latest live browser proof passed against the production SkyeNet URL. It checked forty-two routes, five media/assets, desktop and mobile app behavior, the age gate, the hero video, share controls, workspace preview, nonblank screenshots, and the workspace chat widget creating real Relay13 conversations from the deployed app.

That matters because a flyer is only useful if the thing behind the QR code behaves. Bob's flyer can point to the public pitch and the actual app because both routes are live. The workspace chat can be described as real because the deployed widget created Relay13 conversations in proof, including desktop conversation conv_bd40795b-4f60-4f54-a775-53b5c417b58f and mobile conversation conv_3da068e5-eec9-46eb-8236-68931542176a.

Live proof receipts
  • Browser proof receipt: test-artifacts/bobs-skynet-live-browser/2026-05-27T22-59-32-141Z/receipt.json
  • Result: ok: true, 42 route checks, 5 asset checks, 2 viewport proofs, 0 failures.
  • Good SkyeNet deploy receipt: test-artifacts/bobs-skynet-deploy/2026-05-27T19-02-39-558Z/receipt.json
  • Live route mode: the app serves through the 0S full-system Worker from the SkyeNet R2-backed deployment lane.
  • Direct operator asset repair was also proved when the already-bound SkyeNet deployment received the corrected widget, service worker, workspace preview, script, and CSS assets.

Why SkyeNet makes this stronger.

SkyeNet is the part of the story that lets the offer become more than "I made you a website." The route, proof, workspace, shared auth posture, and operator records are part of the same company operating system. The client app is not floating away from the business command center. It is tied to the infrastructure I use to run the company.

The honest version is still the strongest version. Cloudflare primitives can back the edge, but the customer-facing product is not a resale wrapper around a generic Pages account. The live route sits under MetrAIyux 0S SkyeNet, uses the 0S route registry and deployment assets, and can be connected to Founder Command, Relay13, ConnectLog, SkyEmail, AE Flow, SkyePay, and Citadel-style backup lanes as the offer expands.

Here is the boundary I will not fake.

The static edge deploy and route lane is live. Bob proves that. Relay13 workspace chat is live. Bob proves that too. SkyePay product mapping exists for SkyeNet offers. The managed/signed SkyeNet Functions lane is backed by the converter/runtime proof path. But I am not selling unrestricted hostile customer-uploaded arbitrary code as if it is already a fully isolated public function cloud. That is the reserved runtime phase.

What is backed right now
  • Static SkyeNet app deploy/routing: backed by Bob's live production app and browser proof.
  • Shared 0S owner/admin posture: backed by the FS27/SkyGate/Free99 gate rule and mounted-app auth pattern.
  • Relay13/ConnectLog chat: backed by real conversation creation from the deployed Bob widget.
  • SkyePay offer mapping: backed by the SkyeNet offer sync lane and SkyePay platform launcher proof scripts.
  • Managed/signed functions: backed by tools/skyenet-functions-convert.mjs, tools/skyenet-functions-runtime.mjs, and npm run 0s:skyenet:functions-proof.
  • Unrestricted arbitrary customer functions: reserved until the isolate/runtime boundary is finished and proofed.

SkyePay turns the free value into a clean upsell.

The free Bob-style pilot can carry real value without hiding the limits. The business gets a live app, a workspace handoff, chat, and proof. The upsell does not need to be pushy because the next needs are natural: custom domain, more workspace members, more messages, AI response add-on, managed edits, paid backup, stronger analytics, ads, and advanced SkyeNet hosting support.

That is why SkyPay matters. The offer catalog can map the free lane to paid activation without making the first conversation feel like a trap. Give the owner proof first, then let the platform show the value of limits, upgrades, and managed service.

The business-owner version.

A local owner does not need to understand every internal acronym. They need to understand this: "Your app is live. Your team workspace is ready. Your flyer scans to the proof. Your chat lane works. You can keep it, change it, or shut it down. If you want more capacity, more automation, a custom domain, or more help running it, we can activate that from the same 0S ecosystem."

That is the wedge. Bob's app turns the 0S from a huge founder system into a concrete local-business offer. It lets me walk in with generosity first and receipts second, then let the owner decide whether they want to keep the lane open.

Bob's Smoke Shop is not only a client app. It is the first clean proof that the free local-business pitch can land on sovereign 0S infrastructure and still connect to real workspace, chat, proof, and payment lanes.