Use this page as a routing layer. Pick the persona path that matches your current bottleneck, finish one milestone, then move to architecture and readiness work.

How to use this page

1. Choose the persona closest to your day-to-day responsibilities.
2. Complete the first milestone without expanding scope.
3. Follow exactly one training link and one docs/checklist link before adding new requirements.

Persona quickstarts

Elixir platform engineer

• First milestone: run one supervised agent and verify deterministic state updates.
• Start: Counter Agent example
• Next training: Agent Fundamentals on the BEAM
• Ops/reference follow-up: Architecture

AI product engineer

• First milestone: ship one user-facing workflow backed by explicit actions.
• Start: Demand Tracker Agent example
• Next training: Actions and Validation
• Ops/reference follow-up: Production Readiness Checklist

Python AI engineer

• First milestone: understand where BEAM runtime boundaries improve reliability and orchestration.
• Start: BEAM for AI Builders
• Next training: LiveView + Jido Integration Patterns
• Ops/reference follow-up: Security and Governance

TypeScript fullstack engineer

• First milestone: model one multi-step workflow with clear signal boundaries.
• Start: Multi-Agent Coordination
• Next training: Signals and Routing
• Ops/reference follow-up: Guides

Platform and SRE engineer

• First milestone: define runtime health checks and incident response expectations before launch.
• Start: Observe everything
• Next training: Production Readiness: Supervision, Telemetry, and Failure Modes
• Ops/reference follow-up: Incident Playbooks

Proof check: first value in one command loop

alias AgentJido.Demos.CounterAgent
alias AgentJido.Demos.Counter.IncrementAction

agent = CounterAgent.new()
{agent, _directives} = CounterAgent.cmd(agent, {IncrementAction, %{by: 1}})
agent.state.count

Expected result:

1

When to move to architecture work

Move to Reference Architectures when any of these become true:

• You need multiple cooperating agents with distinct ownership boundaries.
• You need predictable recovery behavior for long-lived workflows.
• You need a package selection rationale that can be reviewed with platform stakeholders.

Get Building

Choose one path, complete one milestone, and document your decisions. Then continue with Reference Architectures for topology and package planning.