Security // concrete controls

Keep authority visible.

Shimpz protects consequential work with explicit boundaries rather than an absolute security promise.

01

Scoped Integration access

Assistants declare the provider capabilities and scopes they need. Team binds encrypted provider tokens to the exact Team, Assistant, Integration, provider, scopes, and generation.

02

Human authority at the boundary

A reviewed Power can pause for one Team-owned human request. Approval, denial, expiry, and authentication remain owned by the platform boundary, not by Assistant code.

03

Isolated execution

Teams isolate workloads, files, bindings, credentials, networks, and lifecycle. The shared Brain gains none of an Assistant’s execution authority.

04

Audit without secret disclosure

Security events record bounded principal metadata and outcomes. Tokens, keys, prompts, messages, file contents, and provider credentials are excluded.