Concepts: Modules & Golden Paths
Understand the Argy model: encapsulating workflows into versioned and configurable modules.
Understanding the Argy model means understanding how to transform workflows into reusable, governed capabilities.
Module: The Base Unit
A module is the atomic unit of automation in Argy.
It is a versioned workflow with:
- inputs schema (JSON Schema)
- outputs schema (JSON Schema)
- workflow graph (nodes + edges)
Example (Module Spec v1, simplified):
{
"name": "microservice-secure-deploy",
"version": "2.1.0",
"inputsSchema": { "type": "object" },
"outputsSchema": { "type": "object" },
"workflow": { "nodes": [], "edges": [] }
}
Golden Path: Standardization Without Friction
A golden path is a module published in the catalog and recommended by the organization.
- Adoption: teams consume it through portal/CLI self-service.
- Governance: approvals and auditability remain enforced.
- Evolution: golden paths are versioned with SemVer and can be deprecated.
Status badges: stable / experimental / deprecated / draft.
Module-in-Module (composition)
Published modules appear as actions in the Studio palette, so a module can include other modules.
Note: the Argy AI action
One of the available actions is Argy AI: a module-defined AI step (custom prompts + tools) that can orchestrate sub-agents. This is how enterprises build their own governed AI agents inside modules.