Work Records
The structured evidence produced by one completed request.
A Work Record is the real, structured trace of one request — what commands ran, which files changed, what was verified, and why it stopped if it stopped early.
It builds up as actions run: commands with their exit codes and output, file changes, and check results (type check, build, tests, lint). A section with nothing to show stays empty — PawOS never fills it with a made-up summary.
Note
Software installs and PATH repairs appear in the Work Record timeline, showing what ran and in what order.
How it works
What you see
- Workspaces, tasks, plans, permission questions, Work Records, usage meters and connection status.
- You use these through normal requests — there is no separate configuration console.
What PawOS does
- A workspace scopes file and command work; a task groups one request; a plan proposes work; an action performs one concrete step; a Work Record captures what happened.
- Work Records are built from the real results of each action, not written up afterwards.
Permissions
- Naming something a workspace, plan or task never skips a permission question.
- PawOS decides what to do, but every change to your machine goes through a dedicated, checked action.
- Plan limits and permission questions are separate protections and can both apply.
Records
- Each claim in a Work Record points to the command, file, check, screenshot or result behind it.
- A Work Record shows partial success, skipped checks, rejected plans and failures just as clearly as successes.
Good to know
- Work Records always show the timeline of what ran; many action types add detailed evidence on top.