# Atlas OS v2 Product Scope

## Product decision

Atlas OS is The Wizards’ Customer Zero implementation of W-BOS. W-BOS is the reusable framework and embedded Kernel; it becomes a commercial product only after internal evidence. Version 2 expands the founder operating loop just enough to connect the company’s most important recurring reality: client demand, authorized delivery, cash, exceptions, evidence, and learning.

## Committed workflows

1. Weekly Founder Operating Review
2. Client Lead-to-Cash
3. Project Delivery Control

They operate on a shared canonical model, not three separate applications.

## Implemented v2 capabilities

| Capability | Implementation |
|---|---|
| Organization and authority | Tenant boundary, memberships, five practical roles, locale, current horizon |
| Executive governance | Outcomes, issues, decisions, commitments, exceptions, evidence, reviews, human approval |
| Relationships | Organization/person profiles, stage, owner, interaction timeline, next action |
| Sales | Opportunities, probability, value/currency, next step, proposal versions, win/loss conversion |
| Delivery | Projects, status/health, milestones, acceptance criteria/evidence, linked control records |
| Finance | Accounts, invoices, collections, expenses, same-currency transfers, derived balances and project cash |
| Evidence and memory | Private files, checksums, authority/freshness, comments, expected/actual outcomes, lessons |
| Governance and assurance | Role permissions, tenant validation, audit history, status command, explicit AI ceiling |
| KPI telemetry | Definition, formula, source, target, guardrail, confidence, and measurements |
| Experience | Responsive workspaces, workflow pulse, English-first locale, Arabic/RTL-ready shell |

## Explicitly outside v2

- Double-entry general ledger, bank reconciliation, tax filing, payroll, inventory, procurement, and statutory accounting
- Marketing automation, email synchronization, telephony, customer portal, e-signature, and payment gateway
- Resource scheduling, timesheets, advanced dependencies, Gantt charts, and portfolio capacity planning
- Public registration, subscription billing, tenant self-service, and broad commercialization
- Atlas Core extraction, Studio, marketplace, editions, public API, or partner ecosystem
- Autonomous authority, automatic cash posting, or unreviewed consequential external action
- Native mobile app, multi-region architecture, enterprise SSO, and data warehouse
- Full Arabic translation before terminology, translator, and review ownership are approved

These are not forgotten requirements. They are evidence-gated expansions that should integrate through the existing identities and audit contract.

## Customer Zero acceptance gate

Run v2 for an 8–12 week operating cycle. Progression requires:

- all three workflows used on representative work without continuous founder rescue;
- at least one relationship moving from opportunity through accepted delivery and collected cash;
- at least one material executive decision linked to project/financial evidence;
- accepted milestones and visible exceptions with accountable owners;
- complete cost, manual intervention, incident, and limitation evidence;
- no unresolved critical tenant, security, privacy, continuity, or cash-integrity blocker;
- no customer-specific fork in core workflow semantics;
- measured reduction in chase work, retrieval time, decision latency, or rework;
- a documented go, narrow, repeat, defer, or stop decision.

## Next evidence-gated releases

- **v2.1:** approved notification cadence, reminders, CSV import/export, retention controls, and password reset/MFA.
- **v2.2:** Arabic content pack, terminology QA, printable proposal/invoice documents, and customer-facing acceptance links.
- **H1 design partners:** API/integration layer, supervised queue operations, external identity requirements, and commercial tenancy controls.

No date or capability claim should be published until the corresponding gate has accepted evidence.