Start here

The orchestrator is the developer.

A developer defines an outcome, chooses and equips AI agents and tools to make it, verifies the result and answers for it. You do not need to type the code yourself.

Two layers

One foundation, plus your field.

Every developer learns the same universal foundation. Each field then adds its own expertise. A field pathway builds on the foundation; it does not teach it again.

Universal foundation

The skills every developer shares, in any field:

  • Outcomes and evidence: the goal, the limits and the proof of success.
  • Instructions and context: what the agent needs to know and do.
  • Agent stacks: harnesses, models, skills and tools, with only the access the job needs.
  • Verification: check the result, its risks and its cost before you rely on it.

Field expertise

What one field adds on top of the foundation:

  • The field's own artifacts and tools, such as a robot simulation or a sequencing pipeline.
  • Its standards, and the qualified review its work needs.
  • Its safety limits. Practice here never replaces a license or a professional approval.

Outcome first

Your journey, step by step.

Each step says what you can use today and what is still being prepared.

  1. Choose an outcome

    Start from what you want to make and how you will know it works, not from a tool.

    Available now. Starter katas and working examples are ready.

  2. Build the universal foundation

    Learn to give agents clear instructions and context, choose a stack, and check what comes back.

    Partly available. Starter lessons and katas are ready. The full foundation kata collection is being prepared.

  3. Add field expertise

    Apply the same foundation in one field, with its own tools, standards and qualified review.

    Partly available. Robotics and biotechnology tracks are ready. Other fields have starter practice only.

  4. Practice, stretch and apply

    Repeat a kata, meet an unfamiliar Randori challenge, then take the technique into a real mission.

    Partly available. Randori challenges and the mission playbook are ready. Belts are a practice checklist and are not issued yet.

  5. Grow on the training path

    Move from Developer to Master Developer, then coach others as a Sensei.

    Available now. The Developer and Master Developer paths and the Sensei guides are ready today.

Existing training

Everything you used before is still here.

The lessons, tracks and paths keep their addresses. Progress you marked stays in this browser; this page does not change it.

The current program rules, assessments and certificates still apply as written. How they fit this wider definition of a developer is being reviewed. Until that review is approved, this page does not change them.

Terminology guide

The words we use.

We use each word in one way across the site. The same meanings are in the glossary.

Developer
Anyone who develops an outcome: you define it, orchestrate AI agents and tools to make it, and verify the result. Developer is also the first rank on the training path.
Orchestrator
The person who chooses, equips and directs AI agents toward an outcome and answers for the result. The orchestrator is the developer.
Universal foundation
The skills every developer shares in any field: outcomes and evidence, instructions and context, agent stacks, and verification.
Field expertise
The tools, standards and qualified review that one field adds on top of the universal foundation, such as robotics or biotechnology.
Agent stack
The harness, models, instructions, skills and tools you choose for a piece of work.
Kata
A repeatable technique you practice, from a clear outcome to the evidence that it worked.
Belt
A practice stage for showing capability in one field: practice, adapt, demonstrate. Belts are not issued yet, and a belt is never a professional license.
Randori
Practice without a recipe: you get a goal, constraints and checks, then choose your own stack and approach.
Mission
Real work where you apply a practiced technique, with agreed permissions, checks and review.
Master Developer
The second rank. A Master Developer owns a whole product end to end and runs it in the real world.
Sensei
The third rank. A Sensei coaches other developers, reviews their work and hosts live builds.