Docs
Every capability in the Singularity is a module. There are 31 today, and they come in three kinds.
A module is one capability of the Singularity. Foundational Modules hold the facts, Workflow Modules turn those facts into work, and Agentic Modules run that work on their own.
A deployment turns on the modules that fit the operation, so no two look identical. Every module has its own reference page in the module library, and all 31 are linked from the docs overview.
Each one is the single place a given fact lives: assets, permissions, integrations, history. Every other module reads the same values with the same provenance.
These act on the facts the Foundational Modules hold, with an operator’s judgment built in. They run the work: scheduling, investigating a defect, catching quality drift before it costs a run, answering a question against the operation’s own knowledge.
An Agent is a Function plus a Persona. The Function is the operational area: scheduling, quality, procurement. The Persona is the real industrial job title: Planner, Auditor, Buyer.
The same Agent logic runs in every deployment, and the operator knowledge sets how each one behaves in a given industry. One Agent, Operations, sits above the rest and coordinates them, directing who handles what and in what order. None of the six replace judgment that needs a human. They escalate those calls and act on the rest.
The six are covered in depth on the Agents page.
You do not buy all 31 on day one. Which module does what sorts the same 31 by the job you are trying to do, and What the Singularity is covers how an engagement grows into more of them.
Five modules are the exception. Security, Governance, Authority Matrix, Approval Queue, and Historian carry the compliance backbone, and no deployment runs without all five active. That is covered in Security and governance.
We use cookies to understand how the site is used and to connect form submissions to earlier visits. No analytics or marketing cookies are set until you choose. Privacy Policy