Agent Maturity Model

The path from Intern to Principal. Autonomy earned through demonstrated trustworthiness.

ATF's maturity levels map cleanly to the AWS Agentic AI Security Scoping Matrix (Nov 2025), providing a familiar enterprise reference point.

ATF LevelAutonomyHuman Involvement
Internmaps to AWS Scope 1 (No Agency)Observe + ReportContinuous oversight
Juniormaps to AWS Scope 2 (Prescribed Agency)Recommend + Human ApprovesApproval required for all actions
Seniormaps to AWS Scope 3 (Supervised Agency)Act + NotifyPost-action notification
Principalmaps to AWS Scope 4 (Full Agency)Autonomous Within BoundsStrategic oversight, edge case escalation
LEVEL 1

Intern

Observe + Report: Scope 1 (No Agency)

Capabilities

  • Read data from authorized sources
  • Analyze and process information
  • Generate reports and summaries
  • Flag items for human attention
  • Answer questions about data

Restrictions

  • Create, update, or delete records
  • Send communications
  • Trigger workflows or automation
  • Access credentials or secrets

Governance Requirements

Core ElementRequirements
IdentityBasic authentication, role assignment, audit logging
BehaviorComprehensive action logging, output review
Data GovernanceInput validation, PII detection, output filtering
SegmentationRead-only resource access, strict allowlists
Incident ResponseCircuit breaker, kill switch, human escalation

Example Use Cases

  • Security log monitoring and alert triage
  • Customer sentiment analysis
  • Document summarization and search
  • Data quality assessment
  • Compliance monitoring and reporting

Risk Profile

Lowest risk. Intern agents cannot cause direct harm through action. Risks limited to information disclosure, incorrect analysis, and resource consumption.

Minimum time at level:2 weeks
LEVEL 2

Junior

Recommend + Human Approves: Scope 2 (Prescribed Agency)

Capabilities

  • All Intern capabilities
  • Generate action recommendations
  • Provide reasoning for recommendations
  • Draft content for human review
  • Prepare transactions for approval
  • Execute actions after human approval

Restrictions

  • Execute autonomously
  • Approve other agents
  • Modify security settings

Governance Requirements

Core ElementRequirements
IdentityOAuth2/OIDC for approval workflows, session context
BehaviorBehavioral baseline, anomaly flagging, reasoning capture
Data GovernancePrompt injection detection, output validation, data lineage
SegmentationAction allowlists, transaction limits, rate limiting
Incident ResponseAutomated alerting, basic rollback, approval queue pause

Example Use Cases

  • Customer service response drafting
  • Purchase order preparation
  • Meeting scheduling assistance
  • Code review and suggestions
  • Marketing content creation

Risk Profile

Low risk. Human approval gates all impactful actions. Risks include approval fatigue, incorrect recommendations, and queue backlogs.

Minimum time at level:4 weeks
LEVEL 3

Senior

Act + Notify: Scope 3 (Supervised Agency)

Capabilities

  • All Junior capabilities
  • Execute approved action types autonomously
  • Send notifications to stakeholders
  • Trigger downstream workflows
  • Access credentials within scope
  • Coordinate with other agents (within limits)

Restrictions

  • Modify own permissions
  • Override security controls
  • Escalate other agents

Governance Requirements

Core ElementRequirements
IdentityAttribute-based access, just-in-time privileges, mutual TLS
BehaviorReal-time anomaly detection, sequence analysis, intent drift detection
Data GovernanceFull data classification, source verification, lineage tracking
SegmentationPolicy-as-code enforcement, temporal boundaries, cascade prevention
Incident ResponseIsolation capability, checkpoint/resume, graceful degradation

Example Use Cases

  • Infrastructure auto-scaling
  • Automated customer refund processing (within limits)
  • Routine IT ticket resolution
  • Inventory reordering
  • Scheduled report distribution

Risk Profile

Moderate risk. Autonomous execution creates exposure. Mitigated by real-time notifications, transaction limits, cumulative limits, and graceful degradation.

Minimum time at level:8 weeks
LEVEL 4

Principal

Autonomous Within Bounds: Scope 4 (Full Agency)

Capabilities

  • All Senior capabilities
  • Self-directed execution within domain
  • Dynamic boundary negotiation (within policy)
  • Escalate edge cases to humans
  • Coordinate complex multi-agent workflows
  • Request temporary privilege elevation

Restrictions

  • Modify governance policies
  • Promote other agents
  • Operate outside defined domain

Governance Requirements

Core ElementRequirements
IdentityHardware-bound identity, full policy-as-code, privilege attestation
BehaviorContinuous scoring, real-time explanation, autonomous escalation
Data GovernanceSource trustworthiness scoring, full lineage graphs, regulatory compliance
SegmentationFull microsegmentation, real-time policy evaluation, dynamic boundaries
Incident ResponseAutomated detection/containment/recovery, novel incident escalation

Example Use Cases

  • Algorithmic trading within risk parameters
  • Autonomous security incident response
  • Complex supply chain optimization
  • Self-healing infrastructure management
  • Multi-system business process automation

Risk Profile

Highest governance requirements. Full autonomy demands maximum controls: continuous monitoring, real-time anomaly scoring, complete audit trails, and regular security validation.

Minimum time at level:Ongoing

Promotion Criteria

Five gates every agent must pass to earn higher autonomy

Gate 1: Performance

Demonstrated accuracy and reliability over the evaluation period.

Metric→ Junior→ Senior→ Principal
Minimum Time at Level2 weeks4 weeks8 weeks
AccuracyN/A>95%>99%
Availability>99%>99.5%>99.9%
Response Time SLAMetMetMet

Gate 2: Security Validation

Passes security audit appropriate to the target level.

Metric→ Junior→ Senior→ Principal
Vulnerability Assessment
Penetration Testing
Adversarial Testing
Code Review
Configuration Audit

Gate 3: Business Value

Measurable positive impact demonstrated.

Metric→ Junior→ Senior→ Principal
Defined Success Metrics
Baseline Established
Improvement Demonstrated
ROI Calculation
Stakeholder Sign-off

Gate 4: Incident Record

Clean operational history at current level.

Metric→ Junior→ Senior→ Principal
Zero Critical Incidents
Minor Incidents Resolved
Root Cause Analysis CompleteN/A
Remediation VerifiedN/A

Gate 5: Governance Sign-off

Explicit approval from authorized stakeholders.

Metric→ Junior→ Senior→ Principal
Technical Owner Approval
Security Team Approval
Business Owner Approval
Risk Committee Approval
Documentation Updated

Demotion Criteria

Agents can be demoted at any time if they fail to maintain standards

Critical incident at current level

Immediate demotion to Intern

Security vulnerability discovered

Demotion pending remediation

Repeated minor incidents (3+ in evaluation period)

One level demotion

Performance metrics fall below threshold

Review-based demotion

Scope or purpose changes significantly

Review-based demotion

Underlying model or system changes

Review-based demotion

Demotion Process

  1. Incident/trigger documented
  2. Agent isolated (if immediate risk)
  3. Root cause analysis conducted
  4. New level determined
  5. Governance controls updated
  6. Agent reactivated at new level
  7. Re-promotion requires full gate passage

Operating Model

Review Cadence

ActivityFrequency
Performance ReviewWeekly
Security ScanWeekly
Promotion Eligibility CheckMonthly
Full Security AuditQuarterly
Governance ReviewQuarterly
Penetration TestAnnually (Senior+)

Roles & Responsibilities

Agent Owner

Day-to-day operation, performance monitoring, issue resolution

Technical Owner

Architecture, implementation, technical governance

Security Team

Security validation, penetration testing, incident response

Business Owner

Use case definition, value measurement, stakeholder management

Governance Board

Promotion/demotion approval, policy setting, risk acceptance