You asked
How do I set up the game?
Answered counted as answeredAsked with: Sky Teambg-373106-en-1e
To set up the game, follow these steps: 1. Place the Control Panel between the players, who should ideally be sitting next to each other on the same side of the table [1]. 2. Ensure the arrow on the Airplane Axis disc is pointing at the black triangle at the top [1]. 3. Ensure all Switches are covering the green lights [1]. 4. On the Speed Gauge, place the blue Aerodynamics marker between the 4 and the 5 [1]. 5. Place the orange Aerodynamics marker between the 8 and the 9 [1]. 6. Place the Brake marker to the left of the 2 on the Brake track [1]. 7. The player on the side with the blue spaces plays the Pilot; give them the 4 blue dice [1]. 8. The player on the side of the orange spaces plays the Co-Pilot; give them the 4 orange dice [1]. 9. Slide the Altitude T rack (green/yellow side) into the slot at the top right of the Control Panel until the number 6000 is visible in the screen [1]. 10. Slide the YUL Montréal-T rudeau Approach T rack into the slot at the top left of the Control Panel until the icon is visible in the screen [1]. 11. Place a Reroll token on each Reroll icon on the Altitude T rack [1]. 12. Place as many Airplane tokens as there are Traffic icons on each space of the Approach T rack [1]. 13. Create a reserve of Coffee tokens by placing them next to the board (not on the board) [1]. 14. Give a screen to each player and read the reminders written inside [1].
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 299 ms · ask 6821 ms · total 1862449 ms
- single-flight (PR-5)
- queued 1855319 ms · generation 7130 ms
- retrieval refs (raw)
- [{"page": 3, "score": 0.04918, "snippet": "Place the Control Panel between the players, who should, ideally, be sitting next to each other on the same side of the table. Make sure the arrow on the Airplane Axis disc is pointing at the black triangle at the top, and that all Switches are covering the green lights. On the Speed Gauge, place th", "headingPath": "", "sharpsignalDocId": 202}, {"page": 4, "score": 0.032258, "snippet": "STRATEGY DISCUSSION AND DICE ROLLS DICE PLACEMENT END OF ROUND Discuss your strategy at the beginning of every round. For example, 'We really need to get rid of that plane, ' or 'Let's make sure we advance 2 spaces.' You are not allowed to discuss the dice. Saying things like, 'If you get a 6 , put ", "headingPath": "WHEN YOU FIRST OPEN THE BOX · STRATEGY DISCUSSION AND DICE ROLLS 1 · REROLL · GENERAL RULES", "sharpsignalDocId": 202}, {"page": 1, "score": 0.031746, "snippet": "PRÉPAREZ-VOUS POUR L'ATTERRISSAGE Take the controls of an airliner with your trusty crewmate, coordinate your efforts, and land your aircraft all over the world! In this cooperative game, you play a team of pilots charged with landing your commercial airliner at airports all over the world. But land", "headingPath": "LANDING PROCEDURE", "sharpsignalDocId": 202}, {"page": 9, "score": 0.03125, "snippet": "Brake enough to bring the plane to a halt once it touches the runway. Place a die respecting the number constraint. The brakes must be deployed in order , starting with the 2 space. IMMEDIATELY advance the red Brake marker one space. The Brakes only have an impact in the game's final round. You must", "headingPath": "Example · VICTORY CONDITION · REROLLS · DECREASING ALTITUDE", "sharpsignalDocId": 202}, {"page": 2, "score": 0.030769, "snippet": "Start by removing and throwing out all parts of the Control Panel with this symbol: WHEN YOU FIRST OPEN THE BOX 1 Stick the airplane sticker on the Airplane Axis disc. Place the Airplane Axis disc into its space. 3 Stick the 9 double-sided stickers on the indicated spaces on the inside and back of t", "headingPath": "", "sharpsignalDocId": 202}, {"page": 8, "score": 0.030303, "snippet": "Deploy the flaps. Each flap extended increases the aircraft's lift and wind resistance. Place a die respecting the number constraint. Deploy the Flaps in order, from top to bottom. Slide the Switch below your die to show the green light. IMMEDIATELY advance the orange Aerodynamics marker one space. ", "headingPath": "VICTORY CONDITION · CONCENTRATION · Example", "sharpsignalDocId": 202}, {"page": 7, "score": 0.029851, "snippet": "Communicate with the Control Tower to clear the traffic on your approach path. The Pilot has only 1 space to place a Radio die, and the Co-Pilot has 2. On the Approach Track, count the number of spaces, starting with your Current Position, and IMMEDIATELY remove one Airplane token from that space. I", "headingPath": "RADIO · Example · LANDING GEAR Pilot only · AERODYNAMICS AND SPEED · VICTORY CONDITION", "sharpsignalDocId": 202}, {"page": 12, "score": 0.029412, "snippet": "The briefing period that comes before every round is very important. Look closely at the Approach Track and study your overall situation. Is it better to advance 0, 1, or 2 spaces? What elements could cause you to lose the game? What is urgent? What can wait? In Sky Team, there are 2 ways to communi", "headingPath": "THE BRIEFING PERIOD · COMMUNICATION · PLACING YOUR DICE · THE AXIS · CONCENTRATION · DELAYING · …", "sharpsignalDocId": 202}]
- citations (raw)
- [{"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 202}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 202 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 202 boosted
- answered-before recall
-
this ruling was answered, so past rulings were not offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
- debug row retained until
- Nov 6, 2026 14:41
retrieval — what the search arm returned
score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. This ruling ran the THREE-ARM fuse (full-text + vector + the doc-priority boost arm, which carried the base rulebook and/or the errata corrections this query matched), whose arithmetic ceiling is 0.04918 — all three arms ranking the same chunk #1 (ceiling = arms/(k+1) at k=60). The measured healthy band 0.016–0.033 was measured on TWO-arm asks and does not bound this one: its high end is the two-arm ceiling, and a third arm has room above it. A chunk only one arm ranked highly lands near 0.016 (that one arm's #1 vote), so 0.03 here is an excellent hit, not a 3% match.
per-arm ranks (the rank each search arm gave a chunk): NOT DISCLOSED by the gateway. Fusion happens gateway-side and only the FUSED score crosses the wire, so rulesage cannot show them without a gateway change. The rank column below is the FUSED rank (position in the returned list), which is real.
token count per chunk: NOT DISCLOSED — chunk token counts are not reported on the ask path. The character counts below are of the bounded snippet/quote rulesage actually received — a real measurement of what we hold, never an estimate of the chunk.
| fused rank | document | heading | page | fused RRF score | snippet chars |
|---|---|---|---|---|---|
| #1 | RULEBOOK Sky Team — Rulebook (corpus doc 202) | p.3 | 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) | 300 | |
| #2 | RULEBOOK Sky Team — Rulebook (corpus doc 202) | WHEN YOU FIRST OPEN THE BOX · STRATEGY DISCUSSION AND DICE ROLLS 1 · REROLL · GENERAL RULES | p.4 | 0.032258 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one)) | 300 |
| #3 | RULEBOOK Sky Team — Rulebook (corpus doc 202) | LANDING PROCEDURE | p.1 | 0.031746 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one)) | 300 |
| #4 | RULEBOOK Sky Team — Rulebook (corpus doc 202) | Example · VICTORY CONDITION · REROLLS · DECREASING ALTITUDE | p.9 | 0.03125 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one)) | 300 |
| #5 | RULEBOOK Sky Team — Rulebook (corpus doc 202) | p.2 | 0.030769 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one)) | 300 | |
| #6 | RULEBOOK Sky Team — Rulebook (corpus doc 202) | VICTORY CONDITION · CONCENTRATION · Example | p.8 | 0.030303 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one)) | 300 |
| #7 | RULEBOOK Sky Team — Rulebook (corpus doc 202) | RADIO · Example · LANDING GEAR Pilot only · AERODYNAMICS AND SPEED · VICTORY CONDITION | p.7 | 0.029851 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one)) | 300 |
| #8 | RULEBOOK Sky Team — Rulebook (corpus doc 202) | THE BRIEFING PERIOD · COMMUNICATION · PLACING YOUR DICE · THE AXIS · CONCENTRATION · DELAYING · … | p.12 | 0.029412 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one)) | 300 |
chosen chunks — what the answer actually cited
token count per chunk: NOT DISCLOSED — chunk token counts are not reported on the ask path. The character counts below are of the bounded snippet/quote rulesage actually received — a real measurement of what we hold, never an estimate of the chunk.
| # | document | heading | page | quote chars |
|---|---|---|---|---|
| [1] | RULEBOOK Sky Team — Rulebook (corpus doc 202) | p.3 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 299 ms · first delta 4568 ms · total 1862449 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 1855319 ms · retrieval 299 ms · ask 6821 ms · gateway work 7130 ms · total 1862449 ms
- tokens in (the prompt the answerer read)
- 3573
- tokens out (what the answerer generated)
- 371
- tok/sec
- 148.9 tok/sec — 371 output tokens in 2.492 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 31s ago)
- stream path
- streamed — the gateway pushed at least one accumulated draft
- watchdog
- first-token watchdog: 30s per arming window (rulesage.table.first-token-watchdog-seconds), re-armed once by the passages frame — so the worst case before a reader falls back to polling is 60s. Whether it actually fired is a BROWSER-side decision that never reaches the server, so it is not recorded here. The stream path above is the server's half of that story: whether a delta was emitted at all.
- num_ctx · think posture
- both are the CHILD's settings, not rulesage's, and no ask reply carries them — an answer never states which context window or think posture produced it. The live-seat line above reads them from the running child instead, where the gateway can answer for itself; it describes the child NOW, not this ask.
disposition
- outcome
- ANSWERED — Answered
- abstain rationale (n/a — this ruling answered)
- answered — no abstain rationale applies
setup-shape — why the checklist band did or didn't render
- decision
- NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
- pattern that matched
- SETUP — "setup" / "set up"
- matched words (in the normalized question)
-
set up
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 127), so "no registered errata card matched" above could never have matched one
Errata scope: the gate above matched this ruling's own edition only. When an ask also reads an expansion, that expansion's own registered errata cards stay outside the match — a stated phase-1 limitation, not a failed lookup.