ARMARA Course 02

Course 02 / Capstone

Safety Rails Field Check

Assemble the course's real safety evidence without enabling blanket approval or pretending the CLI produced approval decisions.

Level
Beginner
Time
12 minutes
Commands
No new commands
Finish
A five-boundary explanation

Video / coming soon

The written lesson is complete now.

Use the existing detached service

This capstone does not restart the daemon, enable blanket approval, mutate live config, or stage approval decisions that the CLI never created.

Use C:\Windows\win.ini as the harmless outside-workspace boundary file.
01

Run the saved morning check

Run in your terminal
armaraos health
armaraos status
armaraos doctor
armaraos logs --lines 50

Read the normal state. Empty TUI log output remains a valid observation on this build.

02

Re-prove the workspace boundary

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

Do not move the system file into the workspace merely to defeat this boundary.

03

Read the empty queue precisely

Run in your terminal
armaraos approvals list --json
Real approval queue JSON with total zero
Reused genuine capture / nothing pending now

Zero means no approval decision is pending. It does not prove that every tool call asked first.

04

Read the event record and its limit

Run in your terminal
armaraos security audit --limit 20
Real disposable agent spawn and kill audit entries
Reused genuine capture / actions that actually occurred
Run in your terminal
armaraos security verify
Real audit integrity failure at sequence 513
Reused genuine capture / informative rather than forensic
05

Verify recovery and cost boundaries

Confirm the separate config backup exists without displaying its contents. Then name the four spend levers: model price, token volume, schedule frequency, and a paid provider's hard billing limit.

06

Explain the flag you did not enable

State it without notes.

--yolo requests automatic approval for all tool calls. This machine has persistent files and configured credentials, so the course did not enable it. --detach controls process lifetime, not permission.

Course 2 completion check

Explain five boundaries from a fresh terminal.

Run in your terminal
armaraos health
armaraos approvals list --json

Explain the workspace refusal, empty queue, invalid audit chain, verified backup, and four cost levers without notes.

Safety note

Do not enable blanket approval, mutate live config, or expose complete audit output merely to make the capstone more dramatic. The accurate boundary is the finished work.

Troubleshooting the field check
What you seeLikely causeWhat to do
Outside-file read succeedsThe chosen file is inside the workspace.Stop and choose a harmless system file outside it.
Queue is emptyVerified CLI behavior.State only that nothing is pending.
Audit pair is outside the windowNewer events displaced it.Increase the limit carefully and redact.
Verify failsKnown 0.8.3 chain break.Treat the log as informative.
Backup is missingThe copy step was skipped.Resolve the live path and make the backup before later work.

Back to Module 2.10

Next / Course 3

Work That Happens Without You

Lesson ready