gryph-policy-authoring

# Authoring Gryph Policies Gryph mediates what an AI coding agent reads, writes, and runs. A policy is an ordered list of rules. Each rule matches an action and returns a decision. This skill helps a human draft those rules, with an agent's help, then hands the human a command to install them. You draft in a workspace directory. You never install. You never write into Gryph's config directory. The human reviews the draft and runs the install command you give at the end. This keeps the human in control of what becomes active policy. ## The two hard rules 1. Draft only in a workspace directory you create, for example `./gryph-policy/`. Never write a policy file into Gryph's config directory or its `policies/` directory. Gryph blocks an agent write there by design, and a direct write bypasses the human review. 2. Never install. Do not run `gryph policy install`, `gryph policy edit`, or `gryph policy init <name>` (a bare name writes into `policies/`). These change live policy. Your job ends at a validated draft plus an install command for the human. ## The gryph binary is the source of truth The installed `gryph` binary is authoritative and version-matched. Read the schema and the existing policy from it. Do not author fields from memory. - `gryph policy schema` prints the exact rule fields, match criteria, and decision set. This is the single source of truth for the schema. Check it before you write a field. - `gryph policy builtin` prints Gryph's own built-...