User Input --> requirements --> [proposal] --> design --> classify --> plan --> implement
                                    |
                                    +--> Can also be invoked standalone

PROOF REQUIREMENTS:
- List specific files and line numbers
- Show actual code snippets as evidence
- Count occurrences (e.g., "47 files import date-fns")
- Identify breaking change surface

PROOF REQUIREMENTS:
- Include URLs for every claim
- Cite specific numbers (downloads/week, bundle size in KB)
- Reference dated benchmarks (no older than 18 months)
- Note any conflicting information found

PROOF REQUIREMENTS:
- Cite actual blog posts, talks, or documentation
- Note whether company USES it in production vs merely recommends
- Identify if company has CONTRIBUTED to the technology
- Flag any company that has MIGRATED AWAY and why

MAINTAINABILITY VERDICT:
Rate each dependency: SAFE / ACCEPTABLE / RISKY / AVOID
- SAFE: Corporate-backed, foundation-governed, large contributor base
- ACCEPTABLE: Active community, multiple maintainers, stable funding
- RISKY: Single maintainer, no funding, sporadic updates
- AVOID: Abandoned, license concerns, known instability

RISK MATRIX:
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|

# Proposal: <title>

## Metadata

branch_name: `{branch-name}`
descriptive_name: `{descriptive-name}`
created: `{ISO 8601 timestamp}`
status: `draft` | `reviewed` | `approved` | `rejected`
decision: `pending` | `accepted` | `rejected` | `deferred`

## Executive Summary

**Proposal**: <one-sentence description of what is proposed>
**Recommendation**: <ADOPT / TRIAL / DEFER / REJECT>
**Confidence**: <HIGH / MEDIUM / LOW>
**Impact**: <HIGH / MEDIUM / LOW>

<3-5 sentence summary of the proposal and recommendation with key reasoning>

---

## 1. Problem Statement

### Current State
<what exists today, with codebase evidence>

### Pain Points
<specific problems, with evidence from codebase and team experience>

### Desired State
<what we want to achieve>

---

## 2. Proposed Solution

### Description
<detailed description of the proposal>

### Alternatives Considered

#### Alternative A: <name>
- **Description**: <what it is>
- **Pros**: <list>
- **Cons**: <list>
- **Why not chosen**: <specific reasoning>

#### Alternative B: <name>
...

#### Alternative C: Do Nothing
- **Description**: Keep current approach
- **Pros**: No migration cost, no risk
- **Cons**: <list current pain points>
- **Why not chosen**: <or why this is actually fine>

---

## 3. Evidence: Codebase Analysis

### Current Usage
<how this area is currently handled in the codebase>

### Affected Surface Area
- **Files impacted**: {count}
- **Modules affected**: {list}
- **Test files needing updates**: {count}

### Code Evidence
<specific file:line references, code snippets, grep results>

### Dependency Overlap
<existing deps that relate, potential conflicts>

---

## 4. Evidence: Web Sources

### Official Status
- **Latest version**: {version}
- **Release date**: {date}
- **Documentation quality**: {assessment}
- **Roadmap**: {key upcoming changes}

### Adoption Metrics
- **npm weekly downloads**: {number}
- **GitHub stars**: {number}
- **Bundle size**: {size} (minified + gzipped)
- **Dependencies**: {count} ({list critical ones})

### Benchmarks
<performance data with source URLs>

### Security
- **Known CVEs**: {count}
- **Last security audit**: {date or "none"}
- **Snyk/Socket score**: {if available}

### Community Sentiment
<summarized opinions from developer communities, with links>

---

## 5. Evidence: Industry Opinions

### Big Tech Usage

| Company | Uses It? | In Production? | Notes |
|---------|----------|----------------|-------|
| Google | {yes/no} | {yes/no} | {details} |
| Meta | {yes/no} | {yes/no} | {details} |
| Amazon | {yes/no} | {yes/no} | {details} |
| Microsoft | {yes/no} | {yes/no} | {details} |
| Netflix | {yes/no} | {yes/no} | {details} |

### Frontier Company Usage

| Company | Uses It? | In Production? | Notes |
|---------|----------|----------------|-------|
| {company} | {yes/no} | {yes/no} | {details} |

### Notable Endorsements or Rejections
<specific blog posts, talks, or statements from industry leaders>

### Migration Stories
<companies that adopted or abandoned this technology, with outcomes>

---

## 6. Third-Party Maintainability Assessment

### Ownership & Governance

| Aspect | Details |
|--------|---------|
| **Maintainer** | {individual/company/foundation} |
| **Corporate Backing** | {company name or "none"} |
| **Governance Model** | {BDFL/committee/foundation} |
| **License** | {license type} |
| **License Compatible** | {yes/no - with our stack} |

### Health Metrics

| Metric | Value | Assessment |
|--------|-------|------------|
| **Core Contributors** | {count} | {good/concerning} |
| **Bus Factor** | {number} | {safe/risky} |
| **Last Commit** | {date} | {active/stale} |
| **Open Issues** | {count} | {manageable/overwhelming} |
| **Issue Response Time** | {avg time} | {fast/slow} |
| **Release Cadence** | {frequency} | {regular/sporadic} |
| **Breaking Changes (last 3y)** | {count major versions} | {stable/volatile} |

### Funding & Sustainability

| Aspect | Details |
|--------|---------|
| **Funding Model** | {VC/open-core/donations/corporate} |
| **Revenue Source** | {description} |
| **Annual Funding** | {amount if public} |
| **Rug-Pull Risk** | {low/medium/high - with reasoning} |

### Maintainability Verdict

**Rating**: {SAFE / ACCEPTABLE / RISKY / AVOID}

<paragraph explaining the rating with specific evidence>

---

## 7. Long-Term Risk Analysis (2-5 Year Horizon)

### Risk Matrix

| Risk | Probability | Impact | Timeframe | Mitigation |
|------|-------------|--------|-----------|------------|
| {risk} | H/M/L | H/M/L | {when} | {strategy} |

### Technical Risk Details
<detailed analysis of each technical risk>

### Business Risk Details
<detailed analysis of each business risk>

### Ecosystem Risk Details
<detailed analysis of ecosystem trajectory>

### Worst-Case Scenario
<what happens if this goes wrong? How do we recover?>

---

## 8. Implementation Considerations

### Migration Effort
- **Estimated scope**: {small/medium/large}
- **Files to change**: {count}
- **Breaking changes to our code**: {list}
- **Rollback strategy**: {how to undo if it fails}

### Proof of Concept
<outline a minimal PoC to validate the proposal before full commitment>

### Adoption Strategy
- **Phase 1**: {initial adoption scope}
- **Phase 2**: {broader rollout}
- **Phase 3**: {full migration, if applicable}

---

## 9. Decision

### Recommendation: {ADOPT / TRIAL / DEFER / REJECT}

**ADOPT**: Proceed with full implementation
**TRIAL**: Implement PoC first, then decide
**DEFER**: Revisit in {timeframe} when {condition}
**REJECT**: Do not proceed because {reason}

### Conditions for Revisiting
<what would change this decision?>

### Decision Rationale
<final summary tying all evidence together>

---

## 10. References

### Web Sources
- [{title}]({url}) - {brief note}

### Blog Posts & Talks
- [{title}]({url}) - {company/author}, {date}

### Codebase References
- `{file:line}` - {what it shows}

### Related Proposals
- `docs/proposals/{name}/{name}-proposal.md` - {relation}

# Proposal Footprint: {descriptive-name}

**Date**: {ISO 8601 timestamp}
**Subject**: {what was proposed}
**Type**: Proposal / Technical Decision

## Research Summary

### Codebase Analysis
- **Files examined**: {count}
- **Key findings**: {list}
- **Current pain points identified**: {count}

### Web Research
- **Sources consulted**: {count}
- **URLs referenced**: {count}
- **Key data points**: {list}

### Industry Research
- **Big tech opinions gathered**: {count}
- **Frontier company opinions gathered**: {count}
- **Notable endorsements**: {list}
- **Notable rejections**: {list}

### Maintainability Assessment
- **Dependencies evaluated**: {count}
- **Ratings**: {list with verdicts}
- **Critical concerns**: {list or "none"}

## Proposal Result

**Proposal File**: docs/proposals/{descriptive-name}/{descriptive-name}-proposal.md
**Recommendation**: {ADOPT / TRIAL / DEFER / REJECT}
**Confidence**: {HIGH / MEDIUM / LOW}
**Maintainability Verdict**: {SAFE / ACCEPTABLE / RISKY / AVOID}

**Key Evidence Points**:
{top 3-5 most compelling evidence items}

**Key Risks**:
{top 3 risks with mitigation strategies}

## Next Steps

**If ADOPT/TRIAL**: Proceed to /design or /classify
**If DEFER**: Revisit conditions: {conditions}
**If REJECT**: Alternative recommendation: {alternative}

{
  "latest_footprint": "agentic/{branch-name}/footprints/foot-proposal-{descriptive-name}.md",
  "latest_command": "proposal",
  "proposal_file_path": "docs/proposals/{descriptive-name}/{descriptive-name}-proposal.md",
  "next_command_metadata": {
    "command": "/design",
    "category": "proposal",
    "confidence": "{HIGH|MEDIUM|LOW}",
    "reasoning": "Proposal complete, ready for design/planning",
    "required_context": "docs/proposals/{descriptive-name}/{descriptive-name}-proposal.md"
  },
  "next_command": "/design",
  "proposal_timestamp": "{ISO 8601 timestamp}",
  "branch_name": "{branch-name}",
  "descriptive_name": "{descriptive-name}",
  "proposal_subject": "{subject}",
  "recommendation": "{ADOPT|TRIAL|DEFER|REJECT}",
  "maintainability_verdict": "{SAFE|ACCEPTABLE|RISKY|AVOID}",
  "evidence_summary": {
    "codebase_files_examined": "{count}",
    "web_sources_cited": "{count}",
    "industry_opinions_gathered": "{count}",
    "dependencies_evaluated": "{count}"
  }
}

{
  "proposal_file_path": "docs/proposals/{descriptive-name}/{descriptive-name}-proposal.md",
  "research_file_path": "docs/proposals/{descriptive-name}/{descriptive-name}-research.md",
  "recommendation": "ADOPT | TRIAL | DEFER | REJECT",
  "confidence": "HIGH | MEDIUM | LOW",
  "maintainability_verdict": "SAFE | ACCEPTABLE | RISKY | AVOID",
  "evidence_counts": {
    "codebase_files": "{count}",
    "web_sources": "{count}",
    "industry_opinions": "{count}",
    "dependencies_evaluated": "{count}",
    "risks_identified": "{count}"
  },
  "key_finding": "{one-sentence most important finding}",
  "next_command": "/design | /classify | (none if rejected/deferred)",
  "footprint_path": "agentic/{branch-name}/footprints/foot-proposal-{descriptive-name}.md",
  "state_path": "agentic/{branch-name}/state.json"
}

/proposal tanstack-table "Replace ag-grid with TanStack Table for data grids"

/proposal redis-caching "Add Redis caching layer for API responses"

/proposal temporal-api "Replace date-fns with Temporal API"

requirements --> proposal --> design --> classify --> plan --> implement

/proposal {name} "{subject}"

## References
- `docs/proposals/{name}/{name}-proposal.md` - Evidence-based evaluation of {subject}

## Relevant Files
- `docs/proposals/{name}/{name}-proposal.md` - Proposal with maintainability assessment and risk analysis