Work Records

Each request builds one Work Record. As each action runs, its real result is added: commands with their exit codes and output, files with what changed, and checks with their pass/fail result — never a summary written after the fact.

Every Work Record includes the full timeline of what ran and in what order, so you can trace any result back to the action behind it.

How it works

What you see

• An overview of how PawOS is organised and how its records work, for engineers and administrators.

What PawOS does

• Specialised engines handle coding, browsing, infrastructure, communication and the companion.
• Every change goes through a checked action, and every action is recorded.

Permissions

• All actions follow the same permission and plan rules described in Security.

Records

• Work Records and billing records are the source of truth for what happened.

Good to know

• See the Changelog for what has changed between versions.