You asked
How should we prepare everything before the first turn?
Answered counted as answeredAsked with: Navegadorbg-66589-en-1e
To prepare for the game, follow these steps: 1. Set up the market by marking the prices for sugar, gold, and spices with a wooden cube at the fourth line from above [1]. 2. Turn over the colony tokens for sugar (9x), gold (11x), and spices (13x) with their prices down, shuffle them well, and distribute them on 12 hidden stacks depicted on the game board, ensuring each stack contains the number of tokens indicated by its position (1, 2, 3, or 4); one token of each type remains hidden and is removed from the game [2][1]. 3. Place one privilege to each arch inside the gallery [2]. 4. Place a token indicating that 2 ships are lost at Nagasaki, and also at Macau if there are only 2 or 3 players [2]. 5. Place an explorer (round wooden disk) on the compass rose of all 12 sea regions except Portugal [2]. 6. Place the buildings yet to be built on the game board: 6 factories for sugar, gold, and spices on the three lines above, and the remaining shipyards and churches on the two lines below, placing them from left to right (avoiding covering the most expensive positions if there are more than 2 players) [2]. 7. Each player starts with 2 ships of their color in the sea region of 'Portugal', 3 workers in Lisboa (marking the '3' field), and their octagonal game stone on the rondel [1]. 8. Each player receives 200 Cruzados, a King's privilege, and their other 5 ships into their personal supply, along with their player sheet containing 1 starting factory (orange), 1 shipyard (brown), and 1 church (grey) [1]. 9. After the starting player has been allotted, the last player receives the 'Navegador' playing card [1][3].
🔧 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 239 ms · ask 7344 ms · total 40698 ms
- single-flight (PR-5)
- queued 33104 ms · generation 7594 ms
- retrieval refs (raw)
- [{"page": 9, "score": 0.032787, "snippet": "The game starts in phase I. After the exploration of Cabo da Boa Esperança the game enters phase II, and after the exploration of Malaca it enters phase III. This is emphasized on the game board by red borderlines (instead of the usual blue ones), and by a small diagram showing the phase numbers whi", "headingPath": "GAME PHASES · NAVEGADOR", "sharpsignalDocId": 407}, {"page": 3, "score": 0.032258, "snippet": "Setting up the game is described in detail in the quick intro (download: www.pd-verlag.de/ navegador). This is a short summary: In the fourth row from the top, cubes marking the prices for sugar, gold and spices are placed. Each player starts with 2 ships of his color in Portugal, places his worker ", "headingPath": "SET UP · 1. Market · 2. Players · 3. Colonies · 4. Privileges · 5. Dangerous sea regions · …", "sharpsignalDocId": 407}, {"page": 4, "score": 0.031746, "snippet": "36 ships 5 workers 5 game stones 12 wooden disks 10 churches 10 shipyards 23 factories 3 price markers 5 player sheets 33 colony tokens 35 privilege tokens 1 Navegador card 2 markers for double loss of ships 1 game board 1 game rules 1 quick intro 1 almanac of historical persons coins in 10, 50, 100", "headingPath": "Wooden Pieces · Cardboard Pieces · ACTION SELECTION · Example: · AT START", "sharpsignalDocId": 407}, {"page": 9, "score": 0.03125, "snippet": "The game end can be triggered in two ways: either after the sea region of Nagasaki has been explored, or after the last building has been taken. After the game end has been triggered in one of those ways, each player, including the one who triggered the end, takes a single final turn and then the ga", "headingPath": "END OF THE GAME · SCORING", "sharpsignalDocId": 407}, {"page": 7, "score": 0.030769, "snippet": "For each factory 1 respective unit of goods may be processed. White factories process sugar, yellow factories gold, and brown factories process spices. The starting factory (orange) works as a wildcard and can be used to process 1 unit of any type free of choice. For each processed unit the player r", "headingPath": "Processing goods with factories · Selling and processing", "sharpsignalDocId": 407}, {"page": 12, "score": 0.030303, "snippet": "The game is in phase I, the possible movements of ships are shown with arrows. The sea region 'Cabo da…' still contains an explorer (round disk), where only a joint fl eet of 2 ships can enter. If both ships enter that region, one ship is lost. In return the player receives the explorer onto his pla", "headingPath": "ABOUT THE DEVELOPMENT OF NAVEGADOR · Necessary workers:", "sharpsignalDocId": 407}, {"page": 6, "score": 0.029851, "snippet": "places the explorer disk from the board on his player sheet, reveals the colony tokens from the corresponding stack, and receives a bonus from the bank, amounting to the price for the cheapest revealed colony. The newly revealed colony tokens are displayed face up at the region. It is not possible t", "headingPath": "PLAYER'S ACTIONS · Example: · COLONY", "sharpsignalDocId": 407}, {"page": 11, "score": 0.029412, "snippet": "This card entitles the holder to conduct an extra sailing action immediately before his turn, and is then passed to his neighbor sitting to the right. 3. Colonies The colony tokens for sugar (9x), gold (11x), and spices (13x) are turned over with their prices down, shuffl ed well, and distributed on", "headingPath": "ABOUT THE DEVELOPMENT OF NAVEGADOR", "sharpsignalDocId": 407}]
- citations (raw)
- [{"page": 11, "quote": null, "headingPath": "ABOUT THE DEVELOPMENT OF NAVEGADOR", "sharpsignalDocId": 407}, {"page": 11, "quote": null, "headingPath": "ABOUT THE DEVELOPMENT OF NAVEGADOR", "sharpsignalDocId": 407}, {"page": 4, "quote": null, "headingPath": "Wooden Pieces · Cardboard Pieces · ACTION SELECTION · Example: · AT START", "sharpsignalDocId": 407}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 407 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 407 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 7, 2026 05:01
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 Navegador — Rulebook (corpus doc 407) | GAME PHASES · NAVEGADOR | p.9 | 0.032787 (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 |
| #2 | RULEBOOK Navegador — Rulebook (corpus doc 407) | SET UP · 1. Market · 2. Players · 3. Colonies · 4. Privileges · 5. Dangerous sea regions · … | p.3 | 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 Navegador — Rulebook (corpus doc 407) | Wooden Pieces · Cardboard Pieces · ACTION SELECTION · Example: · AT START | p.4 | 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 Navegador — Rulebook (corpus doc 407) | END OF THE GAME · SCORING | 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 Navegador — Rulebook (corpus doc 407) | Processing goods with factories · Selling and processing | p.7 | 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 Navegador — Rulebook (corpus doc 407) | ABOUT THE DEVELOPMENT OF NAVEGADOR · Necessary workers: | p.12 | 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 Navegador — Rulebook (corpus doc 407) | PLAYER'S ACTIONS · Example: · COLONY | p.6 | 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 Navegador — Rulebook (corpus doc 407) | ABOUT THE DEVELOPMENT OF NAVEGADOR | p.11 | 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 Navegador — Rulebook (corpus doc 407) | ABOUT THE DEVELOPMENT OF NAVEGADOR | p.11 | no quote on the wire |
| [2] | RULEBOOK Navegador — Rulebook (corpus doc 407) | ABOUT THE DEVELOPMENT OF NAVEGADOR | p.11 | no quote on the wire |
| [3] | RULEBOOK Navegador — Rulebook (corpus doc 407) | Wooden Pieces · Cardboard Pieces · ACTION SELECTION · Example: · AT START | p.4 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 239 ms · first delta 4470 ms · total 40698 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 33104 ms · retrieval 239 ms · ask 7344 ms · gateway work 7594 ms · total 40698 ms
- tokens in (the prompt the answerer read)
- 4177
- tokens out (what the answerer generated)
- 417
- tok/sec
- 135.7 tok/sec — 417 output tokens in 3.073 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 44s 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
- NOT_SETUP_SHAPED — no setup-shape pattern matched this question
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 336), 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.