Ruling — Pax Pamir: Second Edition

← Pax Pamir: Second Edition

You asked

How do I play?

Answered counted as answered

Asked with: Pax Pamir: Second Editionbg-256960-en-1e

Pax Pamir occurs over a series of turns.[1]

**A Turn**

1. The active player performs up to two actions.[1]

2. The player may opt to take only a single action or no action at all.[1]

3. Bonus actions do not count against the two-action limit.[1]

4. To play a card from your hand to your court:

- Reveal the card to everyone and announce its name and region.[2][3]

- If you are the ruler of that region or if no one rules the region, you can freely play the card.[2][3]

- If someone else is the ruler, you must pay them a bribe of rupees equal to the number of the ruler's tribes in that region, unless the ruler waives any portion of the cost.[2][3]

- If the bribe is not paid or waived, play continues as if the action had never been taken.[2][3]

- Add the played card to either the left or right end of your court.[3]

- If the card is a patriot that does not match your loyalty, discard all of your patriots and prizes, remove any gifts, and adjust your loyalty dial to match the patriot.[4][3]

- Resolve each impact icon on the right side of the card from top to bottom.[4][3]

5. To purchase a card from the market:

- Pay the card's cost to the market.[5]

- The cost depends on the card's current column: the leftmost column is free, the next costs one rupee, then two, etc..[5]

- Pay this cost by placing one rupee on each card in the same row to the left of the card being purchased.[5]

- If required to place a rupee on a vacant market spot, pay the cost to the card in the same column in the other market row.[5]

- If you place a rupee on a market card for any reason, you may not purchase that card this turn.[5]

- If military cards are favored, the cost to purchase a card is doubled, and you must place two rupees on each card to the left of the purchased card instead of one.[5]

- If you purchase a card with rupees on it, you receive them along with the card.[5]

- Event cards are resolved the moment they are bought; players should place them below their court, while event cards that alter the general game should be placed near the map.[5]

6. After completing your turn, perform cleanup:[1]

- First, if you have more cards in your court than three plus the sum of the purple stars on cards in your court, discard cards in your court until you are within your limit.[1]

- Second, if you have more cards in your hand than two plus the sum of the blue stars on cards in your court, discard cards in your hand until you are within your limit.[1]

- Third, discard any event cards in the leftmost column of the market (discarding the top row first, then the bottom row); when an event card is discarded, all players are affected by the text or impact icon at the top of the card.[1]

- Fourth, fill empty spaces in the market by moving all cards in that market row (and their rupees) to their leftmost position; if a card moves into a space with rupees from a previously discarded event, those rupees are placed on the new card.[1]

- Draw new cards to fill any empty spaces, starting with the leftmost, to return the market to its normal size, if possible, filling the top row of each empty column first.[1]

7. If a Dominance Check card is revealed while another is already in the market, immediately perform a Dominance Check and then discard both cards and fill the empty spaces as described in cleanup.[1]

8. Play continues clockwise to the next player until the game is over.[1]

[1] RULEBOOK Pax Pamir: Second Edition — Rulebook · p.9 · Sequence of Play · Cleanup

[2] RULEBOOK Pax Pamir: Second Edition — Rulebook · p.11 · Play

[3] RULEBOOK Pax Pamir: Second Edition — Rulebook · p.11

[4] RULEBOOK Pax Pamir: Second Edition — Rulebook · p.11 · No Stacking Limit

[5] RULEBOOK Pax Pamir: Second Edition — Rulebook · p.10 · Core Actions · Purchase

🔧 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 80 ms · ask 7408 ms · total 7490 ms
single-flight (PR-5): queued 0 ms · generation 7490 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 11, "score": 0.048652, "snippet": "Play Play any card from your hand to your court. In order to play a card, first reveal that card to everyone and announce its name and region. If you are the ruler of that card’s region or if no one rules the region, you can freely play the card. If someone else is that region’s ruler, you must pay ", "headingPath": "", "sharpsignalDocId": 266}, {"page": 11, "score": 0.048412, "snippet": "Play any card from your hand to your court. In order to play a card, first reveal that card to everyone and announce its name and region. If you are the ruler of that card's region or if no one rules the region, you can freely play the card. If someone else is that region's ruler, you must pay a bri", "headingPath": "Play", "sharpsignalDocId": 266}, {"page": 8, "score": 0.047123, "snippet": "Players are free to discuss the game during play and explicitly coordinate their actions. However, any agreed-upon deal should be considered non-binding. Cards may never be transferred between players. Money can only be transferred from one player to another if explicitly sanctioned by the rules e.g", "headingPath": "Negotiation · Component Limits · Card Precedence and Special Abilities · Access to Actions · Discarding a Card in Your Court · The Overthrow Rule", "sharpsignalDocId": 266}, {"page": 10, "score": 0.044404, "snippet": "Core Actions The two core actions of Pax Pamir are described in this section. While not difficult, the purchase and play actions are, by far, the most complicated actions of the game. When teaching the game, some groups may prefer to learn just these two actions and then introduce the other actions ", "headingPath": "", "sharpsignalDocId": 266}, {"page": 10, "score": 0.04359, "snippet": "/The two core actions of Pax Pamir are described in this section. While not difficult, the purchase and play actions are, by far, the most complicated actions of the game. When teaching the game, some groups may prefer to learn just these two actions and then introduce the other actions gradually ov", "headingPath": "Core Actions · Purchase", "sharpsignalDocId": 266}, {"page": 9, "score": 0.04311, "snippet": "Pax Pamir occurs over a series of turns. Each turn, the active player performs up to two actions which are described in the following two sections of this rulebook. Bonus actions (page 12) do not count against this limit. You may opt to take only a single action or no action at all. A/fter you have ", "headingPath": "Sequence of Play · Cleanup", "sharpsignalDocId": 266}, {"page": 7, "score": 0.043009, "snippet": "Each of the six regions in the game is associated with a ruler token. Ruler tokens remain on the board if no player currently rules the region. If a player does rule a region, they should immediately take the associated ruler token and place it in their play area. Likewise, if a player ceases ruling", "headingPath": "Ruling a Region 3", "sharpsignalDocId": 266}, {"page": 16, "score": 0.042068, "snippet": "/This section introduces an automated opponent called Wakhan. /Thematically, this opponent represents some radical ideology (theological or philosophical) that has taken hold across the region and that transcends traditional loyalties. Wakhan can be faced by one or two human players. However, this i", "headingPath": "Playing with Wakhan · Setting Up", "sharpsignalDocId": 266}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 9, "quote": null, "headingPath": "Sequence of Play · Cleanup", "sharpsignalDocId": 266}, {"page": 11, "quote": null, "headingPath": "Play", "sharpsignalDocId": 266}, {"page": 11, "quote": null, "headingPath": "", "sharpsignalDocId": 266}, {"page": 11, "quote": null, "headingPath": "No Stacking Limit", "sharpsignalDocId": 266}, {"page": 10, "quote": null, "headingPath": "Core Actions · Purchase", "sharpsignalDocId": 266}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 266 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 266 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.92285 of 2748 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 15, 2026 09:56

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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)		p.11	0.048652 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Play	p.11	0.048412 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Negotiation · Component Limits · Card Precedence and Special Abilities · Access to Actions · Discarding a Card in Your Court · The Overthrow Rule	p.8	0.047123 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)		p.10	0.044404 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Core Actions · Purchase	p.10	0.04359 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Sequence of Play · Cleanup	p.9	0.04311 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Ruling a Region 3	p.7	0.043009 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Playing with Wakhan · Setting Up	p.16	0.042068 (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 51 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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Play	p.11	#2	0.048412 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Sequence of Play · Cleanup	p.9	#6	0.04311 (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
#3	RULEBOOK Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Playing with Wakhan · Setting Up	p.16	#8	0.042068 (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
#4	RULEBOOK Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Core Actions · Purchase	p.10	#5	0.04359 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	No Stacking Limit	p.11	#24	0.023611 (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 re-ranker chose it
#6	RULEBOOK Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Ruling a Region 3	p.7	#7	0.043009 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Wakhan's Core Action	p.17	#14	0.027651 (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 re-ranker chose it
#8	RULEBOOK Pax Pamir: Second Edition — Rulebook (corpus doc 266)		p.11	#1	0.048652 (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 Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Sequence of Play · Cleanup	p.9	no quote on the wire
[2]	RULEBOOK Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Play	p.11	no quote on the wire
[3]	RULEBOOK Pax Pamir: Second Edition — Rulebook (corpus doc 266)		p.11	no quote on the wire
[4]	RULEBOOK Pax Pamir: Second Edition — Rulebook (corpus doc 266)	No Stacking Limit	p.11	no quote on the wire
[5]	RULEBOOK Pax Pamir: Second Edition — Rulebook (corpus doc 266)	Core Actions · Purchase	p.10	no quote on the wire

generation — timing and the path taken

timing split: retrieval 80 ms · first delta 3293 ms · total 7490 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 80 ms · ask 7408 ms · gateway work 7490 ms · total 7490 ms
tokens in (the prompt the answerer read): 2913
tokens out (what the answerer generated): 855
tok/sec: 206.0 tok/sec — 855 output tokens in 4.150 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 19s 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 194), 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.