sticky

# Sticky Set per-project auto-routing mode. Three states: | State | Default? | Behavior | |---|---|---| | `auto` | yes (when `.sticky` absent) | **Intent-detection routing** — messages containing chain-starter verbs (`audit`, `debug`, `fix`, `brainstorm`, `scope`, `deploy`, `review`, …) auto-route. Pure conversation passes through. | | `on` | — | **Full sticky** — every task-shaped message routes, even without explicit intent verbs | | `off` | — | **All auto-routing disabled** — only explicit `/hyperflow:*` slash commands trigger chains | Intent-detection is the floor — the user gets it without any opt-in (the orchestrator scans every user message for chain-starter verbs and routes when matched). Sticky `on` raises the ceiling; sticky `off` lowers the floor. Full doctrine: [DOCTRINE.md](../hyperflow/DOCTRINE.md) Layer 1 auto-routing clause (intent verb taxonomy + routing contract + bypass patterns). ## Subcommands | Subcommand | Description | |---|---| | `on` | Set state: on — full sticky routing on every task-shaped message | | `auto` | Set state: auto — intent-verb routing only (the default) | | `off` | Set state: off — disable ALL auto-routing including intent detection | | `status` | Show current state (on / auto / off / when toggled) | Default subcommand when none provided: `status`. ## State persistence Sticky state is stored at `.hyperflow/.sticky` (project-scoped, gitignored). File format: ``` state: on since: 2026-05-17T14:30:00Z trigger: user-mention # o...