Architectural spec — v1.0
ORBWEVA OS
The canonical definition. What it is, what's in it, and what it deliberately isn't.
1. Definition
ORBWEVA OS is a methodology-driven operating system for founder-led businesses.
It integrates four components — a strategic methodology (CORE), a structured knowledge layer (ARC), an autonomous execution layer (AER — Acquire, Engage, Retain) that today executes CORE Ring 2's sales + marketing surface, and a unified visibility layer (Grow) — plus a self-serve entry point (Labs).
ORBWEVA OS is a business OS in trajectory; GTM is the first executable surface today. Executable surfaces for the remaining CORE rings — Finance ops, People ops, Product ops, Strategic ops — are the OS's named direction. See "Where this is heading" below.
One CORE Assessment configures the whole OS. Everything downstream — ARC entries, AER workflows, Grow dashboards — is grounded in the Calibration Document produced by that assessment. The methodology is not advice on top of the tooling; it's the configuration spec the tooling reads from.
Running the OS looks like this: a founder spends 60–90 minutes a week reviewing Grow, approves or redirects AER agents based on what Grow shows, and re-runs a CORE checkpoint quarterly. The agents work the other 168 hours.
Audience: pre-revenue solo founders through ~$50M ARR. Sweet spot $1–10M ARR. Stretch tier $10–50M with caveats (team-scoped ARC + per-department Grow are roadmap).
2. The stack
Four layers in dependency order. CORE configures ARC. ARC grounds AER. AER produces signals for Grow. Labs sits outside the chain and serves as a paid trial.
Methodology
The kernel. Configures the system.
Knowledge layer
It knows my business.
Execution layer
It runs without me.
Visibility layer
I see everything.
Self-serve entry
Let me try it first.
For the technically inclined: the OS analogue
ORBWEVA OS maps to an operating-system analogue if it helps. The mapping is a teaching aid, not a marketing position — we don't call CORE "the kernel" in client copy.
| Layer | OS analogue | Role |
|---|---|---|
| CORE | Kernel | Defines the system. Boots once. Re-boots quarterly. |
| ARC | System of record / syscall layer | Single read-only source every other layer queries. |
| AER | Userspace processes | Agents doing real work. Read from ARC, write to Grow. |
| Grow | Shell + observability | Operator interface. Logs, metrics, decisions. |
| Labs | Bootloader / live USB | Standalone execution without booting the full OS. |
3. What it deliberately isn't
Knowing what ORBWEVA OS isn't is as important as knowing what it is.
A CRM
HubSpot, Salesforce, Pipedrive own that. ARC integrates read-only with them, doesn't replace them.
A no-code automation platform
Zapier, n8n, Make own that. We use n8n internally; we don't sell it.
A course
Academy is a delivery mechanism for the OS, not the product. The product is the OS.
Business coaching
Coaching firms own that lane. ORBWEVA builds the system the founder operates.
An agent marketplace
We ship curated, ARC-grounded execution surfaces — not a 50-template marketplace. Curation is part of the value.
A general-purpose AI assistant
Claude, ChatGPT, Gemini own that. ORBWEVA agents are narrow, ARC-grounded, audit-trail-bound.
For businesses above ~$50M ARR
Above that, the OS needs team-scoped ARC, per-department Grow views, formal RBAC, audit trails — outside the current product. Different sales motion, different deployment.
One-line filter: if the founder needs to be convinced entrepreneurship is for them, or wants a coach to tell them what to do, or is on a VC track and wants board-level strategic advice — ORBWEVA OS is not for them. Above $50M ARR — also not for them.
Where this is heading
AER ships go-to-market execution today (CORE Ring 2's sales + marketing surface). ORBWEVA OS is heading toward executable surfaces for the rest of the business operating layer. Direction, not delivery — no timelines.
Same kernel (CORE). Same knowledge layer (ARC). Same operator interface (Grow). New userspace surfaces over time.
This is the public excerpt of the full spec. The internal version covers layer contracts, engagement sequence, surface tiers (Labs/Academy/Solutions), versioning, IP, and the full Direction section — available to Academy participants and Solutions clients on request.