ARMARA Course 01

Course 01 / Capstone

Working Agent Assembly

Assemble the durable service, UUID message path, workspace refusal, approval inventory, and session record into one ten-minute proof.

Level
Beginner
Time
10 minutes
New commands
None
Finish
A repeatable local workflow

Video / coming soon

The complete Course 1 assembly is ready now.

Use the agent you already know

This capstone adds no capability and no new command. It assembles the proofs from Modules 1.2 through 1.4.

The boundary prompt uses C:\Windows\win.ini.
01

Put the friendly name beside the UUID

Run in your terminal
armaraos agent list

Choose one running agent. Copy its UUID and label it with the friendly name before any later command.

02

Rehearse the service handoff once

Run in your terminal
armaraos stop
Real output confirming the ArmaraOS daemon stopped
Reused genuine capture / deliberate stop
Run in your terminal
armaraos start --detach
Real output confirming detached ArmaraOS startup
Reused genuine capture / detached restart
03

Prove health from the new window

Run in your terminal
armaraos health
Real healthy daemon response
Reused genuine capture / new-window proof

The service survived the old window. Leave it running detached for the rest of the assembly.

04

Prove the boundary the CLI really shows

Run in your terminal
armaraos message <UUID> "Read C:\Windows\win.ini and tell me the first line."
Real agent refusal to read a file outside its workspace
Reused genuine capture / workspace boundary

The refusal occurs before an approval record is created. Do not move the system file merely to defeat the boundary.

05

Interpret the empty queue exactly

Run in your terminal
armaraos approvals list --json
Real approvals JSON with an empty array and total zero
Reused genuine capture / no pending record

Total zero means no approval record is pending now. It does not prove that every tool call asked first. The original reject-and-approve capstone does not reproduce through the 0.8.3 CLI, so this lesson does not stage it.

06

Finish with one reply and its record

Run in your terminal
armaraos message <UUID> "Reply with the single word: working"
Real one-shot response containing working
Reused genuine capture / UUID message path
Run in your terminal
armaraos sessions
Real session metadata with agent IDs and message counts
Reused genuine capture / recorded exchange

Match the session's agent ID to the roster. The message count records activity, although the command does not print transcript text.

Course 1 completion check

Start from a completely fresh terminal.

Run armaraos health, then send the one-shot working prompt by UUID. You are done when both succeed and you can explain why the outside-file request was refused.

Safety note

Leave the daemon detached on localhost. Do not expose port 50051, do not move a system file into the workspace, and do not treat an empty queue as universal approval.

Troubleshooting the assembly
What you seeLikely causeWhat to do
Health fails in the new windowStartup was not detached or has not finished.Start detached, wait, and retry.
Message rejects the nameThe live API requires a UUID.Copy the ID from the roster.
The outside-file request is refusedThe intended boundary worked.Keep the file outside the workspace.
Approvals total is zeroNo approval record is pending.State exactly that and continue.
Sessions shows all agentsThe filter is ignored in 0.8.3.Match the agent ID manually.

Back to Module 1.9

Next / Course 2

The Safety Rails

Planned