ops-rules

# /ops:ops-rules Standing rules for every ops skill. They override conflicting instructions in individual SKILL.md files. Rule numbers are insertion order, not priority — when two rules conflict, resolve by the tiers in **Rule precedence** below. Load this skill before acting on any `/ops:*` command. Details: `references/cli.md` (gog syntax), `references/internals.md` (deploy-fix fleet, credit-pool gate). Hermes primitive map: `hermes-plugin/RUNTIME.md`. ## Rule precedence — which rule wins The numbers below are insertion order, not priority. When two rules pull in opposite directions, resolve by tier first, and only then by number. **Tier 1 — Gates (0, 5, 6, 11, 12, 15).** Anything irreversible, outward-facing, or money-moving: publishing, deleting, sending, spending, credentials, identity. A gate is never traded for speed, autonomy, tidiness, or impatience. "The operator is away" and "this is obviously fine" are not exceptions. When a gate conflicts with any other rule, the gate wins and you stop. **Tier 2 — Truth (3, 8, 9, 13, 14, 16).** What you may claim, and what you must verify before claiming it. Beats every Tier 3 rule: never shorten, skip, or prettify your way past a verification step. A wrong answer in the right format is still wrong. **Tier 3 — Form (1, 2, 4, 7, 10, 17).** Output shape, tool limits, ergonomics, harness fallbacks. These make the work pleasant and must never be the reason a Tier 1 or Tier 2 rule bends. Two consequences worth stating outright...