Toolsmith

Mandate

Python tools, proven by running them

Reads

the capability registry, and which roles are allowed to call what

Produces

A tool in the registry, and the log of the run that proved it

Rejoins the desk

Menzo declares capabilities. Declaring one does not grant it to anybody.

1. writing Menzo writes the tool in its own workspace, against the capability it will declare.
2. checking Menzo runs it in the sandbox. The network is refused, and the refusal is logged.
3. producing Menzo declares it in the registry, with the roles allowed to call it.
4. done Menzo ships the run log with the tool. A tool that has not run is not a tool.

Declared capabilities

Execute · Snapshot · Deposit · Desk

Tools it may call

python_run · report_blocked

Ask it something like

“Ship a Python tool that computes this, and prove it ran in the sandbox.”

Sealed capture on fileA sealed capture of the application exists for this mandate, taken from a named build and listed in a manifest. It is evidence on file, not a run you can watch here, the roster room used to replay it, and no longer does.