Beside the account: the readers' disagreements (C5c-01)

Target length: about 600 words. Stage C5 section 8 prints a disagreement about how to tell the account beside it. The three readers each read account.md at pass 4 with three rooms. For each room they were shown its facts and 7 coded passages drawn at random. Their errors and unclear sentences were fixed in pass 5. These points stand as the readers made them, each with my answer.

cardinals: "does not fit" (all three readers)

• Reader 1: "The sample shows no build or build report. At h53.78 a member asked 'Why no cardinals logo on /r/place?'. Another answered with a condition and a delay: 'If someone gets it started, I'll help after the game.' That answer is not the bare line the account describes, and it waits for a starter who does not appear in the sample."
• Reader 2: "For most of the canvas, the room watched a rival's mark and wished for its own."
• Reader 3: "That talk about a rival comes before any start."

My answer. The seven passages served were 7 of the room's 102. The full record has a call at h36.28 ("[Season 3] Let's make the Cardinals logo in /r/place!" [cardinals/c0024]), a build report at h57.09 ("Nice start just below the blue note. Could use some fixing up" [cardinals/c0035]) and the finished logo at h73.15 ("...and it's done." [cardinals/c0039]). The call comes before the rival talk at h41.05. So the account's chain runs in the room, and the readers could not see it in what I served. That is my error in the packet, not theirs.

Two things they saw stand:

• The room was slow. The call at h36.28 produced no reported build for about 21 hours.
• An answer can commit on a condition. The account now says such answers exist, and that it does not count them.

mysterydungeon: celebration before upkeep (reader 2)

• Reader 2: "In this room, celebration came before upkeep, the reverse of the account's order from building to upkeep to celebration."

My answer. The account claims that upkeep follows the first build report [A03] and that celebration follows it too [A07]. It claims no order between upkeep and celebration. In this room both follow the call and the build, so the room fits as the reader found it.

mysterydungeon: a move with no doubt shown (all three readers)

• Reader 1: "The coder's theme names moving the Time Gear, but the sample shows no doubt about hands (K02) before that move, so A10 cannot be checked here."

My answer. A10 is thin: it rests on 21 rooms, and its one instance failed its audit. The account already says so. The room is a sample of 7 passages, and nothing changes.

luciomains: on the list, yet it fits (all three readers)

• Reader 3: "The account lists luciomains among the rooms it cannot reach, but its sample fits the chain from calls to celebration."

My answer. The readers are right, and the account was wrong to say "cannot reach". The last story told luciomains with a residue: it told the organizing and left one part unexplained, the jokes that turned the work into the room's own game. Pass 5 says this.