decision-logging-rigor

Decision Logging Rigor

Hard Gate

NO PROCEEDING WITHOUT CAPTURING:

1. Decision (one sentence)
2. Alternatives considered (≥2, not just the chosen option)
3. Deciders (names, not team names)
4. Context (constraints, deadlines, stakeholder asks)
5. Expected outcome
6. Written to strategy-graph via decision-logger

Process

digraph decision {
    trigger [label="Trigger: 'решили X' / 'we decided'", shape=box];
    fields [label="All 5 fields captured?", shape=diamond];
    demand [label="PROBE: ask for missing field\none at a time", shape=box];
    write [label="Invoke decision-logger\n→ write to strategy-graph", shape=box];
    pass [label="PASS → proceed", shape=box, style=filled, fillcolor="#ccffcc"];

    trigger -> fields;
    fields -> demand [label="missing"];
    demand -> fields;
    fields -> write [label="present"];
    write -> pass;
}

Checklist

• Decision in one sentence: ___
• Alternatives considered (≥2, not just runner-up — what else was on the table?): ___
• Deciders (names): ___
• Context (what constraint / deadline / stakeholder ask drove this): ___
• Expected outcome: ___
• Risks (optional but recommended): ___
• → invoke decision-logger → strategy-graph

Override Protocol

If this decision changes or overrides a previous decision logged in strategy-graph:

• Reference the original decision explicitly
• State why the override is justified
• Log as a new decision with type: "override of [original decision name]"

Red Flags

Thought	Reality
"маленькое решение"	Маленькие решения переспрашиваются через 6 месяцев.
"всё и так понятно"	Понятно тебе сейчас. Не понятно никому через год.
"альтернатив не рассматривали"	Нужно рассмотреть хотя бы 2 перед записью.
"это техническое решение"	Технические решения с продуктовым влиянием = продуктовые.
"запишу потом"	Контекст исчезает за часы. Запиши сейчас.
"решили на созвоне"	Созвон — не запись. Нужно зафиксировать здесь и сейчас.

When to Skip

• Obvious formatting/copy decision with no architecture impact
• Reversal of a decision made within the same session (update the original instead)
• Explicitly: "skip decision-logging-rigor"