Feature
Trust gates
Hooks, MCP servers, tool permissions and telemetry-emitting assets are blocked until the required approval exists.
Every asset has a trust class. A trust gate combines that class with the projection policy and looks for a matching approval before a write or an exec. A target can also deny asset types outright or cap the trust class it accepts.
Approvals are recorded per root and keyed to exact content, so an approval in a workspace never satisfies a check in your home directory, and an edited file needs a fresh approval.
More features
All features →- 01
Validate the manifest and its trust gates
`wl validate` checks workloom.workspace.json against the schema, then runs the trust gates over a render plan and lists what they would block.
- 02
Deterministic render plans
See every file each provider will get, with its projection policy, ownership and write mode, before anything is written.
- 03
Sync with ownership checks
`wl sync` writes only the projections the trust gate allows, atomically, and changes or removes only files Workloom owns.