House operations and secure operator access

HouseOperations and SkyeBox now sit inside the 0S.

I wired the house command platform and the encrypted authenticator vault into the same operating deck so task pressure, vendors, owner alerts, proof receipts, tutorial runs, billing intents, and local TOTP custody can be shown from one 0S route. The apps stay usable as static browser-local tools, with proof boundaries stated before anyone mistakes them for a managed cloud service.

What expanded

This is an operational expansion, not a loose link dump. HouseOperations is the app-first command room. SkyeBox is the local encrypted authenticator vault nested under it. The main 0S surfaces now have a route, commercial scope, tutorial, billing intent, proof receipt, and browser test path for both.

Commercial scope decision

The base 0S plans still include HouseOperations, and standalone HouseOperations now has paid offers.

Starter and Growth keep the included HouseOperations scope already published in 0S pricing. For clients who only want the house-command lane, SkyePay now has HouseOperations Command at $2,500 setup + $497/mo and HouseOperations Managed at $5,000 setup + $997/mo. Payment, approval, and activation remain SkyePay/FS27 responsibilities.

starter

Local operator lane

HouseOperations preview, one local SkyeBox vault handoff, and setup guidance without claiming managed security custody.

growth

House workspace

One HouseOperations workspace, three operator vault instances, and proof export support alongside ConnectLog and Relay13.

autonomous

Managed operating rooms

Three HouseOperations workspaces, eight vault instances, Cloudflare readiness, owner alerts, and daily operating digest paths.

standalone

HouseOperations Command

$2,500 setup + $497/mo for one command room, one local SkyeBox handoff, tutorial/claim contract, and SkyePay/FS27 activation.

managed

HouseOperations Managed

$5,000 setup + $997/mo for managed rollout, weekly proof review, multiple vault handoffs, and custom event mirror policy.

Boundary

SkyeBox is local-first

It does not create a cloud account, sync secrets to a server, recover forgotten passwords, or replace enterprise password-manager policy.

HouseOperations is static-local here

The folder owns its local state and static endpoints. Cloud persistence requires a future Worker/D1/KV scope.

Billing is explicit

HouseOperations creates a billing intent and SkyePay offer URL. It does not mark itself paid; FS27/SkyePay owns checkout, owner approval, and policy activation.