New to the Academy? Begin with a workflow. Each path opens a guided practice with sources, an artifact, review criteria and a way to return to your draft.
01 / Build a reliable workflow
Start here if you are unsure
Give your AI workflow a clear boundary
You have a recurring task and want to decide what AI may do.
Bring
One recurring task, its owner and an example input. No coding needed.
Make
A workflow brief with permitted actions, a review gate and a stop condition.
Your first move Name one task and the person who owns its result.
See the artifact and review criteriaAI_DEPARTMENT_PACKET.json
Workflow fit. The packet can recommend not automating and bounds one owner, input, output, exception, and reversible test.
Authority and risk. Human decisions, data limits, prohibited actions, stop conditions, and revocation are explicit.
Architecture simplicity. The smallest viable topology is justified and producer/verifier separation is preserved.
Evidence and evaluation. Completion evidence, representative tests, adversarial cases, uncertainty, and runtime pinning are inspectable.
Portability and recovery. Semantic components, native projections, adapter gaps, rollback, and revalidation triggers are named truthfully.
Criteria guide your review. Completing a form does not establish mastery.
A practice you can return to
The draft is only the beginning.
Keep the moments that change your mind. Mission Studio holds the work in this page; download your practice file to keep it, then import it to continue.
Describe the situation and preserve your own first attempt.
02
Make something you can question
Read the sources, build an artifact and attach critique to that exact draft.
03
Revise. Then change the context.
Explain what changed and try your method on a different situation.
The Academy, wherever you work
Your agent can learn the method, too.
Install the free toolkit to bring mission coaching, department design and evaluation exercises into your own agent environment. The same learning contracts travel with you.
Codex and Claude Code have verified Git installation paths. Other supported tools use the downloadable pack and host-specific setup.
Your practice belongs with your work.
A wider world of learning
Many branches. Shared roots.
Explore the Knowledge Tree: evidence, your first agent, teams, memory, science, art and humane leadership. Follow one question into an example, a source and a practice you can keep.
For developers: public learning contracts and current limits
Local practice · no account. Browser drafts live in page memory until you download them. Learner declarations and critique authorship are self-reported. No theatrical claims of consciousness, automatic assessment or agent authority accompany these exercises.
Use public, synthetic or redacted material. A human decides every external action. The public tools do not run a hosted tutor, issue credentials or connect a community.