Concepts: Modules, Patterns, Golden Paths

Understanding the Argy model means understanding how to transform operational complexity into reusable capabilities.

Module: The Base Unit

A module is the atomic unit of automation in Argy. Unlike a simple Terraform script or an isolated CI pipeline, an Argy module encapsulates everything necessary for a workflow's lifecycle:

• Configuration Schema: A clear, typed interface for parameters.
• Templates (IaC/CI): Provisioning and delivery logic.
• Policies/Guardrails: Integrated compliance and security controls (Policy-as-Code).
• Runbooks & Docs: Operational knowledge required for the "Run".
• Observability: Standard monitoring baselines and alerts.

Pattern: Product-Oriented Orchestration

A pattern is a special type of module oriented toward a "product." It describes a complete (E2E) path for a specific workload type. For example, a "Microservice" pattern will orchestrate several sub-modules (Compute, Database, CI/CD, DNS, SSL) to provide an end-to-end experience.

Golden Path: Standardization Without Friction

A golden path is the concrete application of a pattern recommended and supported by the company's platform team.

• Adoption: Developers choose the Golden Path because it is the easiest path (self-service).
• Governance: The company favors the Golden Path because it is secure and compliant by design.
• Evolution: Golden Paths are versioned. Migrating from Golden Path v1 to v2 becomes a standardized and industrialized process.

Argy's ultimate goal is to transform your module catalog into a true Internal Developer Platform (IDP) where each "Golden Path" reduces teams' cognitive load while increasing overall security.