Private Operator Surface

mojoOS turns revenue, delivery, and portfolio oversight into one controlled shell.

The dashboard is now private by default. Public visitors land here first, while authenticated operators move into the workspace, memory, governance, and proposal systems behind the access boundary.

Revenue

Deals, proposals, signatures, and delivery flow

Intelligence

Repos, memory, AI outputs, and operator evidence

Governance

Roadmaps, entropy, portfolio posture, and control-plane views

Access Boundary

What is public now

Landing and trust routes

The landing page and trust entry screens stay public and calm by design.

Public share experiences

Client-facing proposal and presentation share links remain public, scoped, and isolated.

Operator shell

Dashboard, memory, chat, connectors, admin, and governance routes now require an authenticated operator session.

Surface 01

Operator shell stays private

The workspace no longer doubles as the public homepage. Protected routes start at /dashboard.

Surface 02

Trust routes stay separate

Login and onboarding stay outside the operator chrome so they can remain calm, branded, and security-oriented.

Surface 03

Public sharing remains intact

Share-token routes continue to serve clients without exposing internal navigation or operator-only state.