Getting Started

Start at Intern. Earn Your Way Up.

A practical order of operations for implementing ATF: five principles to hold to, four rollout phases, and the week-by-week build order that keeps each element standing on the one before it.

§ 1

Five Principles

Everything else in ATF follows from these. If an implementation decision conflicts with one, the decision is wrong.

Principle	What it means in practice
Never trust, always verify	Agents authenticate and authorize every action
Autonomy is earned	Agents start constrained; privileges expand with demonstrated reliability
Assume breach	Design for containment; limit blast radius by default
Human accountability	Every agent has an accountable human owner
Observable by design	If you can't see it, you can't govern it

§ 2

Four Rollout Phases

Each phase corresponds to a maturity level. You do not skip one, and the minimum durations are minimums, not targets.

Phase 1Intern

Controlled Pilot

Validate the value hypothesis, establish a behavioral baseline

DurationMinimum 2 weeks

Scope: Single use case, limited user population
Data access: Read-only, single domain
Human involvement: Continuous oversight
Success criteria: Accuracy threshold, no unexpected behaviors

Phase 2Junior

Production Introduction

Demonstrate reliability at scale, build operational confidence

DurationMinimum 4 weeks

Scope: Production use case, broader user population
Data access: Read-only, may span domains with approval workflow
Human involvement: Approval required for all recommendations
Success criteria: >95% recommendation acceptance, zero critical incidents

Phase 3Senior

Bounded Autonomy

Deliver operational efficiency with oversight maintained

DurationMinimum 8 weeks

Scope: Defined operational domain
Data access: Read + write within scope
Human involvement: Post-action notification, exception handling
Success criteria: >99% accuracy, zero critical incidents, demonstrated ROI

Phase 4Principal

Full Autonomy

Maximize value with appropriate governance

DurationOngoing with continuous validation

Scope: Multi-domain within policy bounds
Data access: Policy-governed, dynamic scope
Human involvement: Strategic oversight, edge case escalation
Success criteria: Sustained performance, continuous compliance, business value

§ 3

Build Order

Five weeks, one element at a time. The order is not arbitrary: each element depends on what came before it, which is why identity is first and incident response is last.

Week 1

Identity Foundation

ATF-ID

Everything depends on knowing who is acting. It provides session context for every other element.

JWT-based agent authenticationSession managementBasic rate limiting

Week 2

Data Governance

ATF-DAT

Input validation has to precede behavioral monitoring. Clear test cases: does it catch SSNs?

Input schema validationPII detection pipelineOutput filtering

Week 3

Behavioral Monitoring

ATF-BEH

Needs identity for session tracking, and clean data from the governance checks.

Structured logging pipelineBasic anomaly scoringObservability integration

Week 4

Segmentation

ATF-SEG

Needs identity to know who is asking. Start simple with config, then add policy-as-code.

Role-based access policiesResource boundary enforcementPolicy evaluation logging

Week 5

Incident Response

ATF-RES

Needs every other element to generate incidents. It ties the whole thing together.

Circuit breaker implementationKill switch capabilityAlert routing

A note on sequence

Teams that start with monitoring instead of identity end up with logs they cannot attribute. Teams that start with segmentation end up with allowlists they cannot enforce. Identity first is not a preference, it is a dependency.

§ 4