Ruling — Imhotep

You asked

What is the difference between the A and B sides of the site boards?

Answered counted as answered

Asked with: Imhotepbg-191862-en-1e

The differences between the A and B sides of the site boards depend on the specific site:

* **Market**: At the start of the round, instead of 1 face-up card, 2 cards are placed face down on the bottom right card space.[1] For a stone delivered to the market, you can pick up both cards and look at them, then select 1 card to keep and place the other face up on the discard pile.[1]

* **Pyramids**: The owner of a stone delivered to the pyramids decides which of the 3 pyramids the stone is delivered to.[1] Some pyramids yield special bonuses:

* 1 point and the ability to take the top market card from the draw pile.[1]

* 1 point and the ability to immediately take 3 stones from the quarry and place them on the supply sled token.[1]

* 1 point and the ability to place 1 stone from your supply sled token on any empty space of a ship that has not yet sailed to a site.[1]

Additionally, each pyramid is started from the top left, stones are placed column by column, stones in the second level are worth 4 points, and once completed, each additional stone delivered yields 1 point (placed at the right edge of the board).[1]

* **Temple**: At the end of each round, there are various bonuses for each stone visible from above depending on the temple space where the stone is placed.[1]

* **Obelisks**: Each stone delivered is first placed on a space with its corresponding color.[2] When the third stone of any given color is delivered, those stones are immediately assessed and stacked in a single tower on the free space with the highest point value, and the owner receives those points.[2] Individual stones that do not make it into an obelisk earn 1 point each at the end of the game.[2]

[1] RULEBOOK Imhotep — Rulebook · p.9 · THE B SIDES OF THE SITES · B) Market · B) Pyramids · B) Temple

[2] RULEBOOK Imhotep — Rulebook · p.10 · B) Obelisks

🔧 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 79 ms · ask 4703 ms · total 4784 ms
single-flight (PR-5): queued 0 ms · generation 4784 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 9, "score": 0.04918, "snippet": "All site boards have an A side and a B side . You should always start playing with just the A sides. Later on, you can try the B sides. You can also play with a mix of A and B sides . Why not try various combinations? The B side works just like the A side, except for the following difference: At the", "headingPath": "THE B SIDES OF THE SITES · B) Market · B) Pyramids · B) Temple", "sharpsignalDocId": 633}, {"page": 3, "score": 0.032258, "snippet": "Place the 5 site boards in the center of the table as shown in the illustration. All site boards have an A side and a B side . In your first few games, use the A side. You can use the B sides in later games as a variant to the standard game play. So be sure that the A sides of the boards are showing", "headingPath": "GAME PREPARATION", "sharpsignalDocId": 633}, {"page": 10, "score": 0.031746, "snippet": "The B side works just like the A side, except for the following differences: Each stone delivered here is first placed on a space with the corresponding color . When the third stone of any given color is delivered, these stones immediately have their value assessed. The 3 stones are stacked in a sin", "headingPath": "B) Obelisks", "sharpsignalDocId": 633}, {"page": 4, "score": 0.03125, "snippet": "Slide 1 ship to a site board . You must observe 2 conditions, however: The ship must already be loaded with at least the minimum required number of stones . The gray stone symbols at the bow of the ship indicate the minimum number for that ship. This number varies from ship to ship. The site to whic", "headingPath": "Sail 1 ship to a site", "sharpsignalDocId": 633}, {"page": 10, "score": 0.030769, "snippet": "You get 1 point or, if you prefer, you can take 2 stones from the quarry and place them on your supply sled token . You get 2 points . You get the top market card from the draw pile . Example: The point assessment for the temple is performed at the end of the round. The gray player can decide whethe", "headingPath": "B) Temple · B) Burial Chamber · Important:", "sharpsignalDocId": 633}, {"page": 5, "score": 0.030303, "snippet": "At each of the 5 sites, there are different rules for what the stone's owner will receive for each stone delivered, and when they will receive it. The market and the pyramid are assessed immediately . The temple is assessed at the end of each round . The burial chamber and the obelisks are not asses", "headingPath": "Sail 1 ship to a site · Play 1 blue market card · END OF ROUND", "sharpsignalDocId": 633}, {"page": 7, "score": 0.029851, "snippet": "For each stone delivered here, the owner of the stone earns points at the end of the round if the stone is visible from above. Place the stone on the next free space in the temple. Placement of the stones begins from the left, until the first level is full. With 3 and 4 players, all 5 spaces of the ", "headingPath": "A) Temple · A) Burial Chamber", "sharpsignalDocId": 633}, {"page": 7, "score": 0.029412, "snippet": "For each stone delivered here, the owner of the stone can immediately take any 1 face-up market card . Explanations of the various market cards can be found on page 12 of this manual. Important: The delivered stones must be returned to the quarry after taking the card. Drawn cards must be placed fac", "headingPath": "A) Market · A) Pyramids", "sharpsignalDocId": 633}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 9, "quote": null, "headingPath": "THE B SIDES OF THE SITES · B) Market · B) Pyramids · B) Temple", "sharpsignalDocId": 633}, {"page": 10, "quote": null, "headingPath": "B) Obelisks", "sharpsignalDocId": 633}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 633 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 633 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.92759 of 1381 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 13, 2026 12:20

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 Imhotep — Rulebook (corpus doc 633)	THE B SIDES OF THE SITES · B) Market · B) Pyramids · B) Temple	p.9	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Imhotep — Rulebook (corpus doc 633)	GAME PREPARATION	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 Imhotep — Rulebook (corpus doc 633)	B) Obelisks	p.10	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 Imhotep — Rulebook (corpus doc 633)	Sail 1 ship to a site	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
#5	RULEBOOK Imhotep — Rulebook (corpus doc 633)	B) Temple · B) Burial Chamber · Important:	p.10	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 Imhotep — Rulebook (corpus doc 633)	Sail 1 ship to a site · Play 1 blue market card · END OF ROUND	p.5	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 Imhotep — Rulebook (corpus doc 633)	A) Temple · A) Burial Chamber	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 Imhotep — Rulebook (corpus doc 633)	A) Market · A) Pyramids	p.7	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 20 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 Imhotep — Rulebook (corpus doc 633)	THE B SIDES OF THE SITES · B) Market · B) Pyramids · B) Temple	p.9	#1	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Imhotep — Rulebook (corpus doc 633)	B) Obelisks	p.10	#3	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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Imhotep — Rulebook (corpus doc 633)	Sail 1 ship to a site	p.4	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Imhotep — Rulebook (corpus doc 633)	Prepare FOR THE NEXT ROUND · END OF GAME · Final point assessment (scoring) · Obelisks' heading . · The player with the most points is the winner .	p.5	#13	0.013699 (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
#5	RULEBOOK Imhotep — Rulebook (corpus doc 633)	COURSE OF PLAY · COURSE OF A ROUND · TURN · Get new stones · Place 1 stone on a ship	p.4	#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
#6	RULEBOOK Imhotep — Rulebook (corpus doc 633)	B) Obelisks · Variant: WRATH OF THE PHARAOH	p.11	#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
#7	RULEBOOK Imhotep — Rulebook (corpus doc 633)	Sail 1 ship to a site · Play 1 blue market card · END OF ROUND	p.5	#6	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))	vector + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Imhotep — Rulebook (corpus doc 633)	GAME PREPARATION	p.3	#2	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))	vector + the doc-priority boost arm	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Imhotep — Rulebook (corpus doc 633)	THE B SIDES OF THE SITES · B) Market · B) Pyramids · B) Temple	p.9	no quote on the wire
[2]	RULEBOOK Imhotep — Rulebook (corpus doc 633)	B) Obelisks	p.10	no quote on the wire

generation — timing and the path taken

timing split: retrieval 79 ms · first delta 1842 ms · total 4784 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 79 ms · ask 4703 ms · gateway work 4784 ms · total 4784 ms
tokens in (the prompt the answerer read): 3081
tokens out (what the answerer generated): 404
tok/sec: 139.5 tok/sec — 404 output tokens in 2.897 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 25s 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 566), 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.