Ruling — Metropolys

You asked

How do I play?

Answered counted as answered

Asked with: Metropolysbg-25568-en-1e

The game is divided into turns.[1] The sequence of play is as follows:

1. The first player chooses one of their buildings, of any value, and places it in an unoccupied neighborhood, ensuring the building number is visible.[1]

2. Playing clockwise, players may either Outbid or Pass.[1]

3. To outbid, a player must place one of their buildings of a higher value than the previous one in an adjacent, unoccupied neighborhood.[1] Crossing bridges is allowed, but lakes and rivers are impassable.[1]

4. A player who passes may not place another building during that specific call for proposal, though buildings they have already placed stay on the board until the end of the call.[1]

5. A player must pass if they have no buildings left or no buildings with sufficient value.[1]

6. The call for proposal ends when all players but one have passed, no one can place buildings because the last building has no adjacent unoccupied neighborhood, or no one can outbid the latest bid.[2]

7. The player who placed the last building wins the call, turns that building on to its face with no number, and takes any token in that neighborhood.[2]

8. All players receive their unbuilt buildings (those with a visible number) back, and buildings used during the call (other than the winning building) are removed from the board.[2]

9. The winner of the call becomes the first player and starts a new turn.[2]

The game ends as soon as one player places their last building.[1][3]

[1] RULEBOOK Metropolys — Rulebook · p.2 · PLAYING THE GAME · CALL FOR PROPOSAL · 1) Outbidding · 2) Passing

[2] RULEBOOK Metropolys — Rulebook · p.2 · END OF THE CALL FOR PROPOSAL

[3] RULEBOOK Metropolys — Rulebook · p.4 · END OF THE GAME

Rule found, game on.

🔧 debug — where this ruling came from

outcome: ANSWERED — Answered
corpus profile: live,vps
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 107 ms · ask 2809 ms · total 2918 ms
single-flight (PR-5): queued 0 ms · generation 2918 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 2, "score": 0.048387, "snippet": "The game is divided into turns . Each turn represents a call for proposal from Metropolys, at the end of which exactly one building is constructed . The game goes on until one of the players places their last building . The first player chooses one of their buildings, of any value, and places it in ", "headingPath": "PLAYING THE GAME · CALL FOR PROPOSAL · 1) Outbidding · 2) Passing", "sharpsignalDocId": 1133}, {"page": 1, "score": 0.047938, "snippet": "NB: These rules are for 4-player games. Adjustments concerning the number of players will be explained at the end of the rules. Before starting your first game, please read the 'Welcome' player aid. Place the board at the center of the table. For your first game, lay out the neighbourhood tokens as ", "headingPath": "SETUP", "sharpsignalDocId": 1133}, {"page": 4, "score": 0.047619, "snippet": "The progress of the game is strictly the same as in the 4-player version, however the play area is smaller and less neighborhood tokens are used: In 3-player games, one of the peripheral districts is not used. The players will not be able to place buildings in it. Remove 2 'Subway' tokens from the g", "headingPath": "2 AND 3-PLAYER GAMES · ACKNOWLEDGEMENTS", "sharpsignalDocId": 1133}, {"page": 3, "score": 0.046696, "snippet": "A player who builds in a neighborhood containing a token earns it. Collected tokens will yield or cost prestige points at the end of the game. Trendy neighborhoods: these tokens mark the location of a trendy neighborhood. Urban planners who place a building in such a neighborhood are assured to earn", "headingPath": "TOKENS · SPECIAL CARDS · IMPORTANT ADVICE", "sharpsignalDocId": 1133}, {"page": 1, "score": 0.046154, "snippet": "Game design by Sébastien Pauchon - Illustrations by Mathieu Leyssenne - Layout by Cyril Demaegd FAQ & forum: http://www.ystari.com To make the game more enjoyable, two versions of Metropolys are included in these rules: Family and Expert . These versions should not be considered as mere variants, bu", "headingPath": "TWO GAMES IN ONE · CONTENTS · FAMILL E · EXPERT · ONCE UPON A TIME… · GOAL OF THE GAME", "sharpsignalDocId": 1133}, {"page": 3, "score": 0.045476, "snippet": "The game ends as soon as a player has placed their last building. Then the players reveal their secret cards and count their points: For each 'Trendy neighborhood' token a player owns, they earn 3 prestige points , For each 'Subway' token a player owns, they earn 1 prestige point , The owner of the ", "headingPath": "END OF THE GAME", "sharpsignalDocId": 1133}, {"page": 4, "score": 0.03125, "snippet": "The progress of the Expert game is basically the same as in the Family version. However, the players must take into account additional objectives that yield points at the end of the game. The highest building: in this version, the players use the size of buildings . Indeed, each player has 5 small b", "headingPath": "EXPERT GAME · SETUP", "sharpsignalDocId": 1133}, {"page": 4, "score": 0.029412, "snippet": "The game ends as soon as a player has placed their last building . Then the players reveal their secret cards and count their points: In each district, the player who has constructed the highest building (in terms of size, not value) gets a 'Highest building' token which yields 5 prestige points . I", "headingPath": "END OF THE GAME", "sharpsignalDocId": 1133}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "PLAYING THE GAME · CALL FOR PROPOSAL · 1) Outbidding · 2) Passing", "sharpsignalDocId": 1133}, {"page": 2, "quote": null, "headingPath": "END OF THE CALL FOR PROPOSAL", "sharpsignalDocId": 1133}, {"page": 4, "quote": null, "headingPath": "END OF THE GAME", "sharpsignalDocId": 1133}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 1133 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1133 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)
answer fence: passed — letter density 0.92822 of 1212 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 27, 2026 15:15 UTC

retrieval — what the passage search returned

what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.

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 Metropolys — Rulebook (corpus doc 1133)	PLAYING THE GAME · CALL FOR PROPOSAL · 1) Outbidding · 2) Passing	p.2	0.048387 (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 Metropolys — Rulebook (corpus doc 1133)	SETUP	p.1	0.047938 (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 Metropolys — Rulebook (corpus doc 1133)	2 AND 3-PLAYER GAMES · ACKNOWLEDGEMENTS	p.4	0.047619 (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 Metropolys — Rulebook (corpus doc 1133)	TOKENS · SPECIAL CARDS · IMPORTANT ADVICE	p.3	0.046696 (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 Metropolys — Rulebook (corpus doc 1133)	TWO GAMES IN ONE · CONTENTS · FAMILL E · EXPERT · ONCE UPON A TIME… · GOAL OF THE GAME	p.1	0.046154 (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 Metropolys — Rulebook (corpus doc 1133)	END OF THE GAME	p.3	0.045476 (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 Metropolys — Rulebook (corpus doc 1133)	EXPERT GAME · SETUP	p.4	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
#8	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	END OF THE GAME	p.4	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

what the answerer read — the passages it actually had in front of it

what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.

candidate pool: the answering read scored 11 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.

floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.

arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.

read at	document	heading	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	PLAYING THE GAME · CALL FOR PROPOSAL · 1) Outbidding · 2) Passing	p.2	#1	0.048387 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	EXPERT GAME · SETUP	p.4	#7	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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	END OF THE CALL FOR PROPOSAL	p.2	#9	0.014493 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#4	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	2 AND 3-PLAYER GAMES · ACKNOWLEDGEMENTS	p.4	#3	0.047619 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	NEIGHBORHOODS · AREAS	p.6	#11	0.014085 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#6	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	TOKENS · SPECIAL CARDS · IMPORTANT ADVICE	p.3	#4	0.046696 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	END OF THE GAME	p.4	#8	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))	vector + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	SETUP	p.1	#2	0.047938 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	PLAYING THE GAME · CALL FOR PROPOSAL · 1) Outbidding · 2) Passing	p.2	no quote on the wire
[2]	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	END OF THE CALL FOR PROPOSAL	p.2	no quote on the wire
[3]	RULEBOOK Metropolys — Rulebook (corpus doc 1133)	END OF THE GAME	p.4	no quote on the wire

generation — timing and the path taken

timing split: retrieval 107 ms · first delta 1214 ms · total 2918 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 0 ms · retrieval 107 ms · ask 2809 ms · gateway work 2918 ms · total 2918 ms
tokens in (the prompt the answerer read): 2938
tokens out (what the answerer generated): 331
tok/sec: 202.0 tok/sec — 331 output tokens in 1.639 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 59s ago)
gateway schema (read from the running child): schema head 0042_definer_search_path (live revision not readable by this principal)
answerer host (measured by rulesage): reachable (for 60h, checked 5s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
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 1063), 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.