Hooks

Hooks run at documented lifecycle boundaries and return bounded decisions to the same policy engine used by native operations.

Events

Allowed decisions

A hook may add context, replace documented input fields, or block an operation. A hook cannot grant a capability that is absent, unhealthy, outside the workspace jail, or forbidden by operator policy.

Operate

/hooks inspects active hook sources and status. Hook output should be deterministic, bounded, non-interactive, and free of secret material.

Failure contract

A required policy hook that cannot produce a valid decision must fail closed. Post-tool failures are retained as evidence and must not erase the underlying tool result.