Modules: the three kinds

What a module is

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 every one is linked from the docs overview.

Foundational Modules

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.

Asset Registry

One live record for every asset, read by every other module.

Knowledge Library

Operational know-how, structured and searchable, kept after people leave.

Integration Hub

Every system you already run, connected once.

Historian

An immutable, timestamped record of everything that happened.

Authority Matrix

Who is allowed to do what, checked at every action.

Approval Queue

Sign-offs routed to the right person and recorded when they land.

Governance

Requirements turned into rules the platform checks.

Security

Protection running under every module, session, and data movement.

Trust Registry

Roadmap, not available today. The record of what was verified, by whom, and when.

Supplier Registry

One record for every supplier your operation depends on.

Form Builder

Build the capture forms the work actually needs.

Screen Configurator

Configure what each role sees, without a release.

Data Model Engine

A working model of the operation for what-if questions.

Workflow Modules

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.

Scheduling Engine

A live, constraint-aware schedule for every job and machine.

Model Router

Every AI call routed to the model built for it.

Workflow Engine

Processes that run, with every step and handoff in flight.

Retrieval Engine

Search and exploration across everything the platform holds.

SPC Engine

Statistical process control against live process data.

OEE Engine

Availability, performance, and quality, measured continuously.

Investigation Engine

Root cause traced through the record, not argued.

Q&A Engine

Plain-language questions answered from the Knowledge Library.

Demand Planner

Demand taken in and planned inside the platform.

Notification Center

Configurable alerts that reach the right person.

Facility Organizer

Sites, areas, and lines in one shared hierarchy.

ProMatch

Opportunities matched to suppliers able to deliver them.

Agentic Modules

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 them replace judgment that needs a human. They escalate those calls and act on the rest.

Production Planning (Planner)

Replans the schedule against what the floor actually did.

Procurement (Buyer)

Runs procurement off live asset and supplier records.

Quality (Auditor)

Watches the records an audit will ask for.

Continuous Improvement (Coach)

Finds the next improvement in the operating record.

Operations (Manager)

Holds the operational picture and raises what needs a decision.

Anomaly Detection (Analyst)

Flags behaviour that does not fit, early.

They are covered in depth on the Agents page.

Choosing modules

You do not buy every module on day one. Which module does what sorts the same modules by the job you are trying to do, and What the Singularity is covers how an engagement grows into more of them.

The compliance backbone is the exception. Security, Governance, Authority Matrix, Approval Queue, and Historian carry the compliance backbone, and no deployment runs without all of them active. That is covered in Security and governance.