# Paper skeleton (PRIMUS-style)

Instantiate this on day one of any new paper. Do not write prose into it for the first two weeks — fill in bullets only.

---

## Working title
<single sentence, <= 14 words>

## One-sentence pitch
<the sentence you would say to a stranger in an elevator>

## Target venue
PRIMUS | College Math Journal | J. Mathematical Behavior | J. Computing in Higher Ed | Mathematical Thinking and Learning

## Authorship
- Henry Fan (corresponding, first)
- Jeff Anderson (mentor, second)

## Abstract (draft v0)
<150–200 words. Rewrite every two weeks. Track versions.>

## 1. Motivation
- The problem (in the world, not in the literature)
- Who has it
- Why nobody has solved it well yet

## 2. Background & prior work
- Anderson's relevant prior paper(s)
- 3–5 closely related papers
- The gap this paper fills, in one sentence

## 3. The contribution
- Method / artifact / framework
- Why it is novel
- What it costs (time, money, hardware, expertise)

## 4. The 8-step modeling process (when applicable)
1. Find & understand the real problem
2. Mathematize
3. State ideal model
4. Solve
5. Analyze
6. Verify (← Jeff cares most about this)
7. Transfer
8. Iterate

## 5. The activity / system
- Materials
- Procedure
- What a student / user actually does, minute by minute

## 6. Pilot / evidence
- Setting, n, IRB status
- Pre/post or design-based research
- Honest reporting of failure modes

## 7. Discussion
- What it means
- What it does NOT mean
- Threats to validity

## 8. Limitations & future work
- One paragraph. Be honest.

## 9. Acknowledgements
Jeff's mentorship. Foothill students. Funders (none yet).

## Figures, tables, and one "money figure"
Decide on Day 1: which single figure would a reader screenshot? Build that figure first; it shapes the rest of the paper.

## References (BibTeX file path)
`paper/refs.bib`

---

## Ship checklist
- [ ] One-sentence pitch survives the elevator
- [ ] Money figure exists
- [ ] All claims have a falsifier in the experiment ledger
- [ ] Jeff has read it once with corrections incorporated
- [ ] Code/hardware/data are public and linked from §3
- [ ] Companion video is at least at storyboard stage
- [ ] IRB documentation in the supplement
- [ ] Tagged in git: `submitted-<venue>-YYYY-MM`