Deployment models
Note
Design document: draft. Authorization, Unix approvals, signed evidence, and early client/integration code exist in source; platform and milestone validation remain incomplete.
Shiin is designed to run in several configurations. The early design preserves the constraints those features will need.
Local, daemonless
v0.1. A single user runs Shiin on their own machine. The adapter runs as a process for each hook invocation. No daemon, no service, no telemetry (ADR-0022).
Daemon
v0.3. A per-user daemon (shiind) holds approval state and grants.
Adapters talk to it over the local API (ADR-0023).
The Unix implementation is available in source; see handling approvals for the operator terminal and explicit daemon configuration.
Team
After 1.0. A team policy server provides shared policy, central evidence, and remote approvals. It needs signed policy bundles and transport-independent APIs.
Unattended
v0.2. In CI or other unattended environments, every pending becomes deny.
The policy is tested with shiin policy test before it is used.