# project_highlevel — active tasks

## Active

1. **Today (2026-06-02)**: support Cameron's left/right hemisphere split design for the TRI Phase 1 OOD experiment. He's recollecting demos with paper-ready setup. Watching for results to land later this week.

2. **By 2026-06-08**: drive the Phase 4 lead-task decision (desk organize vs cup-continuation vs crumbled-shirt). Per `vault/para/tasks.md` item #3.

3. **Continuous**: keep `vault/para/{overview,tasks}.md` and `notes/tri_internship_plan.md` in sync with Cameron's actual progress. Weekly retro every Sunday or Monday morning (Phase X gate hit / missed?).

4. **Standing**: re-surface durable strategic decisions Cameron has signed off on whenever they become relevant — esp. "lead with data efficiency, not robustness as headline" (2026-05-25), "head > backbone is a new paper claim" (2026-05-19), "drop UMI, dropped 2026-05-11."

5. **Late July / early August**: surface the FidExoskeleton V2 paper revision (Wk 11) — make sure Cameron captures Raiden-vs-FidExo calibration residuals NOW while the infra is hot.

## Recently completed

- 2026-05-30: Filed FidExoskeleton V2 plan into `tri_internship_plan.md` + memory
- 2026-05-29: 15-demo mug-pick result acknowledged; sticky-number sharpened to "15 vs 3,000+"
- 2026-05-26: Spec'd + dispatched manager to create `yams` agent; wrote handoff
- 2026-05-25: TRI internship plan doc written (`notes/tri_internship_plan.md`); life-vs-research-vs-arm-v2 sequencing resolved through long conversation
- 2026-05-19: PARA architecture finalisation acknowledged + CLAUDE.md updated; "head > backbone" framing surfaced as new paper claim
- 2026-05-12: Lab presentation deck shipped at `omidlab.net/para_presentation` (22 slides)

## Blocked

(none)

## Anti-patterns I've helped Cameron avoid (not "tasks" but recurring patterns I should watch for)

- **Bundling**: "since I'm doing X (necessary), I'll also do Y (exciting)" — usually scope expansion in disguise. See `memory.md`.
- **Anxiety → addition**: when stuck, Cameron's instinct is to add workstreams (Onshape, arm v2, second projects). Push back: "subtract until you can put everything into the one thing that matters most this month."
- **Pitching from mechanism, not from paradox or result** — see `memory.md`.