CIRMS Conception

A centralized hub-and-spoke model built around HERCULES, ATLAS and small reusable automation units called ATOMS.

Core model

Centralized communication.
Distributed resources.

CIRMS uses a centralized hub-and-spoke communication model that enables structured two-way communication between HERCULES and the systems and resources it manages. This simplifies the flow of information and operational instructions while supporting consistent interaction patterns across different technologies and environments.

Send → Receive Check & see

Monitoring and information gathering across connected systems.

Send → Do Check & fix

Authorized operational execution through defined tasks.

Standardized two-way communication simplifies administration, centralizes coordination and allows additional managed resources to be incorporated without redesigning the communication model.

01 / SINGLE HERCULES One managed environment
Databases Applications Infrastructure Services
HERCULES Operational execution
GL3 GL4
GL3 Automation &
Data Acquisition
GL4 AI Data
Readiness
Conceptual architecture · HERCULES includes GL3 and GL4
CIRMS component hierarchy

A vocabulary designed for clarity.

HERCULES

The operational backbone of CIRMS. Each HERCULES machine manages a designated environment or technology domain and performs GL3 Intelligent Automation, monitoring, health checks, resource management and data acquisition.

Through GL4, HERCULES transforms collected operational data into structured, curated and AI-ready knowledge.

ATLAS

The coordination and oversight layer. ATLAS consolidates operational information across HERCULES environments and provides an organization-wide perspective for centralized monitoring, governance and coordination. Planned GL5 capabilities are intended to extend this layer with AI-assisted analysis and conversational intelligence while maintaining human oversight.

CLIENTS

The resources and systems managed through HERCULES — including databases, servers, applications, services, infrastructure and other connected operational assets.

THE MOTHER SYSTEM CONCEPT

One organization. One continuous operational intelligence loop.

Project TOHOL® was conceived around a fundamental principle: complex operational environments should be managed through a unified, modular and intelligent architecture. By combining centralized oversight, distributed execution, trusted operational data and AI Data Readiness, CIRMS establishes a foundation for system autonomy, operational intelligence and responsible AI integration.

HERCULES machines operate close to the environments they manage, while ATLAS provides coordination, governance and an organization-wide perspective across the organization.

Conceptual illustration from the original CIRMS visual identity. GL3 automation and data acquisition and GL4 AI Data Readiness form the operational foundation. The intelligent services and advanced AI-assisted capabilities shown in the illustration represent the broader conception and the planned GL5 direction.

CIRMS Mother System concept showing HERCULES, ATLAS, operational data, AI Data Readiness and organizational feedback loops across sectors.
Concept diagram · the broader CIRMS Mother System vision
GL4 · Knowledge preparation

A traceable path from data to knowledge.

GL4 extends the operational foundation created by GL3 by transforming acquired operational data into governed, structured and AI-ready knowledge through traceable preparation stages such as metadata refresh, raw ingestion, curation, document generation, chunk generation, vector embedding and semantic validation.

The preparation work belongs to HERCULES. AI models and conversational intelligence are part of the planned GL5 evolution.

Process overview, not a live execution or readiness result.

  1. 01

    Metadata refresh

    Understand the source.

  2. 02

    Raw ingestion

    Acquire operational data.

  3. 03

    Curation

    Prepare structured data.

  4. 04

    Document generation

    Create AI documents.

  5. 05

    Chunk generation

    Divide knowledge into chunks.

  6. 06

    Vector embedding

    Prepare vector representations.

  7. 07

    Semantic validation

    Validate semantic use.

Reusable building blocks

Small execution units.
Larger workflows.

At the foundation of CIRMS automation are ATOMS — small, focused and reusable units of execution, historically referred to as “Atomized Bots.” Each ATOM represents a specific operational task or process.

ATOMS can be combined into Modules and orchestrated into larger workflows, allowing CIRMS to build complex automation while maintaining granular control, reuse and adaptability.

01 ATOMS Focused execution bots
02 MODULES Groups of ATOMS
03 WORKFLOWS Orchestrated tasks

Modular & Reusable — ATOMS can be reused and recombined for different operational requirements. Precision Control — each ATOM is purpose-built for a focused task, supporting clear responsibility and precise execution. Adaptive Execution — workflows can be extended or reconfigured as systems, technologies and organizational requirements evolve.

Next steps

See how the model scales.

Explore a single HERCULES environment, HERCULES–ATLAS coordination and the planned multi-ATLAS architecture.

Explore Architecture