Skip to main content

Apply Path (Tier 2 Transformation)

Use this page when you are ready to apply the Tier 2 Transformation reference implementation to a real organization rollout.

This is the execution-first companion to:

When to Use This Path​

Choose Tier 2 apply if you need:

  • multi-team rollout over 1-6 weeks
  • CI/CD enforcement beyond basic starter checks
  • agent contracts and handoffs (typically 3-5 agents to start)
  • KPI/provenance collection and governance evidence

If you only need day-1 controls, start at Reference Implementations -> Start Here and use Quick Start or Config Packs first.

What "Apply" Means at Tier 2​

At Tier 2, you are not just copying files. You are:

  1. Installing the repo baseline (pipelines, schemas, prompts, contracts)
  2. Mapping it to your organization's current SDLC and repo structure
  3. Activating staged governance controls with owners and evidence
  4. Scaling from pilot teams to broader rollout

Prerequisites​

  • Existing Git-based SDLC with CI/CD
  • Named Phase Lead and platform owner
  • Pilot teams selected (2-3 teams recommended)
  • Baseline security scanning and incident response process
  • Agreement on initial standards scope (through PRD-STD-009)

Step 1: Clone Tier 2 Reference Implementation​

git clone https://github.com/AEEF-AI/aeef-transform.git

Then choose your language baseline:

Step 2: Map Your Starting Point​

Pick the apply mode before copying anything:

  • Greenfield rollout: Use the language implementation as your baseline repo shape
  • Brownfield rollout: Port only the required CI/policy/agent/metrics assets into existing repos

Use Adoption Paths if you still need the decision tree.

Step 3: Apply CI/CD Controls First (Pilot Teams)​

Start with the enforcement layers that create immediate signal:

  • expanded CI pipeline stages
  • quality gates / required checks
  • license + dependency controls
  • documentation enforcement hooks

Goal: every pilot repo produces consistent pass/fail evidence before adding orchestration depth.

Step 4: Apply Agent SDLC Configuration (Start Small)​

Use Agent SDLC Setup to install:

  • ai/agents/registry.*
  • ai/contracts/*
  • ai/handoffs/*
  • role prompts and schema validation in CI

Recommended starting shape:

  • developer-agent
  • qa-agent
  • security-agent
  • optionally architect-agent or product-agent

Do not start with all 11 agents unless you already operate formal cross-functional gates.

Step 5: Align to the Transformation Track Phases​

Map the technical rollout to the program plan:

Use the Transformation Implementation Hub if stakeholders need role-by-role sequencing.

Step 6: Enable Metrics and Provenance​

Apply Metrics Pipeline Setup so you can measure adoption quality, not just rollout completion.

Minimum outputs to enforce:

  • provenance records per CI run
  • KPI snapshots on a weekly cadence
  • schema validation for governance artifacts

Step 7: Prepare the Tier 3 Decision​

Before moving to Tier 3, confirm you can demonstrate:

  • stable CI quality gates across pilot and expanded teams
  • repeatable agent handoffs with evidence
  • ownership for security/compliance/platform approvals
  • auditable metrics and remediation tracking

Then use Tier 3: Production Apply Path.

Orchestration Model Note (Canonical vs Apply)​

  • The canonical orchestration model remains in /transformation/agent-sdlc-orchestration/
  • This page explains how to apply it at Tier 2
  • Tier 3 uses the same model, but a different apply sequence and control depth
Last updated on by BalrogEg