Governed Command System
A governed command system for serious work.
Dominion OS™ turns intent into structured systems: intelligence, decisions, workflows, software, dashboards, evidence and controlled deployment paths inside one governed operating environment.
Product Families · Deployment Architecture
One governed foundation. Distinct deployment models.
Dominion OS for Business and Dominion OS for Politics share a governed command foundation but have distinct operating environments, infrastructure paths and distribution boundaries.
Dominion OS for Business
Desktop and enterprise infrastructure
Dominion OS for Business 1.0 and the Fractal5 SaaS Suite have a Windows x64 desktop release track and customer-controlled deployment profiles spanning four hyperscalers. Each environment is qualified against its own runtime, security, licensing and acceptance requirements.
Dominion OS for Politics · Google Cloud
Governed campaign deployment
Dominion OS for Politics follows a Google Cloud-specific deployment path for authorized campaign engagements. Campaign roles, integration scope, access, data handling and operational authority are defined per engagement. Public proof remains synthetic and separate from controlled campaign operation.
Public proof ≠ public binary. Architecture-ready ≠ certified runtime. Deployment ≠ production. A provider profile is not evidence of an installer, marketplace listing or entitlement; each production environment requires actual customer authority, controls, acceptance evidence and operating support.
System Architecture
An orchestration layer across people, AI, tools and evidence.
Dominion OS™ structures serious work above and between existing tools, people, data, agents, infrastructure and operating workflows. It does not require every adjacent system to be replaced.
Command kernel
Structures work, roles, review gates, operating state, accountability and evidence-aware execution.
Human + AI
Coordinates machine assistance and human work across defined authority, source and approval boundaries.
Application layer
Connect modules, dashboards, workflows and adjacent products around a shared governed mission.
Controlled runtime
Supports hosted, private, client-owned and provider-specific deployment paths where the actual engagement establishes them.
Operating Capabilities
Turn serious intent into inspectable work.
Prompt to system
Produce bounded concepts, page code, schemas, dashboards, reports, workflows and implementation artifacts.
Operational coordination
Organize priorities, tasks, handoffs, operating state, health and release evidence where those surfaces exist.
Intelligence orchestration
Structure research, stakeholders, signals, evidence, uncertainty, risk and source-aware analysis.
Role-based UX
Present bounded operating views for executives, analysts, developers, professional teams and reviewers.
Portable delivery
Favor explicit ownership, portable artifacts, clear handoffs and architecture choices that reduce unnecessary lock-in.
Public-safe proof
Demonstrate capability without exposing credentials, source code, customer records, private data or protected methods.
Governed Command Loop
Intent → structure → generate → review → deploy → improve.
The pattern stays consistent while authority, evidence and deployment boundaries change with the mission.
Mission
Users, stakeholders, risk, sources and desired result.
Requirements
Roles, source classes, controls and boundaries.
Artifacts
Interfaces, data models, reports and workflows.
Evidence
Claims, security, UX, accessibility and risk.
Approved environment
Demo, hosted, private or client-controlled runtime.
Operating feedback
QA, telemetry, feedback and receipts refine the system.
Deployed Configuration
Dominion OS for Politics has entered the field.
Dominion OS for Politics has moved beyond synthetic demonstration into controlled live campaign deployments at Canadian federal and provincial levels.
Public deployment records identify the electoral context while keeping candidate identities, credentials, private campaign data, protected correspondence and internal operating information outside the public surface.
Deployment records document product use. They do not imply electoral success, voter influence, candidate endorsement, electoral-authority approval or a public Dominion OS for Politics download.
Deployment Architecture
Dominion OS for Business spans desktop and hyperscalers. Dominion OS for Politics follows Google Cloud.
Deployment paths are chosen by product configuration, mission, customer infrastructure and authorized operating boundary. Architecture is distinct from proven release or runtime availability.
Dominion OS for Business
Windows desktop · Four hyperscaler profiles
Dominion OS for Business has a Windows x64 desktop release track and provider-specific options for customer-controlled environments. Each installer or cloud package remains subject to its own current release, certification and commercial evidence.
Google Cloud
Qualified customer-controlled Google Cloud deployment profile for Dominion OS for Business.
AWS
Qualified customer-controlled AWS deployment profile for Dominion OS for Business.
Azure
Qualified customer-controlled Azure deployment profile for Dominion OS for Business.
OCI
Qualified customer-controlled Oracle Cloud deployment profile for Dominion OS for Business.
Windows x64 is a desktop release track for Dominion OS for Business. Private, on-premises, sovereign and other enterprise arrangements require qualification; none is automatically represented as a publicly available or certified package.
Dominion OS for Politics
Dedicated Google Cloud campaign architecture
Dominion OS for Politics has a Google Cloud-specific path for controlled, engagement-specific campaign operation. Its public synthetic demonstration does not expose campaign data or grant public access to a production system.
Named infrastructure providers are architectural profiles, not representations of universal runtime certification, marketplace publication, public downloads or production entitlements.
Operating Contexts
One command pattern. Different missions.
These are configuration contexts, not claims that every capability is independently available as a finished standalone product.
Personal command
Research, projects, knowledge systems, dashboards, writing, planning and decision support.
Founders & creators
Product planning, demos, launch systems, research, prototypes and operating dashboards.
Professional teams
Client delivery, task routing, proposals, communications, knowledge, reporting and QA.
Enterprise
Transformation pilots, executive operations, vendor coordination, role-based workflows and controlled delivery.
Public institutions
Modernization, procurement intelligence, source-aware analysis, operating dashboards and governed workflow design.
Research institutions
Funding intelligence, observatories, evidence synthesis, multi-stakeholder coordination and research workflows.
Commercial Model
Start small enough to prove the system.
Final scope, pricing, legal terms, security posture, deployment, data boundaries, support and acceptance criteria are confirmed through governed discovery before commitment.
Individual command
Personal users, creators and bounded command workflows.
Scoped team
Small teams, pilots and early operational dashboards.
Professional delivery
Professional workflows, integrations and engagement-specific deployment.
Controlled architecture
Role separation, procurement, security review, deployment, onboarding and support at greater scale.
Use it as a service
Hosted command surface under confirmed service terms.
Deploy it
Private, customer-owned, provider-specific or sovereign path where approved.
License it
Licensed use under approved commercial and technical terms.
Extend it
Build modules, agents, dashboards, workflows and integrations around it.
Catalogue presence does not equal downloadable availability. Historical package pricing is not treated as the authoritative current public pricebook. Enterprise, licensing, deployment, third-party distribution, API and custom terms remain engagement-specific unless a current public offer expressly states otherwise.
Governance & Security
Capability does not outrun authority or evidence.
Dominion OS™ is designed for serious civilian, commercial, public-sector, research, infrastructure, security and other mission environments. Some deployments may be dual-use.
Intended use, authorized end users, jurisdiction, deployment, remote access, data, security requirements and applicable obligations are assessed for the actual engagement.
Identities, tools, services and operating roles receive only the authority required for their bounded function.
Control mapping and assurance support are not represented as formal certification without current formal evidence.
Encryption, key management, network, residency and data controls are confirmed for the actual environment rather than assumed universally.
High-impact change should include staged delivery, health checks, recovery planning, release evidence and rollback paths.
Public proof does not expose private source, customer data, credentials, secrets, protected records or internal production controls.
A dual-use posture does not itself establish export classification or authorize a particular destination, end user, transfer, security use or deployment.
Sector Configurations
Configuration patterns, not universal availability claims.
Domain configurations are scoped against actual professional responsibility, data, regulatory requirements, technical readiness and engagement authority.
Aerospace & space
Airspace analysis, permitting, risk modeling, policy and funding intelligence.
Energy & infrastructure
Energy systems, resilience, renewables, resource analysis and policy intelligence.
Public sector
Legislative intelligence, procurement, program analysis, executive briefing and modernization workflows.
Health information
Population, workforce, access, evidence and policy analysis within appropriate professional boundaries.
Trade, labour & economy
Indicators, labour signals, trade intelligence, investment and scenario analysis.
Regulatory & risk
Regulatory change, gap analysis, controlled evidence workflows and issue analysis.
Fractal5 SaaS Suite
Thirteen catalogue modules around the command layer.
Catalogue presence describes product architecture. Exact runtime, licensing, integrations and deployment state remain subject to their own current evidence.
GrantConnect
Funding intelligence, eligibility and preparation workflows.
TeamConnect
Roles, routing, team telemetry and internal coordination.
PolicyConnect
Policy, compliance-signal, legal-risk and bill-impact workflows.
ChannelConnect
Outreach and supported communications workflow coordination.
Cloud Engine
Deployment planning, health, observability and rollback posture.
Vault Systems
Structured records, intelligence archives and controlled evidence.
Command Core
Mission logic, operating state, telemetry and orchestration.
Advocate Engine
Stakeholder and public-message workflow tooling within applicable boundaries.
Install Grid
Onboarding, setup, deployment steps and implementation handoff.
OpsSignal
Mission telemetry, integrity checks and operating status.
EcoStack
Environmental, energy, climate and resource-intelligence patterns.
StoryThread
Narrative, media workflow and source-aware public content systems.
DataHarbor
Auditable data architecture, source catalogs and governed repositories.
A listed module is not automatically a paid API, public download, third-party distribution listing, activated runtime, certified production system or universally available integration.
Dominion OS™ 1.0
Start with one governed build.
Bring a workflow, dashboard, module, data problem, public-safe proof surface or enterprise pilot. Fractal5 will scope the authority, controls, evidence, acceptance criteria and deployment path around the actual mission.
Dominion OS™ 1.0 is available for inquiry and qualified deployment consideration. Public demonstrations are illustrative proof surfaces and do not grant software, production, redistribution, export, security, defence or other regulated-use rights.