Public, sanitized mirror of an AI orchestration command center: agents, skills, MCP servers, slash-command workflows. All infrastructure identifiers, hostnames, mesh IPs/subnets, repo paths, maintainer identity, and hardware fleet specifics scrubbed to <placeholders>; session debug logs and host-specific memory removed. No live credentials. Verified clean by automated leak sweep. See SANITIZATION.md. churchofmalware.org . authorized research only
3.8 KiB
Decision Framework: {{DECISION_TITLE}}
Generated: {{DATE}}
1. The Decision
Question: {{DECISION_QUESTION}}
Context: {{CONTEXT}}
Key Tension: {{KEY_TENSION}}
2. First Principles Test
Core Question: Does this solve a problem you cannot solve yourself?
Your Current Capabilities: {{CURRENT_CAPABILITIES}}
Assessment: [ ] No — I can do this myself | [ ] Partial — some unique value | [ ] Yes — solves what I can't
Notes:
3. Timing Assessment
| Factor | Value | Notes |
|---|---|---|
| Weeks until key milestone | ||
| Hours/week available | ||
| Total hours before milestone |
Timing verdict: Is now the right time?
4. Stakeholder Analysis
Key stakeholders: {{STAKEHOLDER_INFO}}
Stability assessment (1-10): ____
| Score | Interpretation |
|---|---|
| 1-3 | High risk — low confidence in stability |
| 4-6 | Moderate — monitor for changes |
| 7-10 | Solid — verify this is evidence-based |
5. Bias Audit
Check any biases you recognize in yourself:
-
FOMO — Fear of missing a rare opportunity
- Counter: What evidence suggests this is truly unique?
-
Sunk Cost — Factoring in past investment of time/money
- Counter: Past investment is gone. This decision is forward-looking.
-
Authority Bias — Influenced by credentials or status
- Counter: Authority ≠ correctness or fit for you.
-
Social Proof — Following because others are
- Counter: Others' choices may not match your context.
-
Commitment Consistency — Feeling obligated by past statements
- Counter: New information justifies reassessment.
-
Optimism Bias — Assuming problems will resolve
- Counter: Look at patterns, not hopes.
-
Recency Bias — Overweighting recent events
- Counter: Consider the full timeline.
-
Confirmation Bias — Seeking only validating information
- Counter: What would disprove this?
-
Shiny Object — Attracted by novelty
- Counter: Is this genuinely better, or just new?
-
Loss Aversion — Overweighting potential losses
- Counter: Compare actual probabilities.
Total biases identified: ____
6. Opportunity Cost Calculator
| Component | Value |
|---|---|
| Hours/week × Weeks | |
| × Hourly rate | |
| = Direct cost |
What else could that time produce?
- {{ALTERNATIVE_1}}
- {{ALTERNATIVE_2}}
- {{ALTERNATIVE_3}}
True opportunity cost assessment:
7. Scenario Matrix
| Scenario | Probability | Outcome | Notes |
|---|---|---|---|
| Worst case | {{WORST_PROB}}% | {{WORST_OUTCOME}} | |
| Bad case | % | ||
| Neutral | {{NEUTRAL_PROB}}% | {{NEUTRAL_OUTCOME}} | |
| Good case | % | ||
| Best case | {{BEST_PROB}}% | {{BEST_OUTCOME}} |
Expected value assessment:
8. Pre-Mortem
Imagine it's {{FUTURE_DATE}}. This decision failed. Why?
Possible causes: 1. 2. 3.
Which are within my control?
Warning signs to watch for:
9. Questions to Resolve
Before deciding, get answers to:
{{QUESTIONS_LIST}}
10. The 10-10-10 Framework
How will I feel about this decision in...
- 10 minutes?
- 10 months?
- 10 years?
11. Regret Minimization
Imagine you're 80 looking back.
- Would you regret doing this?
- Would you regret NOT doing this?
12. Decision
Options: {{DECISION_OPTIONS}}
My decision:
Rationale:
Boundary statement (what I will and won't do):
Review date:
Summary
| Factor | Assessment |
|---|---|
| Solves unique problem | |
| Timing | |
| Stakeholder stability | |
| Biases identified | |
| Opportunity cost | |
| Probability of success | |
| Regret profile |
Final recommendation: