Everything as Code — Framework (Blueprint)¶

BLUEPRINT DOCUMENT. This is the portable framework definition. It is target-agnostic and intended for export to a corporate EaC Adoption Instance workspace. All examples in this document use the synthetic NovaTrek Adventures workspace as the exemplar. See the README for the Blueprint vs Instance distinction.

1. Definition¶

Everything as Code (EaC) is the practice of expressing every artifact required to design, build, run, govern, and evolve a software system as a declarative, version-controlled, machine-readable, human-readable text file living in source control alongside the application.

The defining properties of an EaC artifact:

If an artifact lacks any of these, it is not "as code" — it is a document, a screenshot, or a database record.

2. The Industry Name¶

The umbrella term is Everything as Code (EaC). It generalizes a family of related "X as Code" disciplines:

Adjacent and synonymous terms used in industry:

• Software Defined Everything (SDE / SDx) — used in networking and infrastructure circles to mean the same thing as EaC
• Declarative-first — used in Kubernetes / cloud-native communities
• GitOps — when git is the single source of truth and reconciliation is automated (Flux, Argo CD)
• Spec-Driven Development (SDD) — emphasizing that specifications precede implementation (AWS Kiro, OpenSpec, Spec-Kit)
• Single Source of Truth (SSoT) architecture — the goal that EaC enables

3. The Transformation Has a Name Too¶

Adopting EaC across an organization or practice is referred to as:

The transformation this blueprint describes is best named:

AI-Native Continuous Architecture via Everything as Code

…which reads as: a continuous architecture practice (the "what"), enabled by everything as code (the "how"), targeted at AI-native workflows (the "why"). This blueprint is the pattern; the corporate instance is the realization.

4. The Pillars¶

Every EaC implementation is organized around pillars — one per discipline. The full adoption guide for each pillar (artifact types, adoption steps, CI integration, exit criteria) lives in TRANSFORMATION-PLAN.md. This section is the reference catalog: purpose, format, and AI fit for all 35 pillars.

Pillar A — Infrastructure as Code (IaC)¶

Pillar B — Pipeline as Code (PaC)¶

Pillar C — Actors as Code¶

Pillar D — Applications as Code¶

Pillar E — Architecture Artifacts as Code¶

Pillar F — Capabilities as Code¶

Pillar G — Decisions as Code (ADRs)¶

Pillar H — Architecture Backlog as Code¶

Pillar I — Tests as Code¶

Pillar J — Policy as Code¶

Pillar K — AI Instructions as Code (AIaC)¶

See AI-INSTRUCTIONS-AS-CODE.md for the deep dive.

Pillar L — Wireframes as Code (UIaC)¶

Pillar M — Documentation as Code (Docs as Code)¶

Pillar N — Presentations as Code (PrC)¶

See Presentations as Code for the deep dive.

Pillar O — Governance as Code¶

Pillar P — Operational Runbooks as Code¶

Pillar Q — Data Models as Code¶

Pillar R — Database Migrations as Code¶

Pillar S — Data Contracts as Code¶

Pillar T — Event Schemas as Code¶

Pillar U — Security as Code¶

Pillar V — Compliance as Code¶

Pillar W — Secrets Management as Code¶

Pillar X — SBOM as Code¶

Pillar Y — Observability as Code¶

Pillar Z — SLO / SLI as Code¶

Pillar AA — Feature Flags as Code¶

Pillar AB — Release Strategies as Code¶

Pillar AC — Environment Definitions as Code¶

Pillar AD — Service Mesh Configuration as Code¶

Pillar AE — Team Topology as Code¶

Pillar AF — Onboarding as Code¶

Pillar AG — Developer Experience as Code¶

Pillar AH — Architecture Principles as Code¶

Pillar AI — Ubiquitous Language as Code¶

Pillar AJ — Coding Standards as Code¶

Pillar AK — Patterns and Anti-patterns as Code¶

Pillar AL — Risk Register as Code¶

Pillar AM — Service Catalog as Code¶

5. Maturity Model — From Documents to AI-Native EaC¶

A practical maturity model for an architecture practice's EaC adoption:

The maturity levels describe organizational milestones, not per-pillar completion gates. An organization reaches Level N when the majority of relevant pillars in that level's category are producing validated, CI-enforced artifacts. Individual pillars can sit at different levels; the overall practice maturity is the mode or median across the active pillars.

Pillar groups by maturity level:

To assess where a real practice sits today, use the assessment template in CURRENT-STATE-ASSESSMENT.md.

6. The Codify-Validate-Generate (CVG) Loop¶

Every EaC pillar implements the same operational loop:

┌────────────┐     ┌────────────┐     ┌────────────┐     ┌────────────┐
│  CODIFY    │ ──► │  VALIDATE  │ ──► │  GENERATE  │ ──► │  PUBLISH   │
│ (author)   │     │   (CI)     │     │   (CI)     │     │ (deploy)   │
└────────────┘     └────────────┘     └────────────┘     └────────────┘
      ▲                                                          │
      └──────────────── feedback / refinement ──────────────────┘

The CVG loop is the operational core of EaC. Every pillar must implement it end-to-end before that pillar can be considered "as code."

7. Anti-Patterns That Prevent True EaC¶

8. Key References¶

This section will be populated by the deep research response. See DEEP-RESEARCH-PROMPT-EAC-MATURITY-MODEL.md.

Initial seed references:

• ThoughtWorks Technology Radar — multiple "X as Code" entries
• HashiCorp's "Infrastructure as Code" methodology
• The Open Group ArchiMate specification
• Architecture as Code (AaC) project — https://github.com/DevOps-MBSE/AaC
• Structurizr DSL — https://structurizr.com/dsl
• Likec4 — https://likec4.dev/
• IcePanel — https://icepanel.io/
• Diátaxis documentation framework — https://diataxis.fr/
• MADR ADR template — https://adr.github.io/madr/
• OpenSpec — https://github.com/Fission-AI/OpenSpec
• AWS Kiro (spec-driven development) — https://kiro.dev/
• The arc42 template — https://arc42.org/
• C4 Model — https://c4model.com/
• Continuous Architecture in Practice (Erder, Pureur, Woods) — Addison-Wesley, 2021
• Standardized taxonomy of AI instructions and OpenSpec governance model (workspace deep research) — standardized.taxonomy.of.ai.instructions.etc.deep.research.response.md