# Team HCI

- **Event:** [Built with Opus 4.7: a Claude Code hackathon](https://cerebralvalley.ai/e/built-with-4-7-hackathon)
- **When:** Apr 21 at 12:00 PM – Apr 27 at 2:00 AM (EDT)
- **Where:** Online
- **Team:** [Bektour](https://cerebralvalley.ai/u/bektour)
- **GitHub:** https://github.com/Apolotary/probe-researcher
- **Demo video:** https://youtu.be/zB40JrTdV-s
- **Gallery:** https://cerebralvalley.ai/e/built-with-4-7-hackathon/hackathon/gallery
- **Page:** https://cerebralvalley.ai/e/built-with-4-7-hackathon/hackathon/gallery/97

I'm an HCI researcher, and I keep running into the same problem:
every claim has to be tested with real users. Two to three months
of recruitment per study, another six months for the publication
cycle, and very little room to discover — halfway through — that
something basic about the design was off.

Probe is a rehearsal stage for study design, powered by Claude
Opus 4.7. You start with a one-sentence premise. Opus splits it
into three sub-research-questions — mechanism, intervention, lived
experience. Sonnet 4.6 surveys arXiv, ACM, and Semantic Scholar
per angle. Opus then drafts three candidate study designs; you
pick one, and Probe writes the actual artifacts: implementation
plan, IRB memo, validation protocol, survey kit, diary kit.

A simulated pilot runs twelve composite personas through the
protocol — surfacing failure modes before recruitment. The final
stage is an adversarial peer-review panel; Opus 4.7 then audits
their disagreement and separates real conflicts from apparent ones.

---

Markdown version of https://cerebralvalley.ai/e/built-with-4-7-hackathon/hackathon/gallery/97. Site index for agents: https://cerebralvalley.ai/llms.txt · full text: https://cerebralvalley.ai/llms-full.txt