Build is where you convert Jido concepts into workflows that can ship. Use this section when you already understand the runtime model and need a concrete implementation path.
What you can do from here
- Pick a starting path by role in Quickstarts by Persona.
- Choose a topology before coding in Reference Architectures.
- Validate design and operations assumptions with Architecture and Production Readiness Checklist.
Wave A map
| Guide | Use it when | Outcome |
|---|---|---|
| Quickstarts by Persona | You need a first milestone matched to your role | A bounded first deliverable in one focused session |
| Reference Architectures | You need to choose process boundaries and package layout | A blueprint with clear runtime and ownership boundaries |
Proof surface in this repository
The workbench runs a supervised agent runtime in AgentJido.Application.
This is the same execution model referenced throughout the build guides.
children = [
AgentJido.Jido,
{Jido.AgentServer,
id: AgentJido.ContentOps.OrchestratorServer,
agent: AgentJido.ContentOps.OrchestratorAgent,
jido: AgentJido.Jido,
name: AgentJido.ContentOps.OrchestratorServer}
]
Supervisor.start_link(children, strategy: :one_for_one)Expected result:
{:ok, #PID<...>}Recommended flow
- Start with your persona route and complete one small implementation proof.
- Select an architecture pattern and document why it matches your constraints.
- Run through training and checklist validation before broad rollout.
Get Building
Start with Quickstarts by Persona, then move to Reference Architectures when you need to harden topology decisions.