A read-only decision card
No state changes occur. Use the same ArmaraOS commands on both platforms.
Use PowerShell.
Use Terminal.
01
Use one comparison card
| Mechanism | Starts when | Author a file? | Verified note |
|---|---|---|---|
| Cron | A clock reaches a time. | No | Create works; disable did not persist. |
| Webhook | A callback registration is used. | No | Registration fails on 0.8.3. |
| Trigger | An internal event occurs. | Inline JSON | Bounded create and delete work. |
| Mission | You start a goal-directed run. | No | Course 4. |
| Workflow | You run fixed ordered steps. | JSON file | Course 4. |
02
Separate recipe from goal
A workflow is a recipe with fixed steps. A mission is a goal the agent figures out how to reach.
03
Read all five inventories
armaraos cron list
armaraos webhooks list
armaraos trigger list
armaraos mission list --agent-id <UUID>
armaraos workflow list
04
Choose from plain-language scenarios
| Scenario | Choice |
|---|---|
| Weekday brief at 9 | Cron |
| React when another agent is spawned | Trigger |
| Repeat three fixed transformations in order | Workflow |
05
Choose your next course deliberately
If you want one assistant to run a scheduled job and message you, this is a legitimate stopping point once channel credentials are ready. Course 4 is multi-agent work. Course 5 is memory and outside tools.
Check it / choose without notes
Name the start condition.
Choose a mechanism for three new scenarios and run its list command to name where state would appear.
Safety note
Every command in this sitting is read-only.
Troubleshooting the decision
| Confusion | Correction |
|---|---|
| Workflow versus mission | Fixed recipe versus goal-directed work. |
| Cron versus trigger | Time event versus internal event. |
| Webhook versus trigger | Registered URL mechanism versus internal event. |
| Bare mission list fails | Add --agent-id. |
Next / Module 3.8
Lesson ready