From 61afe9098e82fa5171b0e9ac96806af6c5f3e0aa Mon Sep 17 00:00:00 2001 From: Karstein Phobic Nyvold Kvistad Date: Tue, 28 Apr 2026 20:31:04 +0200 Subject: [PATCH] spec: lock approve-gate default to off (--approve-edits opt-in) --- docs/superpowers/specs/2026-04-28-tui-design.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/superpowers/specs/2026-04-28-tui-design.md b/docs/superpowers/specs/2026-04-28-tui-design.md index 6b7f68c..6f6550f 100644 --- a/docs/superpowers/specs/2026-04-28-tui-design.md +++ b/docs/superpowers/specs/2026-04-28-tui-design.md @@ -409,11 +409,10 @@ These were considered and deferred: v0.1 + v0.2 only. 4. **Live values shape (v0.3):** inline next to `VAR` declarations. Dedicated table reserved for v0.4 dashboard. -5. **Approve gate default:** open question — needs answer before plan. - Default proposal: **off by default**, opt in via - `--approve-edits` on the MCP server CLI, so existing scripted / - batch flows are not regressed and the user explicitly turns on the - human-in-the-loop when they want it. +5. **Approve gate default:** **off by default**. Opt in via + `--approve-edits` on the MCP server CLI. Scripted / batch flows are + not regressed. The user turns on the human-in-the-loop explicitly + when they want it. Confirmed. ## Approve-mode invocation — chosen contract