Step 11 of 12 · 15 min

Form a team

Team formation is at kickoff. You do not need a team before then. Name the jobs even if one person holds two of them for a weekend.

Six roles

Capacity is up to 50 participants per campus. A published team-size cap beyond that room limit is Details coming soon.

The Domain guide describes day-one jobs such as framing and storytelling. Those jobs sit inside the roles below. They do not create a second team system.

  1. Domain/Problem Lead. Owns the problem statement and USE-CASE.md.
  2. Data Lead. Knows what the data is, what was left out, and what would leak.
  3. Classical Baseline Lead. Produces the score the quantum run has to face.
  4. Quantum/Qiskit Lead. Owns the circuit or the written reason there is no circuit.
  5. Benchmark/Evidence Lead. Keeps the metric, the configuration, and the limitation next to every number.
  6. Documentation/Demo/Pitch Lead. Owns the README, the demo, and the five-minute story.

How to find each other

Bring a half-finished use-case canvas from the Domain guide. Read it aloud at team formation on October 1, 2026. Builders are looking for a real problem. Domain partners are looking for someone who will write the limitation down.

When do you have to arrive with a finished team?

Choose one answer when you are ready. This is practice.

Prepare the GitHub submission