Skip to content
EcoSec WorX

Agentic AI Octopus Factory™

Bring us the problem. We'll design the intelligence.

EcoSec WorX helps organizations turn business problems into secure, practical Agentic AI systems. Business first, architecture first, security by design, on any cloud, model or agent framework.

Any cloud · any model · any agent framework

  • AWS
  • Microsoft Azure
  • Google Cloud
Agentic Intelligence Fabric reference architectureRequests from customer consoles, the EcoSec reference console and API consumers enter through the Integration Fabric and Theo into the Agent Fabric, which runs the Orchestrator Agent, Capability Agents, Context Resolver and Site Context Agent. The Decision Intelligence Layer governs every conclusion before action. The Operational Context Model, Operational Knowledge Fabric and Action Playbooks supply context, grounding and procedure, while the Operational Event Stream, external systems and telemetry analytics supply signals. The Trust Ledger runs alongside every layer, and the Runtime Adapter Layer, persistence interfaces and Deployment Adapter Layer isolate AI runtimes, data stores and clouds.TRUST LEDGERCustomer consoleReference consoleAPI · MCP · webhooksIntegration Fabricauthenticate · resolve tenant · apply policyTheoagentic orchestration & interaction layerAGENT FABRICOrchestratorAgentCapabilityAgentsContextResolverSite ContextAgentDecision Intelligence Layerevidence · confidence · risk · approvalOperationalContext ModelOperationalKnowledge FabricActionPlaybooksOperationalEvent StreamExternalsystemsTelemetryanalyticsRuntimeAdapter Layerany model · frameworkData storespersistence interfacesDeployment Adapterany cloud
Agentic Intelligence Fabric (AIF) reference architecture. The Trust Ledger records every layer; providers sit behind adapters.
What we do
Turn business problems into secure Agentic AI
How it starts
$5K · 50 days · fixed scope
Day 50
Stop, Build or Operate. Your call.
Built on
Reusable blocks, not a blank page

The $5K / 50-Day Agentic AI Challenge

$5,000. 50 Days. One Business Challenge.

Design + Demonstrate + Roadmap

A decision-ready Agentic AI design for one well-defined problem, secured and scoped under a written SOW. Plus one customized Agentic AI training session for your team.

Day 50: STOP → BUILD → OPERATE

Your business

  • People
  • Data
  • Systems
  • SOPs
  • Knowledge
  • Workflows

Agentic AI Octopus Factory™

  • Software & Architecture Building Blocks
  • The Octopus Body of Knowledge
  • AI-Assisted Engineering

Customer-specific

Agentic Intelligence for your organization

$5K · 50 days · fixed scope

Day 50: you decide

  • STOPTake the Blueprint
  • BUILDTurn the Design Into Reality
  • OPERATEMake Agentic AI an Ongoing Capability
Your business context of people, data, systems, SOPs, knowledge and workflows flows into the Agentic AI Octopus Factory, which combines software and architecture building blocks, the Octopus body of knowledge and AI-assisted engineering, to produce customer-specific Agentic Intelligence. On Day 50 you choose to stop, build or operate.

Included with every $5K / 50-Day Challenge

Bonus: Custom Agentic AI Team Briefing

Every $5K / 50-Day Challenge includes one tailored Agentic AI training session based on what we learn about your organization, your architecture, and the recommendations developed during the engagement.

How the briefing works →

Choose the emphasis that is most useful for your team:

  • Executive Agentic AI briefing
  • Technical architecture briefing
  • Agentic AI cybersecurity briefing
  • Employee AI enablement briefing
  • Leadership Crawl → Walk → Run briefing

ISACA San Diego · Oct 23, 2026

When AI Gets the Keys: Securing the Agentic Enterprise

Download Tom Caldwell's ISACA presentation on what changes when AI stops recommending and starts acting — and how the Octopus framework keeps intelligence governed, action bounded and humans accountable.

  • The five questions every agent must answer
  • Where permission actually happens — the authorization boundary
  • Graduated autonomy and tamper-evident audit trails

The executive problem

Everyone Wants AI. Few Organizations Know What to Build First.

Most organizations have run an experiment. Far fewer have a production system that integrates with real applications, APIs, data and telemetry — with the security, governance and evidence an enterprise needs. The gap between the two is architecture, not enthusiasm.

  • Where should we start?
  • Which use cases are actually worth building?
  • Can agents safely touch our operational systems?
  • Who owns what gets built?
ExperimentationProduction Agentic AI
  • A demo that answers questionsA system that acts on your operations
  • Prompts and documentsLive signals, context and governed tools
  • One clever modelSupervised agents with bounded authority
  • "It seemed to work"Evidence of what it observed, decided and did

Our differentiator

We Don't Start With a Blank Screen.

Your business logic is custom. The plumbing doesn't have to be. EcoSec WorX brings existing architectural patterns and reusable Agentic AI building blocks, so engagement time goes into what makes your system unique — not into reinventing orchestration, decision governance and the Trust Ledger.

Agents & Orchestration

  • Theo orchestration
  • Orchestrator & Capability Agents
  • Multi-agent orchestration
  • Workflow engines
  • Memory & context

Knowledge & Context

  • Retrieval-Augmented Generation
  • Knowledge bases
  • Knowledge graphs
  • Operational Context Model (OCM)
  • Operational Knowledge Fabric

Integration & Signals

  • Tool integrations
  • APIs
  • MCP integrations
  • Event-driven architecture
  • Telemetry ingestion
  • Operational signals

Security & Governance

  • Identity & authorization
  • Guardrails
  • Human-in-the-loop controls
  • Policy enforcement
  • Security controls

Evidence & Observability

  • Audit trails
  • Evidence collection
  • Agent activity logging
  • Observability

Platform & Operations

  • Cloud infrastructure patterns
  • AIOps components
  • Operational dashboards

Custom layer

Your application and business logic — built specifically for your organization, on top of proven components.

Engagement model

Crawl. Walk. Run.

Risk is controlled in stages. Every engagement begins with an Agentic AI Architecture Sprint that ends in an explicit Go / No-Go decision — before any major investment. Our job is not to convince you to build AI. Sometimes the right answer is "don't build it yet."

Take the $5K / 50-Day Challenge

Learn throughout the journey · Challenge → Build → Operate

  1. CHALLENGE

    Learn enough to decide

    One customized training episode

    Included with every $5K / 50-Day Challenge.

  2. BUILD

    Learn enough to deploy

    Optional three-part customized training series

    May be included in larger Build engagements.

  3. OPERATE

    Learn continuously

    Ongoing training, workshops, reviews and enablement

    Can be part of an Operate engagement.

  1. Stage 1

    Crawl

    Discover & Architect

    A focused sprint to decide whether the opportunity is worth pursuing — before major investment.

    Offer

    Agentic AI Architecture Sprint

    Deliverables

    • Prioritized use cases
    • Reference & agent architecture
    • Operational Context Model (OCM)
    • Knowledge & integration strategy
    • Cloud recommendation
    Go / No-Go Decision
  2. Stage 2

    Walk

    Build the MVP

    If the Sprint produces a GO, we build a working system that demonstrates measurable operational value before scaling.

    Outcome

    Working Agentic AI MVP

    Typical components

    • Theo orchestration
    • Orchestrator & Capability Agents
    • Integration Fabric connectors
    • Operational Knowledge Fabric
    • Operational Event Stream & OCM
    Validated Value
  3. Stage 3

    Run

    Production Agentic Operations

    Validated systems move into production with the architecture, hardening and support that enterprise operations require.

    Outcome

    Production deployment & operations

    Typical components

    • Production architecture
    • High availability & scalability
    • Multi-agent & multi-tenant systems
    • Cybersecurity hardening
    • Enterprise integrations
    Operate & Improve

Context before intelligence

AI Without Context Is of Limited Value.

A model can reason. An operational system also needs to understand the environment it operates in. Our Operational Context Model (OCM) gives agents machine-readable context: what something is, where it is, what it connects to, what state it's in, who owns it, which policies apply and which actions are appropriate.

An LLM gives an agent intelligence.

An OCM gives it operational understanding.

  • Assets
  • Devices
  • People
  • Customers
  • Locations
  • Systems
  • Relationships
  • Events
  • Policies
  • Roles
  • Procedures
  • Historical conditions
  • Operational states
  • Security constraints
Operational Context Model (OCM) exampleA single asset, GW-07, connected to its type, location, network, current state, owner, governing policy and permitted actions.is aEdge gatewaylocated atSite North · Rack 4connected toVLAN 30 · 42 devicesstateDegraded since 13:48owned byField Ops · on-callgoverned byChange-window policypermittedRestart w/ approvalGW-07asset

Telemetry & operational signals

Give Your AI Agents Eyes and Ears.

Agentic AI shouldn't operate on documents and prompts alone. We connect agents to the signals that describe what is actually happening — telemetry, events, alerts, logs, sensors, infrastructure metrics, security events and network data — so they can understand a situation and determine what action should occur.

SignalsWhat is happening
ContextWhat it means here
KnowledgeWhat we have learned
ReasoningWhat should happen
ToolsWhat can be done
Agentic OperationsUnderstand, decide, act — with evidence

Knowledge Fabric

Turn Tribal Knowledge Into Operational Intelligence.

Capture what your best people know before it walks out the door. Much of an organization's most valuable operating knowledge lives in engineers, technicians, operators and subject matter experts — not in documentation. The Operational Knowledge Fabric captures, curates and grounds that expertise — manuals, procedures and incident history — so agents and future employees can use it.

Where it lives

People

  • Engineers
  • Technicians
  • Operators
  • Executives
  • Support teams
  • Subject matter experts
Capture

Sources & methods

  • Expert interviews
  • Conversational capture
  • SOPs & procedures
  • Incident history
  • Troubleshooting notes
  • Documents
  • Tickets
  • Logs
Structure

Operational Knowledge Fabric

  • Curated corpus
  • Tenant-scoped retrieval
  • Action Playbooks
  • OCM context
Use

Who benefits

  • AI agents
  • New employees
  • Operators on shift
  • Incident responders

Cybersecurity, built in

When AI Gets the Keys, Security Changes.

Once agents can act, authority becomes attack surface. Security is a foundational design principle in every EcoSec WorX architecture — never an add-on after the system is built.

Authority agents may hold

  • Query databases
  • Call APIs
  • Modify systems
  • Create tickets
  • Send communications
  • Trigger workflows
  • Change configurations
  • Interact with OT
  • Initiate automated responses

What we design for

  • Least privilege
  • Identity & authorization
  • Tool permissions
  • Tenant isolation
  • Secrets protection
  • Prompt-injection defenses
  • Knowledge poisoning
  • Excessive agency
  • Compromised tools
  • Privilege escalation
  • Human approval gates
  • Blast-radius reduction
  • Policy enforcement
  • Tamper-evident activity records
  • Cybersecurity monitoring

Auditability & evidence

Autonomous Doesn't Mean Unaccountable.

Every agent action should leave evidence. Our architectures record execution, decision context, tool activity, telemetry history and change history — designed to support governance, evidence collection and compliance programs such as SOC 2, NIST and ISO.

Questions you should be able to answer

  • What happened?
  • What did the agent observe?
  • What information did it use?
  • What decision did it make?
  • Why did it make that decision?
  • Which tool did it call?
  • Who authorized the action?
  • What changed?
  • Can the sequence be reconstructed?

Architecture can support compliance efforts; it does not by itself make an organization compliant with any framework.

evidence · run_7f3asha256 chained · append-only
observed
4 signals · link_down x3, temp_high x1
context
ocm://site-north/gw-07 · state=degraded
knowledge
sop-118 rev 4 · incident-2291 (similar)
decision
restart gw-07 uplink during window
rationale
matches sop-118 §3; blast radius 1 site
approval
required · granted by on-call (field-ops)
tool_call
netctl.restart_uplink(gw-07) → 200
change
uplink restored 14:06:40Z · ticket OPS-5521
Illustrative agent execution record. Every step can be reconstructed.
The Octopus FrameworkA central core of shared context, governance and knowledge with eight connected capabilities: Agents, Data, Telemetry, Cybersecurity, Knowledge Fabric, OCM, Workflows & Automation, Human Expertise.AgentsDataTelemetryCybersecurityKnowledge FabricOCMWorkflows & AutomationHuman ExpertiseSHARED COREContextGovernanceKnowledge

Thought leadership

The Octopus Framework

Intelligent enterprises need interconnected capabilities, not isolated AI applications. Like an octopus, specialized arms act independently while staying connected through shared context, governance, knowledge and operational intelligence.

Developed by Thomas Caldwell and the Octopus book series, the framework is the intellectual architecture behind how EcoSec WorX scopes, designs and delivers every engagement.

Explore the Octopus Framework

Cloud agnostic

Your Cloud. Not Ours.

We design Agentic AI architectures for AWS, Microsoft Azure and Google Cloud — and hybrid environments when that is the right call. The platform follows your constraints, not a partnership quota.

  • AWS
  • Microsoft Azure
  • Google Cloud

Architecture is designed around

  • Your existing environment
  • Security requirements
  • Existing contracts
  • Data architecture
  • Workload requirements
  • Operational systems
  • Hybrid where appropriate

Intellectual property

Your Solution. Your IP.

We don't hold your AI strategy hostage. Your custom business logic and work product can belong to you.

Custom work product

Can belong to you

The custom business logic and work product we build specifically for your engagement can be owned by your organization.

Pre-existing EcoSec WorX components

Licensed for your solution

Where we use our reusable frameworks, libraries or building blocks to accelerate delivery, those components can be licensed to you for use within your solution.

Detailed ownership and licensing terms are defined in the applicable consulting agreement or statement of work.

We don't hand over code and disappear.

After delivery we stay available for support, maintenance, enhancements and advisory — including fractional CTO services.

  • Support
  • Maintenance
  • Enhancements
  • Architecture advisory
  • Fractional CTO services
  • AI lifecycle management
  • Knowledge-base maintenance
  • Agent optimization
  • Security reviews

Optional · Managed Agentic AI Monitoring

  • Agent failures
  • Workflow failures
  • Abnormal actions
  • Latency
  • Model usage
  • Security events
  • Tool failures
  • Integrations
  • Telemetry anomalies
  • Operational health

People

Senior Leadership. Specialist Talent When Needed.

You work directly with our executive leadership. When an engagement calls for it, we assemble specialists from a deliberate expert network — rather than staffing your project from a bench.

Thomas Caldwell

CEO/CTOAgentic AI Architect

As CEO/CTO, Thomas leads the company and its technical direction. He is a technology executive, entrepreneur and cybersecurity innovator with experience at Microsoft, Cisco Systems and technology startups, works across distributed systems, networking, AI and autonomous operational systems, and is the author of the Octopus book series.

  • Technology leadership
  • Agentic AI architecture
  • Cybersecurity
  • Distributed systems
  • Octopus Framework

Greg Ricchiuti

Chief Strategy Officer (CSO)Agentic AI Strategy Architect

As Chief Strategy Officer, Greg leads corporate, business and customer strategy — shaping how Agentic AI initiatives are scoped, commercialized and tied to measurable business outcomes, and how operating models adapt to run them.

  • Technology leadership
  • Corporate strategy
  • Customer outcomes
  • Commercialization
  • Operating-model strategy
  • Agentic AI strategy

Extended expert network

  • Data scientists
  • AI engineers
  • Cloud architects
  • Cybersecurity professionals
  • Software developers
  • Frontend engineers
  • Backend engineers
  • DevOps engineers
  • Data engineers
  • Domain specialists

Next step

Have an Agentic AI Idea?

Let's determine whether it is worth building. Every engagement starts with an Architecture Sprint that ends in an explicit Go / No-Go recommendation — and sometimes the right answer is "don't build it yet."