Operate the system.
Don’t just watch it.
One operating system. Different missions.
Dominion OS brings intelligence, decisions, people, AI, workflows, software, and evidence into one governed operating environment.
The first public mission domains are Business and Politics. Google Cloud is the first cloud deployment path. Downloads, deployments, and live-runtime claims appear only when their evidence is registered.
Dominion OS is a governed operating environment for coordinating missions through intelligence, decisions, workflows, software, AI, and evidence. Public demonstrations and distribution metadata are deliberately separated from private source code, credentials, customer information, signing material, production controls, private APIs, and operational authority.
Business + Politics
Two first mission packs. One Dominion core. The domain changes the operating context, terminology, data, specialist views, and workflows — not the governing logic underneath.
Dominion OS for Business
Executive command and coordination across organizational intelligence, priorities, projects, operations, markets, finance, risk, stakeholders, decisions, and work.
Bring market evidence, assumptions, scenarios, decisions, owners, workstreams, and receipts into one mission workspace.
Dominion OS for Politics
Governed political operating infrastructure for public-source intelligence, issues, policy, communications, organizational operations, decisions, scenarios, and evidence.
Connect issues, policy, public intelligence, stakeholders, communications, organizational work, decisions, and evidence without fragmenting the mission.
Software and decision infrastructure. Fractal5 does not provide lobbying through this product surface.
A mission workspace, not another dashboard.
The GUI is designed to keep situation, intelligence, decisions, work, and evidence in one operating context. This schematic illustrates the interface model; it is not presented as a live-runtime screenshot.
Mission → Situation → Intelligence → Options → Decision → Action → Evidence
Intelligence becomes useful when it moves through a controlled decision loop and leaves durable evidence behind.
Mission
Define the objective, authority, constraints, and desired outcome.
Situation
Understand conditions, actors, systems, risks, and dependencies.
Intelligence
Structure sources, evidence, analysis, uncertainty, and forecasts.
Options
Compare scenarios, consequences, trade-offs, and courses of action.
Decision
Apply policy, judgment, approvals, and human authority.
Action
Move approved work into bounded execution and coordinated workflows.
Evidence
Preserve inputs, approvals, outputs, state, and receipts.
Make authority visible.
Dominion distinguishes machine assistance from human review, authority, execution, and evidence.
Release states are earned, not implied.
Every public download, deployment, or runtime claim must be represented by an approved public registry entry or current provider evidence.
No registry entry, no public availability claim.
Checking current catalogue…
Registered public release states will appear here. Missing evidence remains neutral.
The gateway remains available, but absent artifacts are not presented as released products.
Request AccessGoogle Cloud first. Provider state stays evidence-bound.
The public runtime manifest separates architecture or deployment readiness from live-runtime certification. Provider cards below are rendered from that manifest rather than hard-coded marketing copy.
Checking deployment matrix…
Provider states will appear when the public runtime manifest is available.
Four words. Four different proofs.
These terms are intentionally non-interchangeable across the website, release registry, demonstrations, and sales material.
A runtime is currently operating with fresh evidence sufficient for the claim.
A real, versioned public artifact exists and can actually be downloaded.
A defined deployment package or path has earned the required implementation evidence.
A defined capability or workflow has observable evidence showing what occurred.
Evidence, not theatre.
Public proof remains deliberately narrow. Private source, secrets, credentials, customer data, signing material, private APIs, and production controls stay outside this surface.
Missing, stale, malformed, contradictory, or unavailable evidence produces a neutral state — never an invented green badge.
See the proof first. Scope the real environment second.
The public gateway establishes what can be inspected now. Real deployments add identity, data, integrations, controls, infrastructure, security, acceptance, and operating requirements for the actual mission.
Build the system that can carry the mission.
Start with Business or Politics. Inspect public proof. Use registered release states. Then move into a controlled demonstration, pilot, or deployment without confusing readiness with certification.