Level 1: Certified ArcFlow Workflow Developer

Title: Certified ArcFlow Workflow Developer

Prerequisite: None. Start here if you write agent workflows in Python or TypeScript.

What certified means at this level

You can build and run linear multi-step workflows with real or stub providers, configure agents with instructions and tools, read execution traces for basic lifecycle events, use arcflow init and arcflow run from the CLI, and diagnose WorkflowConfigurationError and WorkflowExecutionError without external help.

Competencies covered

CompetencyDemonstration
Linear workflowsThree or more ordered steps with handoff
Agent configurationInstructions, role, optional tools
ProvidersStub for tests; switch to one real LLM provider
TracesIdentify WorkflowStarted, StepCompleted, WorkflowCompleted
CLIinit project and run a script locally
ErrorsFix config errors vs execution failures

Continue with

Practical project

Build a three-step research, analyze, summarize pipeline:

StepAgent roleOutput expectation
1 ResearchGather facts on a topic you chooseStructured notes
2 AnalyzeIdentify themes and risksAnalysis text
3 SummarizeExecutive summaryFinal string returned from run()

Requirements

RequirementDetail
Real LLM providerAt least one step uses a non-stub provider via env configuration
ToolAt least one agent registers a simple tool (calculator, datetime, or domain stub)
Trace verificationScript asserts required lifecycle event kinds after run()
CLIProject creatable via arcflow init; workflow runnable via CLI
READMELists env vars and verify command

Suggested starting points

ResourceLink
Blog pipeline sampleFirst linear workflow walkthrough
First linear docfirst-linear-workflow

Extend the blog pipeline pattern with an analyze step and real provider on one agent.

Verification commands

bash
# SDK run
python your_project/main.py

# Expected: exit 0, non-empty output, step_count >= 3

# CLI trace (replace RUN_ID)
cargo run -p arcflow-cli -- trace RUN_ID --format json

Pass criteria checklist:

CheckPass
status == completedyes
step_count >= 3yes
Tool invoked at least oncevisible in trace or logs
Real provider stepnon-stub model id in config
Trace kinds include lifecycle trioyes
Configuration error recoveryyou can explain a fixed config mistake

Error handling competency

Reproduce and fix:

ErrorTriggerFix pattern
WorkflowConfigurationErrorEmpty agent nameCorrect agent definition
WorkflowExecutionErrorInvalid tool args or provider failureValidate inputs; check provider env

Document one intentional misconfiguration and your fix in the project README.

Self-assessment checklist

Before claiming Level 1:

QuestionAnswer must be yes
Can you explain linear vs graph mode at a high level?
Can you read a trace export without prompt text?
Can you run Track A in Python or TypeScript cold?
Does your project README let a peer reproduce runs?

Next level

Proceed to Level 2: Systems Engineer after graph, RAG, and server patterns in Tracks B through E.