H-Reason
Start with the question that is actually current.
Call /h-reason when a concern deserves a deliberate, source-supported reasoning pass. Haft retrieves the relevant versioned FPF material, applies the smallest useful method, and keeps alternatives live when the evidence is insufficient.
A reversible exchange can stay in conversation. It becomes a durable project record only when handoff, replay, authority, automation, or later verification needs an addressable result.
$ /h-reason "How should we handle cross-service transaction failures?"
Other #Commands
/h-frameClarify the real problem and acceptance basis./h-diagnoseTest rival causes of an observed failure./h-exploreGenerate genuinely distinct approaches./h-compareCompare existing options under explicit parity./h-verifyMeasure whether a recorded claim still holds./h-statusRead current project memory, drift, and readiness./h-specManage typed specification carriers and gates./h-noteSave an explicitly requested non-binding fact.
Manual
Binding actions fail closed without explicit operator invocation. The MCP kernel validates required fields and authority boundaries server-side, so a persuasive prompt is not an approval receipt.
/h-decideRecord a human-approved DecisionRecord.Manual/h-commissionGrant bounded authority for execution work.Manual