OmegaCrownAI Sovereign AI Company OS

Build your full AI company, not just one small tool.

Sovereign AI Company OS organizes OmegaCrownAI into powerful departments: websites, apps, coding, automation, trading, creative, marketing, finance, customer operations, security, reliability, and project workspaces.

Website Builder

Website Department

Build premium business websites, landing pages, service pages, funnels, SEO-ready pages, and launch-ready customer experiences.

Open Website Department →

App Builder

App Department

Build dashboards, SaaS apps, portals, business systems, customer apps, internal tools, and full-stack product workflows.

Open App Department →

Coding Workspace

Coding Department

Generate, edit, debug, review, refactor, test, and ship production code through OmegaCrownAI project workspaces.

Open Coding Department →

Automation Builder

Automation Department

Build AI agents, business workflows, scheduled jobs, execution pipelines, lead follow-ups, reporting systems, and operations automations.

Open Automation Department →

King Trading System

Trading Department

Build King Trading System dashboards, market discovery, watchlists, forecast quality controls, alerts, and research tools.

Open Trading Department →

Creative Studio

Creative Department

Build content systems, videos, image prompts, brand assets, campaigns, scripts, and production-ready creative pipelines.

Open Creative Department →

Marketing Engine

Marketing Department

Build campaigns, funnels, customer acquisition systems, copy, landing strategies, distribution plans, and growth workflows.

Open Marketing Department →

Finance Ops

Finance Department

Build revenue tracking, payment flows, provider management, billing readiness, financial dashboards, and business controls.

Open Finance Department →

Customer Ops

Support Department

Build customer support workflows, onboarding, help systems, customer operations, readiness checks, and response pipelines.

Open Support Department →

Governance

Security & Governance

Build safety policies, audit trails, access controls, identity verification, compliance evidence, and governance workflows.

Open Security & Governance →

Reliability

Reliability Department

Build monitoring, incident response, replay systems, job reliability, cost controls, and production-grade operational checks.

Open Reliability Department →

Workspace OS

Projects & Workspaces

Open the full workspace layer where Sovereign AI Company projects, departments, memory, execution, and build history live.

Open Projects & Workspaces →

Start Here

New customer? Start with this path.

The Sovereign OS now has many departments, artifacts, downloads, and validation checks. Use this simple path first: build a website, download a starter, then verify readiness.

Start Website Builder

01Recommended

Start Website

Start Website Builder

Best first step for most customers. Generate website structure, copy, SEO, and deployment checklist.

Open →

Download ZIP

Download Full-Stack Website/App

Get sovereign-website-starter.zip with HTML pages, CSS, SEO, brand direction, and checklist.

Open →

Download Trading

Open Trading Bundle

Download the paper-trading starter repository. Live trading remains disabled.

Open →

Check Status

Check Readiness

Verify release status, workspace stability, smoke tests, and safety gates.

Open →

Customer journey

Choose department → Generate artifact → Download starter → Validate checks → Launch or continue building

Recommended first move

Start with the Website Builder first. It is the easiest customer-facing artifact to understand, download, inspect, and deploy. Then use the Trading Builder only when paper-trading safety is understood.

Self-Improvement Engine

OmegaCrownAI learns safely, repairs syntax, and validates before release.

This control layer turns lessons from build errors, broken routes, shallow outputs, and unsafe workflows into stronger validation rules, better builder prompts, and safer upgrade discipline.

Open Engine API Run Engine Smoke Test

Self-Repair

Build-safe

Detect syntax, build, route, 404, 502, and deployment failures.

Evaluation

Benchmarked

Score builders for depth, accuracy, syntax, safety, and usefulness.

Accuracy

Evidence-aware

Separate verified facts, memory, inference, and live-check needs.

Guardrails

Protected

No PM2 restart before build, no git add ., no unsafe live trading.

Production rule

Build first → smoke test → restart PM2 → verify production → commit targeted files.

Self-improvement smoke-test results

The Self-Improvement Engine passed validation: required engines, production guardrails, release sequence, learning ledger, and build-before-restart rule are present.

Open Engine Smoke-Test JSON

Smoke Test

7/7 passed

Self-improvement engine validation passed.

Engines

Self-repair, syntax repair, evaluation, accuracy, prompt quality, model router, and ledger.

Guardrails

Production safety rules are registered.

Release Steps

Build, smoke test, restart, verify, commit, and log checks are defined.

Full-Function Artifact Standard

OmegaCrownAI must deliver full-function customer artifacts.

No shallow output. No only-front-page website when backend is needed. No missing preview, review, download, validation, README, deployment, or next action.

Open Standard API Run Standard Smoke Test

Customer-ready target

90–110%

Minimum 90%, premium 100%, elite above-competitor target 110%.

Core requirements

Frontend, backend, preview, download, README, validation, missing-info, deployment, next action.

Builder coverage

Website/App, Trading, Automation, Coding, Creative/Marketing.

No shallow output

Enforced

No paid/customer artifact should stop at only a homepage or blueprint.

Platform rule

Every paid/customer project should target 90–110% customer-ready output: real artifact, functionality, validation, review, export, and next action.

Builder Output Depth Scoring

Every builder output is now scored against the full-function standard.

Website/App, Trading, Automation, Coding, and Creative outputs are checked for real functionality, preview/review, download/export, validation, missing-info, deployment, and next action.

Open Website Score Run Depth Smoke Test

Website/App

110%

Frontend, backend/API, review panel, download, validation, deployment.

Trading

110%

Paper-trading repo, risk safety, README, smoke test, download.

Automation

110%

Trigger, actions, approvals, logs, retry/failure handling, review.

All builders

Scored

Builder output depth now uses the Full-Function Artifact Standard.

Depth rule

Builder output depth now means full-function delivery, not just longer text. The score checks functionality, files, preview, export, tests, deployment, and customer next action.

Sovereign Execution Layer

OmegaCrownAI now has the blueprint for safe execution.

This is the next step after reasoning: registered actions, approval gates, sandbox rules, replayable audit logs, rollback requirements, and production safety.

Open Execution API Run Execution Smoke Test

Execution categories

Software, Website/App, Trading, Automation, API/tool, Production deployment.

Approval gates

Low risk, medium risk, high risk, and blocked-by-default actions.

Replayable actions

Required

Every action should record id, inputs, outputs, status, error class, and rollback.

Production safety

Enforced

Build before restart, no git add ., smoke checks, clean PM2 logs.

Execution rule

OmegaCrownAI should execute only through registered actions, scoped permissions, approval gates, sandbox rules, audit logs, and rollback-aware workflows.

Multi-Agent Memory Registry

OmegaCrownAI now has the blueprint for governed long-term memory.

Memory is partitioned by role, source-labeled, auditable, correctable, and governed so agents can remember project truth without hiding uncertainty.

Open Memory API Run Memory Smoke Test

Memory partitions

Customer, project, artifact, execution, governance, and learning ledger memory.

Confidence labels

Verified, user-declared, project memory, inferred, needs verification, unsafe/blocked.

Governed writes

Required

No hidden memory, no secrets, no inferred claims stored as verified facts.

Replay review

Auditable

Phase, deployment, artifact, and failure memory must be reviewable.

Memory rule

OmegaCrownAI memory must be scoped, source-labeled, auditable, correctable, and never used to present inferred information as verified truth.

Governance, Permissions & Audit

OmegaCrownAI now has the blueprint for accountable sovereign control.

Every high-value action should pass through role permissions, approval gates, blocked-action rules, compliance hooks, audit evidence, and rollback-aware records.

Open Governance API Run Governance Smoke Test

Roles

Owner, Admin, Builder Agent, Execution Agent, Governance Agent, Viewer.

Approval gates

Read-only, artifact generation, workspace write, production, external write, blocked.

Audit trail

Required

Every high-value action needs actor, role, permission, risk, evidence, status, and rollback.

Blocked actions

Protected

Secrets, live trading, destructive deletes, failed-build restarts, and git add . are blocked.

Governance rule

No sovereign execution without permissions, approval gates, audit trail, compliance review, and rollback-aware accountability.

Deployment / Self-Hosting Readiness

OmegaCrownAI now tracks deployment sovereignty.

Sovereignty means portability, recoverability, environment documentation, health checks, backup/restore, and future Docker/Kubernetes/self-hosting paths.

Open Deployment API Run Deployment Smoke Test

Deployment modes

Managed SaaS, VPS, Docker Compose, Kubernetes/private cloud, offline future.

Environment registry

Documents runtime variables, app URL, database, model keys, and storage provider.

Backup / restore

Required

Database, uploads, env, code, and PM2/runtime recovery plans.

Self-hosting

Planned

Docker, compose, env example, healthcheck, backup scripts, and README.

Deployment rule

OmegaCrownAI should be recoverable, portable, documented, smoke-tested, and eventually self-hostable through Docker, private cloud, or on-prem modes.

Enterprise Reliability & Observability

OmegaCrownAI now tracks enterprise reliability signals.

Enterprise operation requires health categories, incident severity, error-class routing, metrics, structured logs, alert rules, and recovery evidence.

Open Reliability API Run Reliability Smoke Test

Health categories

Application, API, artifact generation, deployment, governance, customer experience.

Incident levels

SEV0, SEV1, SEV2, and SEV3 response classes.

Error classes

Build, runtime, API contract, artifact validation, governance, deployment.

Observability

Tracked

Metrics, structured logs, alert rules, scorecard, and operational checks.

Reliability rule

Every enterprise-grade system needs visible health, classified errors, measurable reliability, alerting, recovery paths, and audit-ready operational evidence.

Connector / Integration Marketplace

OmegaCrownAI now has the foundation for governed integrations.

Connectors must use scoped permissions, credential safety, approval gates, manifest validation, install review, webhook rules, audit logs, and disconnect policies.

Open Connector API Run Connector Smoke Test

Connector categories

Communication, CRM, storage, development, payments, marketing, models, webhooks.

Permissions

Read, draft write, external write, financial action, secret management.

Credential safety

Required

No secrets in code, logs, UI, artifacts, commits, or client-side bundles.

Marketplace flow

Governed

Install review, scoped permissions, healthcheck, audit, and disconnect policy.

Connector rule

No connector should execute external writes, expose secrets, publish public content, or perform financial actions without scoped permissions, approval gates, and audit evidence.

Sovereign Connector Manifest Validator

OmegaCrownAI now validates connector manifests before install.

Every connector must define safe auth, scoped permissions, actions, schemas, approval gates, audit requirements, healthchecks, disconnect policy, and data retention.

Open Validator API Run Validator Smoke Test

Manifest fields

Connector id, name, category, version, auth, permissions, actions, healthcheck, policies.

Action fields

Action id, name, input schema, output schema, approval gate, audit required.

Validation

Required

Connectors must pass validation before install, approval, execution, or marketplace listing.

Unsafe actions

Blocked

Financial, external write, high-risk, unknown permission, and unaudited actions are blocked.

Validator rule

No connector should be installed, approved, listed, or executed unless its manifest passes permissions, auth, action, approval-gate, audit, and safety validation.

Connector Install Review UI

OmegaCrownAI now reviews connectors before install.

Every connector must show permissions, risk, auth type, actions, approval gates, credential safety, validation score, healthcheck, disconnect, and blocked action warnings.

Open Install Review API Run Install Review Smoke Test

Review sections

Identity, permissions, risk, actions, credentials, healthcheck, blocked actions.

Install states

Ready, failed, approval required, approved, limited, active, blocked.

Admin checklist

Scope, auth, actions, audit, secrets, validator, healthcheck, disconnect, retention.

Install safety

Required

No silent install. External writes, publishing, and financial actions require gates.

Install review rule

No connector should be silently installed. Users/admins must review permission scope, credential safety, approval gates, external-write risk, and disconnect policy first.

Connector Permission Gate API

OmegaCrownAI now gates connector actions before execution.

Runtime connector actions are evaluated before they run: allow, require approval, or block based on permission, approval gate, risk level, audit context, and blocked-by-default rules.

Open Permission Gate API Run Gate Smoke Test

Decisions

Allow, require approval, or block before connector execution.

Permissions

Read, draft write, external write, financial action, secret management.

Blocked rules

Financial, secrets, unknown scopes, unsafe gates, high-risk actions.

Audit fields

Connector, action, permission, gate, risk, decision, actor, approval, input, rollback.

Runtime gate rule

Connector review is not enough. Every connector action must pass a runtime permission gate before execution, especially external writes, secrets, and financial actions.

Connector Audit Trail Integration

OmegaCrownAI now records connector permission decisions.

Every connector action decision should leave an audit record with actor, role, connector, action, permission, risk, decision, evidence, and rollback/recovery context.

Open Audit API Run Audit Smoke Test

Audit fields

Actor, role, connector, action, permission, gate, risk, decision, evidence, rollback.

Policies

Read-only, external writes, blocked actions, financial, secrets, high-risk, no raw secrets.

Decisions

Audited

Allow, require approval, and block decisions produce audit-ready records.

Recovery

Required

High-risk, external-write, and blocked actions need rollback/recovery context.

Audit trail rule

Every connector decision should be audit-ready. No secrets in records, no untraceable external writes, and no high-risk execution without recovery context.

GitHub Connector Blueprint

OmegaCrownAI now has its first governed development connector blueprint.

GitHub starts as read-only and draft-only: repository reading, issue review, branch planning, PR draft preparation, release-note drafting, permission gates, and audit records.

Open GitHub API Run GitHub Smoke Test

Connector actions

Read repo, read issues, branch plan, PR draft, release-note draft.

Default mode

Read/Draft

No direct push, merge, deploy, release, or secret changes by default.

Validation

Required

Manifest validation, permission gate, install review, and audit trail.

Blocked actions

Main push, merge, delete, production release/deploy, secrets, branch rules.

GitHub connector rule

GitHub actions must remain read/draft by default. Direct push, merge, production release, deployment, secret changes, and destructive repo actions require explicit approval and audit evidence.

Full-Function Artifact Output

Builder output now shows full-stack customer-ready evidence.

OmegaCrownAI now exposes the artifact score, generated file layers, preview path, download path, validation result, missing-info reporting, and homepage-only block rule.

Open Output API Run Output Smoke Test

Biscuit shop bundle

22 files

Frontend, backend/API, database/schema, admin, preview, deploy, validation, and reports.

Customer-ready score

100/100

Full-stack generated artifact passes; homepage-only stays blocked.

Preview path

Ready

Artifact preview and admin preview links are part of the generated output.

Download path

Ready

Customer download route is connected with draft/customer-ready labeling.

Homepage-only output remains blocked

A frontend-only homepage cannot be labeled customer-ready. Customer-ready output requires backend/API, database/schema, admin review, preview, deployment package, validation report, and missing-information report.

Full-Stack Builder Runtime Correction

OmegaCrownAI is not fully complete yet — the customer artifact builder is being upgraded now.

The system must not claim full completion while website/app outputs are still missing backend, database/data model, admin review, preview, export, and validation. Phase 250 starts the real full-stack builder runtime standard.

Open Runtime API Run Runtime Smoke Test

Customer-ready score

90+

No artifact should be called customer-ready below 90 or with missing required layers.

Required layers

Frontend, backend, data model, admin/review, preview, export, validation, deployment guide.

Current correction

Active

OmegaCrownAI must stop front-page-only website builds.

Truth label

Not complete yet

The builder runtime is being upgraded into a real full-stack artifact generator.

Customer-ready artifact rule

Homepage-only output is not enough. A customer-ready website/app must include frontend, backend/API, database or data model, admin/review path, preview, downloadable export, README/deployment guide, validation report, and missing-information report.

Sovereign Enterprise Foundation Complete

Phase 200 completes the OmegaCrownAI enterprise sovereignty foundation.

OmegaCrownAI now has the blueprint foundation for full-function artifacts, execution, memory, governance, deployment, reliability, connectors, permission gates, audit trails, and the first GitHub connector blueprint.

Open Phase 200 Summary Run Phase 200 Smoke Test

Foundation layers

Artifacts, execution, memory, governance, deployment, observability, connectors.

Readiness pillars

Artifact delivery, safe execution, memory, governance, deployment, reliability, connectors.

Production rules

Build before restart, targeted git, no secrets, validation, smoke checks, audit gates.

Next era

Implementation

Persistent storage, real OAuth connectors, execution runner, health dashboard, self-hosting.

Completion rule

The foundation is complete. The next era should move from blueprint APIs into durable persistence, real OAuth connectors, real execution runners, operational dashboards, and self-hosting packages.

Customer Onboarding

Start building with Sovereign AI Company OS

Follow this flow to move from account access to department selection, project creation, routed workspace execution, and release readiness validation.

Login or create your account

Start with a secure account so projects, workspaces, memory, and release checks stay connected.

Choose a department

Pick the business area you want to build: Website, App, Automation, Trading, Marketing, Finance, Support, and more.

View Departments →

Start a department project

Use Start Department Project to create a real project record under the company workspace.

Start Website Project →

Open the routed workspace

OmegaCrownAI automatically sends each project to the correct workspace for building and execution.

View Routing Matrix →

Check release readiness

Use the readiness dashboard to confirm routing, stability, smoke tests, and protected real-run gates.

Open Readiness API →

Recommended first path

Sign up, open the Website Department, start a department project, then follow the routed workspace. After that, use the Release Readiness dashboard to confirm the system is ready.

Release Readiness

Sovereign OS release status: Ready

The core Sovereign builder flow is now validated across department routing, workspace stability, dry-run smoke testing, and protected real-run project creation.

Open Readiness API

Passed

Sovereign Flow Matrix

12/12

All departments route to their correct workspace.

Passed

Workspace Stability

4/4

Builder data panels are restored for Website, App, Automation, and Trading.

Safe

Smoke Test Dry-Run

4/4

Default smoke test validates routes without creating project records.

Protected

Real-Run Gate

?run=true

Real project creation is intentional and gated.

Release gate: green

Routine smoke checks are dry-run safe. Real project creation remains protected behind explicit ?run=true.

Builder Output Depth

Move from blueprint-only to real build artifacts

Each Sovereign builder department should produce structured outputs that can become real websites, apps, automations, code repositories, or paper-trading systems — not only planning text.

Open Output Depth API

Website

Website pages + copy

Page tree, homepage sections, service copy, SEO, deployment checklist

App

Product build spec

Screens, user flows, data model, API plan, release checklist

Automation

Workflow execution plan

Triggers, actions, approvals, logs, replay, failure handling

Trading

Paper-trading system package

Agents, risk rules, repo plan, backtest plan, live safety gate

Coding

Implementation repo plan

File tree, implementation steps, tests, validation, deployment plan

Phase 158 upgrade target: every builder should create artifacts, next actions, and readiness checks.

Website Builder Artifact Depth

Website Builder now produces full-stack website/app artifacts

The Website Builder output now includes page tree, homepage sections, starter copy, SEO metadata, brand direction, conversion plan, deployment checklist, and next actions.

Download Full-Stack Website/App Open Website Artifact Run Website Smoke Test

Page tree

Included in the Website Builder artifact package.

Starter copy

Included in the Website Builder artifact package.

SEO metadata

Included in the Website Builder artifact package.

Deployment checklist

Included in the Website Builder artifact package.

Customer-ready website path

Prompt → Website artifact → page copy → preview layout → SEO/readiness check → deployment.

Full-stack Website/App smoke-test results

The downloadable Website Builder starter bundle has passed validation: frontend, backend/API starters, review panel, SEO metadata, deployment checklist, and smoke-test files are included.

Open Website Smoke-Test JSON

Smoke Test

9/9 passed

All Website starter bundle checks passed.

Required Files

9/9

README, pages, CSS, SEO, brand, and checklist are present.

ZIP Bundle

Ready

sovereign-website-starter.zip is available for download.

SEO + Deployment

Ready

SEO metadata and deployment checklist are included.

Trading Code Artifact

Generate the paper-trading repository plan

The Trading Builder now has a concrete code-repository artifact plan with agents, config, risk engine, backtest engine, dashboard starter, Docker files, and README. Live trading remains locked behind explicit safety review.

Open Trading Repo Artifact

Agent files

Included in the Trading Builder repository artifact plan.

Risk engine

Included in the Trading Builder repository artifact plan.

Backtest engine

Included in the Trading Builder repository artifact plan.

Paper-trading lock

Included in the Trading Builder repository artifact plan.

Actual starter file contents are ready

The next generator returns real starter code for main.py, agents, risk engine, dashboard, backtest engine, Docker files, tests, config, and README.

Download saits-v1.zip View 8/8 Smoke Test Inspect File JSON

How to run the generated repo

After downloading saits-v1.zip, unzip it and run the starter system locally in paper-trading mode.

Download ZIP Check README

Setup

unzip saits-v1.zip
cd saits-v1
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt

Run

python main.py
streamlit run dashboard.py
pytest

Safety

The generated repository is paper-trading only. Live trading is disabled by default. Do not add real broker keys until code review, paper testing, risk review, and manual approval are complete.

Customer download flow

Follow this simple path after generating the Trading Builder repository. Download first, validate the README and smoke test, then run locally in paper-trading mode.

Download saits-v1.zip

Download ZIP

Get saits-v1.zip with the generated paper-trading starter repository.

Download →

Check README

Verify setup, run, test, dashboard, and safety instructions.

Check →

Smoke Test

Confirm 17/17 generated files, paper mode, and live trading disabled.

Validate →

Run Locally

Unzip the repo, install dependencies, run main.py, dashboard, and pytest.

Inspect →

Stay Safe

Keep paper trading only until review, testing, and manual approval are complete.

Review →

Safety reminder

This generated bundle is for paper trading only. Live trading is disabled by default. Do not add real broker keys until paper testing, code review, risk review, and manual approval are complete.

Bundle smoke-test results

The downloadable Trading Builder bundle has passed structural validation: required files are present, paper-trading safety is active, and live trading is disabled.

Open Smoke-Test JSON

Smoke Test

8/8 passed

All Trading Builder bundle checks passed.

Generated Files

17/17

All required starter files are present.

ZIP Bundle

Ready

saits-v1.zip is available for download.

Safety Mode

Paper only

Live trading remains disabled by default.

Built for full capacity

This hub is designed as the top-level company operating system. Each department can keep expanding with its own dashboards, builders, agents, workflows, execution logs, quality controls, memory, governance, and production readiness checks.

Sovereign Flow Matrix

12 departments routed to the right workspace

Every department has a Start Department Project flow. When a project is created, OmegaCrownAI routes it to the correct workspace automatically.

Open Matrix API

Department

Workspace Route

Status

Website Department

/sovereign/website

/build/website/[projectId]

Ready

App Department

/sovereign/app

/build/app/[projectId]

Ready

Coding Department

/sovereign/coding

/projects/[projectId]

Ready

Automation Department

/sovereign/automation

/build/automation/[projectId]

Ready

Trading Department

/sovereign/trading

/build/trading/[projectId]

Ready

Creative Department

/sovereign/creative

/projects/[projectId]/company/creative-studio

Ready

Marketing Department

/sovereign/marketing

/projects/[projectId]/company/marketing

Ready

Finance Department

/sovereign/finance

/projects/[projectId]/company/finance

Ready

Support Department

/sovereign/support

/projects/[projectId]/company/support

Ready

Security & Governance

/sovereign/security

/projects/[projectId]/company/governance

Ready

Reliability Department

/sovereign/reliability

/projects/[projectId]/company/reliability

Ready

Projects & Workspaces

/sovereign/workspaces

/projects/[projectId]/company/workspaces

Ready

Matrix result from Phase 142: 12 departments checked, 12 passed. This panel makes that routing visible to customers and operators.

Workspace Stability

4 builder workspaces have restored data panels

The Website, App, Automation, and Trading workspaces now keep the premium customer-ready layout while restoring project-backed builder data, build history, active build context, and draft outputs.

Open Stability API

website

Website Workspace

Stable

/build/website/[projectId]

Data Panel

WebsiteBuildWorkspace

Project, builds, active build, website draft payload

app

App Workspace

Stable

/build/app/[projectId]

Data Panel

App project/build history panel

Project record and app-domain build history

automation

Automation Workspace

Stable

/build/automation/[projectId]

Data Panel

AutomationWorkspace

Project, builds, active build, automation flow payload

trading

Trading Workspace

Stable

/build/trading/[projectId]

Data Panel

TradingWorkspace

Project, builds, active build, strategy draft payload

Stability result from Phase 146: 4 builder departments checked, 4 passed.

Real Project Smoke Test

Verify real created projects open real workspaces

This smoke test now opens in safe dry-run mode by default. It verifies route shape without creating records. Add ?run=true only when you intentionally want to create real smoke-test projects.

Open Dry-Run Smoke Test

Website

Real Workspace

Dry-run checks route shape by default. Real project creation requires ?run=true.

Smoke-test ready

App

Real Workspace

Dry-run checks route shape by default. Real project creation requires ?run=true.

Smoke-test ready

Automation

Real Workspace

Dry-run checks route shape by default. Real project creation requires ?run=true.

Smoke-test ready

Trading

Real Workspace

Dry-run checks route shape by default. Real project creation requires ?run=true.

Smoke-test ready

Use dry-run mode for routine checks. Use /api/sovereign/real-workspace-smoke?run=true only before major releases when real test project creation is intentional.