speculationlisted

Speculation-authorization mode toggle (Superscalar §4). Invoke as /speculation off|auto|on|always|status to set who authorizes a speculative lane — starting the likely branch of an unresolved gate before it resolves. Marker .agent/speculation.json, default off. The modes graduate along downstream sensitivity: `auto` asks per speculation with the four-element trade-off, `on` pre-authorizes low-sensitivity lanes (read/analyze/summarize/sandboxed-test inside the worktree) while high-sensitivity ones still ask, `always` pre-authorizes every lane that stays inside the §3 irreversibility barrier. One constraint governs all modes and cannot be read past: the mode changes WHO authorizes, never WHAT a lane may touch — no mode reaches a write, deploy, send, or delete. Andon transparency (visual signal, /stop-spec pull-cord, misprediction logging) is unconditional in every mode including always: pre-authorization removes the question, not the visibility. Orthogonal to /superscalar (how many lanes) and /subscaler (what e
SoliEstre/EstreGenesis · ★ 7 · AI & Automation · score 78

Install: claude install-skill SoliEstre/EstreGenesis

# `/speculation` — who authorizes a speculative lane `/superscalar` decides **how many** lanes. `/subscaler` decides **what each lane runs on**. This skill decides **who signs off on a speculative one** — a lane that starts the likely branch of a gate that has not resolved yet (an approval, a review verdict, a test outcome, an A/B choice), so the result is ready the instant the gate clears. Speculation is the one dispatch class that spends tokens on work that may be thrown away. That is why it has its own toggle instead of riding the dispatch-aggressiveness one: fanning out more lanes and *betting* on an unresolved branch fail differently and want to be tuned separately. Normative spec: `Superscalar.md §4`. Read it before changing this skill — in particular the two-stage announce and the Andon three elements, which this toggle does not modify. ## 0. Toggle contract State = **one marker file**: `.agent/speculation.json` → `{"mode": "off"|"auto"|"on"|"always", "since": "<date>", "note": "<why>"}`. **Absent ⇒ `off`.** Read it at dispatch time; never mirror the mode into other settings surfaces — duplicated per-lane bindings have shipped state-convergence bugs. - `/speculation off` — write `off` (or delete the marker) - `/speculation auto` — write `auto` - `/speculation on` — write `on` - `/speculation always` — write `always` - `/speculation status` — read it back and report the mode **plus where it would apply to the work in front of you**. A toggle without a read-back is