docs: Proposal triage & 80:20 analysis with strategic gaps

[82deutschmark]

Proposal Triage Analysis

Simon requested an 80:20 analysis of the proposal landscape to find quick wins.

What's in This PR

1-triage.md contains:

• The 20% (5-7 high-leverage proposals) driving 80% of architectural value
• Quick wins (parameter tweaks, no rewrites) that unlock 80% value with 20% effort
• Critical gaps (11 missing proposals that should be written)
• 2nd/3rd order effects showing how FermiSanityCheck ripples through the stack
• Strategic questions Simon might not be asking (unit economics, data moat, competition, scale, margins)
• Relevant tasks we can execute proactively (dependency graphs, complexity gating, stakeholder validation)
• Recommended execution path (Phase 1-3 roadmap)

Key Findings

The 20% (High-Leverage):

• Status Stopped prematurely, the output may be incomplete. 210 seconds elapsed. #7 Elo-Ranking (core ranking engine)
• flask-admin less load when browsing the Taskitem table #63-66 Orchestration cluster (Luigi + post-plan + swarm)
• feat: Add FermiSanityCheck validation for quantified assumptions #69 Arcgentica-agent-patterns (hardening via arcgentica)
• feat: propose domain-aware plan ranking engine with relative comparison #62 Agent-first frontend (discoverability)
• Validation cluster: FermiSanityCheck + Red-team + Drift monitor

Quick Wins:

• Status Stopped prematurely, the output may be incomplete. 210 seconds elapsed. #7: Parameterize ranking weights (cost vs. feasibility) → 2-4 hours
• docs: deep implementation sections for 5 proposals (31-35) #32: Parameterize Gantt lanes → 1-2 hours
• docs: deep implementation sections for 10 proposals (21-30) #36-37: Parameterize distributions → 1-2 hours
• docs: deep implementation sections for proposals 01-20 and 51 #38+feat: add Start New Plan form to dashboard + auto-sync upstream workflow #44: Unified risk terminology → 2-3 hours
• feat: propose domain-aware plan ranking engine with relative comparison #62+Status Stopped prematurely, the output may be incomplete. 210 seconds elapsed. #7: Shared ranking heuristics → 2-3 hours

Critical Gaps:

• Execution feedback loop (how to learn from execution)
• Stakeholder assumption validation (de-risk early)
• Complexity gating (don't over-engineer small projects)
• Software plan specialization (bridge to code)
• Cost reduction curve (achieve improving margins)

Next Steps

1. Simon reviews and provides feedback on priorities
2. We execute Phase 1 (FermiSanityCheck + sizing matrix + dependency graph)
3. Phase 2: Parameter tweaks for quick wins
4. Phase 3: Strategic gap-filling proposals

---

PR by Larry + Egon, 26 February 2026