Skip to main content

Apply Path (Tier 3 Production)

Use this page when you need to apply the Tier 3 Production reference implementation to a regulated, enterprise, or high-assurance environment.

This is the execution-first companion to:

When to Use This Path​

Choose Tier 3 apply if you need:

  • production monitoring and alerting for AI/runtime controls
  • configuration drift detection
  • incident response automation
  • sovereign/jurisdiction overlays
  • full 11-agent governance with environment promotion rules

If you do not yet have reliable Tier 2 controls, start with Tier 2: Transformation Apply Path.

What "Apply" Means at Tier 3​

At Tier 3, apply means operationalizing governance in production environments, not only defining it in docs/CI:

  1. Activate monitoring and health checks
  2. Enforce runtime and deployment controls
  3. Apply jurisdiction overlays and evidence requirements
  4. Expand agent governance to production-safe orchestration boundaries

Prerequisites​

  • Tier 2 controls operating consistently (or equivalent)
  • Platform team ownership for monitoring/alerts/deployments
  • Security + compliance approval workflow defined
  • Incident response process and on-call routing available
  • Environment promotion model (dev/staging/prod) already in place

Step 1: Clone Tier 3 Reference Implementation​

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

Then select the closest language baseline:

Step 2: Establish the Production Baseline​

Before overlays or full agent expansion, confirm the base deployment can produce:

  • CI/CD quality gate evidence
  • deployment manifests / release artifacts
  • traceable approvals for production changes

Use Tier 3: Production for the capability map.

Step 3: Deploy Monitoring and Health Signals​

Apply Monitoring Setup first.

Goal:

  • dashboards and alerts are active before high-autonomy workflows expand
  • trust metrics and operational failures are observable
  • governance failures create actionable signals, not manual surprises

Step 4: Enable Drift Detection and Incident Automation​

Apply:

Do this before scaling role autonomy so policy/config regressions are caught automatically.

Step 5: Apply Sovereign / Regulatory Overlays​

Use Sovereign Compliance Overlays to select the required jurisdiction pack(s):

  • KSA
  • UAE
  • Egypt
  • EU

Treat overlays as additive controls over the base AEEF model, not replacements.

Step 6: Expand to the Full 11-Agent Model​

Use the same canonical orchestration model as Tier 2:

Apply production-specific constraints while expanding:

  • environment permissions per agent
  • mandatory human deployment approval
  • trust-level gating and escalation routing
  • audit evidence completeness for agent handoffs

Step 7: Validate Production Readiness Claims​

Before claiming Tier 3 readiness, verify:

  • monitoring, alerting, and rollback pathways are tested
  • overlays are selected and evidence artifacts retained
  • incident triage/rollback procedures are executable
  • 11-agent registry/contracts/handoffs are versioned and auditable

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 3 Production
  • The CLI may still be the execution wrapper, but production controls and approvals differ from the small-team baseline

Same CLI Core, Different Operating Mode​

If you run orchestration via the CLI, keep one CLI core (aeef-cli) and apply a production role-pack / contracts aligned to Tier 3.

See:

Last updated on by BalrogEg