Reuse two running agents
The production verification used the existing assistant and code-helper by UUID, so no extra agents or stored directories were created.
Give two agents narrow jobs
The first agent supplies one sentence. The second reshapes supplied text. They are separate workers with no coordination layer.
Become the message bus
armaraos message <RESEARCHER_UUID> "<QUESTION>"
armaraos message <WRITER_UUID> "Turn this into three bullets: <PASTED_RESULT>"
Name the friction
You were the message bus.
You moved the result, supplied the context, and held the only knowledge that the first answer fed the second request.
Define orchestration after feeling its absence
Orchestration is one agent handing work to another without you in the middle. A trace records the delegation episode, participants, and returned result.
Prove ordinary calls make no trace
armaraos orchestration listarmaraos orchestration list --limit 20 --json
These calls were independent, not delegation. Empty is the expected proof.
Preview the course shape
Next come delegation unlock, missions, trace reading, cost, workflow authoring, and emergency containment.
Check it / explain the empty result
Name what did not happen.
Run orchestration list and explain why two manually connected messages created no delegation trace.
This sitting uses ordinary messages and no new authority. Still read copied text before placing it in another agent's prompt.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
| Name is rejected | Message requires UUID. | Copy it from agent list. |
| Second agent lacks context | The first output was omitted. | Paste the complete reviewed text. |
| Trace list is empty | Calls were independent. | That is expected. |
| Limit is rejected | It is outside 1 through 200. | Choose a valid value. |