Rulebook

If you haven't already, open Present to Room for the class, name teams and share their private invitations, and begin card selection when every team is ready.

Draw an Ink card. Every team uses the same Ink in a round.

Set the round timer (a few minutes is usually more than enough time for even the most demanding Ink card). Teams choose and seal one Territory and one Legend from their dealt cards. Watch the selection count on the host dashboard.

If a team has not finished, choose Assign stragglers before Map Making. This fills only the missing Territory or Legend from that team's dealt cards; it does not replace a selection the team already made.

If one team's hand makes a useful pairing impossible, use that team's Redeal control to give it new cards. Teams can also choose Request a redeal and tell you what's giving them trouble. The request appears in your Communications inbox alongside their current cards. You can redeal or choose Keep hand. Sometimes the connection needs a bit more thought; sometimes the cards really are bunk.

Once an Ink card has been drawn and the timer is set, choose Start Map Making. Every team has a countdown on their screen and "Present to Room" also displays the countdown.

Teams create their Maps. This is when they plan their skit or draw their picture or think of the story they're going to tell, etc. Make sure that every team has sealed their cards and that everyone's doing something. You can also pause the timer at this point or jump to zero, but don't worry, nothing in the game changes without you moving to the next stage.

Teams can also annotate how they plan to connect their Territory and Legend. This is optional, and only their team and the host can see it. It's a good job for someone who's not holding the pen or rehearsing the scene, etc. The explanation becomes read-only when you open voting, so it records what they were thinking before everyone else weighs in.

When the class is ready, open voting.

Teams present their Maps informally. For example, if they've made an image, you can hold each one and walk it around to the different groups or they can stand up and present their skits. Order doesn't matter. On the voting screen, each team chooses which Territory and Legend it perceives in every other team's Map. They can also write an annotation explaining how they perceived that connection. These are optional, but worth encouraging: choosing an answer is one thing; explaining what led you there is another — and they give you something to grade in addition to their Map-making efforts.

Teams can flag a Map as Pioneering if it revealed a connection or perspective they'd never thought of. They can nominate as many teams as they like, or none. Each nomination counts once on the Pioneers leaderboard when you release the voting matrix. Exceptional effort is recognized separately from percentage correct voted received.

An annotation stays private to its authors and the host unless the team selects the envelope to request sharing it. After they seal their ballots, these requests appear in your Communications inbox for review. Approving a note sends it to the team addressed once that team's Map has been revealed. Teams find received notes in Team Annotations → Inbox.

Teams choose Review ballots to check their votes, annotations, Pioneer nominations, and sharing requests. They can go back and edit, or choose Seal ballots to submit everything for the round. Once sealed, those choices are final. While waiting, they can return to their Team Annotations. If the room cannot continue, use End voting early.

Release Maps one at a time. This is a fun action as a class. Each team's actual Territory-Legend pairing will appear on "Present to Room" along with how every other team voted. Here you can discuss how the teams have represented the Territories and Legends

This is also when teams should annotate the round, that is, reflect on the Map they made, the Maps other teams made, and how they understood those. Under Looking back in Team Annotations, they can write about what they see differently now. These reflections stay private to the team and host and appear in your downloadable Host reports, so you can return to them later for discussion or grading.

When the room is ready, choose Release vote matrix. The released matrix shows how the class recognized each Map and which Maps entered the Seminar Atlas.

If a team's Map was successfully recognized by the threshold you set (eg, a majority of the other teams), then they will get to set an Atlas tile by picking a picture to go in the Atlas. Teams can click that tile to inspect and annotate the Map. Unlike their private round reflections, these annotations are intended for the seminar Atlas. You review them before they appear there.

Open the Communications inbox to review Atlas annotations and notes teams want to share. You can review them individually or select several at once. Rejecting removes an annotation from review, but keeps it in your downloadable Host report. Approving publishes it on the Atlas or sends it to the team addressed; its authors earn 1 Archivist point when it is published or delivered. Gilding approves an excellent contribution and makes it worth 5 points in total. Save this for something incisive: an observation that helps the class see more in the Map. Private round explanations and reflections don't earn these points.

When the class is ready, start a new round. The next round begins again with card selection and a new Ink card.

Reports become available after you release the first round's voting matrix. The Host reports include private writing and rejected annotations, so keep those for your own review. The Student report collects released voting matrices, Atlas Maps and their approved annotations, delivered notes, and leaderboard results, including Pioneer nominations. It leaves out private, pending, and rejected writing. This is the version to post for the class afterward.