st-reasoning-chain-precedes-record-decision
ST reasoning chain MUST precede first record_decision, not follow as remediation
Pattern: record_decision with bypass_reasoning_chain=True satisfies the per-call gate, but completion-gate-validator.py separately tracks session-level reasoning-chain telemetry. SUBSTANTIAL-scope sessions (3+ file mutations + memory-touched=True) BLOCK at session-close even when bypass flag was used per-call, because no add_thought/add_hypothesis/generate_hypotheses/add_evidence/first_principles_decomposition/decision_matrix fired in the session.
Action: open ST session + run first_principles_decomposition + add_thought chain BEFORE the first record_decision call. This is a one-round-trip optimization (vs being blocked at stop-gate and remediating retroactively). Higher quality outcomes too — the chain informs the recorded rationale rather than being decorative-after-the-fact.
Trigger criteria for proactive ST session creation:
- ≥3 file mutations expected
- Memory file edit (MEMORY.md, feedback_*, session-learnings, error-playbook, vault) imminent
- Architecture / vendor / strategy decision being made
- Any setup-curator-governed file edit
Source: completion-gate-validator.py blocked twice in session 2026-05-10; second time after bypass_reasoning_chain=True was used; root cause = session-level reasoning-chain check, not per-call bypass.