FAQ
Note
Design document: draft. Authorization, approvals, evidence, and early client/integration code exist in source; platform, host, and milestone validation remain incomplete.
What is Shiin?
Shiin is an agent-agnostic authorization layer for AI agent actions. It sits between agents and the files, commands, networks, and services they act on.
Is Shiin ready to use?
Shiin is experimental; source builds and published alpha binaries are intended for evaluation. The engine, CLI, audit log, and experimental tasks exist; live-host validation and milestone exit criteria remain open. See installation and the roadmap.
What makes Shiin different?
Four things:
- Task-intent binding. Actions are checked against the constraints of the task the developer confirmed.
- An open, agent-neutral contract. The action request, decision, and approval protocol are versioned specifications with schemas and test vectors.
- Analyzable policy. Policies compile to Cedar, a formally verified authorization language.
- Explicit enforcement levels. Every integration is labeled cooperative, mediated, or OS-enforced.
Does Shiin use a language model to decide?
No. No decision ever depends on the output of a language model.
Does Shiin collect telemetry?
No. Shiin is local-first and collects no telemetry.
What can Shiin do that my host’s built-in controls cannot?
Shiin applies one policy across every agent and binds decisions to the task the developer gave. Host controls are configured separately per agent and do not know the task.
What can Shiin not do?
Shiin is not a sandbox, a network firewall, a prompt-injection detector, or a DLP. It complements those tools; it does not replace them.