Skip to content

brainstorming: vendor the grill and route the two tracks - #1

Merged
SSFSKIM merged 1 commit into
mainfrom
worktree-grill-to-brainstorming-router
Jul 4, 2026
Merged

brainstorming: vendor the grill and route the two tracks#1
SSFSKIM merged 1 commit into
mainfrom
worktree-grill-to-brainstorming-router

Conversation

@SSFSKIM

@SSFSKIM SSFSKIM commented Jul 4, 2026

Copy link
Copy Markdown
Owner

What

  • The grill moves to brainstorming. Matt Pocock's grilling text (verbatim, attributed) and the three domain-modeling interview moves now live in brainstorming's clarification step — one vendor point serving both tracks. Previously the verbatim copy lived only in execplan (unreachable at task start) while issue-register carried its own adaptation.
  • Brainstorming gains a thin track router. After the grill, the human partner explicitly chooses: controlled (default — approaches → design → spec → writing-plans) or autonomous (hand off to execplan). Guard: never route silently; a delegation phrase ("just handle it") is not a track choice.
  • execplan slims to authoring/execution/exit; Step 1 points at brainstorming's grill and keeps the invariant "never author an ExecPlan from an un-grilled conversation."
  • Vendor-point drift reverted: the duplicate skills/execplan/references/PLANS.md (commit 1562e6e, no recorded rationale) is deleted, restoring the single shared copy the design spec mandates.
  • Living spec updated (docs/doperpowers/specs/2026-07-03-execplan-track-design.md): Decision Log entry reversing the no-cross-pointer decision (with the rejected fold-into-execspec alternative), Surprises entry on the drift, verification greps, revision note.

Why

The autonomous track's standalone entry never fired mechanically: brainstorming auto-triggers at every task start and captured every entry; execplan's one real use (ida-solution T13) was deliberately invoked, and docs/doperpowers/execplans/ never appeared in this repo. Routing belongs where triggering actually happens.

Verification

  • All four design-spec verification greps pass (single vendor point restored, grill text present in brainstorming, router present, no stray files in skills/execplan/).
  • Three single-shot compliance probes against the edited skill: (A) "just handle it, I'm in meetings" → grill starts, no routing, guard clause cited; (B) "Let's make a react todo list" → one question at a time with recommended answer, no code; (C) explicit autonomous choice after a completed grill → clean hand-off to execplan, controlled-only steps skipped. Single-shot probes, not full multi-session pressure evals — fork-local sanity bar.

Fork-internal change (not for upstream). Authored by Claude Code (Fable 5) with human direction of the design.

🤖 Generated with Claude Code

https://claude.ai/code/session_01H1EUCf5ir9kcTE99XkuYW5

The grill (Matt Pocock's grilling, verbatim) and domain-modeling's three
interview moves move from execplan into brainstorming's clarification
step — one vendor point serving both tracks. Brainstorming gains a thin
track router after the grill: the autonomous track (execplan) is entered
only on the human partner's explicit choice; delegation phrases like
'just handle it' are not a track choice.

execplan slims to authoring/execution/exit and points at brainstorming
for Step 1. The duplicate PLANS.md copy from 1562e6e is reverted,
restoring the single shared vendor point the design spec mandates.
Design spec updated: Decision Log entry (reverses no-cross-pointer),
Surprises entry (vendor-point drift), verification greps, revision note.

Verified: all four spec verification greps pass; three single-shot
compliance probes pass (grill starts one-question-at-a-time; 'just
handle it' does not route; explicit choice hands off to execplan).
@SSFSKIM
SSFSKIM marked this pull request as ready for review July 4, 2026 20:03
@SSFSKIM
SSFSKIM merged commit 33aeb30 into main Jul 4, 2026
@SSFSKIM
SSFSKIM deleted the worktree-grill-to-brainstorming-router branch July 4, 2026 20:04
SSFSKIM added a commit that referenced this pull request Jul 10, 2026
Two-tier trust (review #1, human design call): developer feedback — the
server-resolved role snapshot in TRIAGE_TRUSTED_ROLES (default admin), or
a stripped .env #TRIAGE_DEV_CODE body prefix — is read as instruction
(R1/R4 waived: dev ideas can be born ready-for-agent, labeled
source:dev-feedback); user feedback keeps the conservative gate, residual
risk explicitly accepted in the Decision Log. The dev code is stripped
before the body reaches the prompt or ticket so it never leaks into a
public issue.

The rest of the review, all fixed:
- #2 R2 requires a REAL file citation (path-shaped after :line strip;
  unknown:12 no longer counts)
- #3 R3 scans risk SYMBOLS (assertStudentAccess, supabaseAdmin, RLS,
  generate-plan layout fns, past_exam_problems, SUPABASE_SERVICE_ROLE_KEY)
  in addition to paths
- #4 claim issues a lease token; writeback is lease-conditional (late
  writeback after reclaim throws instead of clobbering); reclaim window
  validated at config load; second idempotency check right before
  registerTicket
- #5 findExisting fails closed on gh search errors
- #6 ticket body temp files: mkdtemp dir, mode 0600, removed in finally
- #7 TRIAGE_ENABLED checked before config parsing
- #8 spec drift fixed (feedback-dispatch.ts references, two-kill-switches)

p86 DDL note gains triage_lease UUID. New src/trust.ts. 91 tests green,
tsc clean.
SSFSKIM added a commit that referenced this pull request Jul 31, 2026
…icity audit #1)

Subtraction pass per the essentialist scaffolding philosophy: drop the
enforcement machinery built for rationalization-prone models (Iron Law
block, rationalization table, red-flags list, verification checklist,
letter-vs-spirit clause, worked examples, flowchart) and keep the
epistemic core: watch-it-fail verification, test-first rationale,
judgment-framed recovery when code precedes tests, writing-good-tests
pointer, when-stuck signals. 320 -> 77 lines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant