You asked
How do I set up the game?
Answered counted as answeredAsked with: Android: Netrunnerbg-124742-en-1e
To prepare a game of Android: Netrunner, follow these steps: 1. Choose Sides: Players decide who will play as the Runner and who will play as the Corporation [1]. 2. Place Identity Cards: Each player places his identity card faceup in his play area and takes a corresponding deck [1]. 3. Create Token Bank: Gather the credits, advancement, brain damage, tag, bad publicity, and generic tokens into piles within reach of both players [1]. 4. Collect Starting Credits: Each player takes five credits from the bank [1]. 5. Shuffle Decks: Each player shuffles his deck, then offers his deck to his opponent for further shuffling [1]. 6. Draw Starting Hands: Each player draws five cards from the top of his deck to form a starting hand [1]. 7. Mulligan (Optional): The Corporation may choose to shuffle his hand back into his deck and draw a new starting hand; after the Corporation decides, the Runner may also decide whether to mulligan [1]. If a player takes a mulligan, he must keep the second hand as his starting hand [1]. 8. Place Decks: When players are satisfied with their hands, each player places his deck facedown in his play area [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 283 ms · ask 18438 ms · total 896762 ms
- single-flight (PR-5)
- queued 878030 ms · generation 18732 ms
- retrieval refs (raw)
- [{"page": 5, "score": 0.048412, "snippet": "To prepare a game of Android: Netrunner , carefully follow the steps below. Choose Sides: The players decide who will play as the Runner and who will play as the Corporation. Then, each player places his identity card faceup in his play area and takes a corresponding deck. Note: New players should u", "headingPath": "Setup · The Golden Rule · Starter Decks · Corporation: · Runner:", "sharpsignalDocId": 279}, {"page": 15, "score": 0.032258, "snippet": "For [ , the Runner installs a single program, resource, or piece of hardware faceup in his rig. An installed Runner card is active and does not have to be rezzed like a Corporation card. Note: The Runner's cards are always installed faceup and in a vertical orientation. ProgramsTo install a program,", "headingPath": "Installing Cards · Playing Events · Removing Tags · Making a Run · Triggering [ Abilities", "sharpsignalDocId": 279}, {"page": 13, "score": 0.031746, "snippet": "For [ , the Corporation installs a single agenda, asset, upgrade, or piece of ice from HQ, placing it facedown on the table. Note: When an asset or upgrade is installed, the Corporation can pay its rez cost to rez it at almost any time (see the 'Timing Structures' on pages 32-33). Ice can only be re", "headingPath": "Installing Cards", "sharpsignalDocId": 279}, {"page": 6, "score": 0.03125, "snippet": "Each player has a click tracker that he uses to track the number of clicks left that he has to spend on his turn. This is a game aid only and its use is optional. Some cards enter Archives faceup, and some cards enter Archives facedown. Facedown cards in Archives should be oriented horizontally so t", "headingPath": "Click Tracker · Remote Servers · Ice · Heap · Rig", "sharpsignalDocId": 279}, {"page": 12, "score": 0.030769, "snippet": "In Android: Netrunner, the Corporation and the Runner alternate taking turns. Android: Netrunner is unusual in that the Runner and the Corporation are governed by different rules. Players should familiarize themselves with the rules for both sides. The Corporation always takes the first turn of the ", "headingPath": "Playing the Game · Turn Overview · Corporation's Turn · Rezzed and Unrezzed Cards · 1. Draw Phase", "sharpsignalDocId": 279}, {"page": 13, "score": 0.030303, "snippet": "If the Corporation wants to install an agenda in a remote server that has an asset or an agenda already installed in it, he can install the card but must trash the existing card first as part of the install action. UpgradesAn upgrade can be installed in any server. When an upgrade is installed in a ", "headingPath": "Installing Cards", "sharpsignalDocId": 279}, {"page": 24, "score": 0.029851, "snippet": "In a Living Card Game, players can customize their decks by adding and removing cards, creating a unique play experience.", "headingPath": "Deckbuilding", "sharpsignalDocId": 279}, {"page": 24, "score": 0.029469, "snippet": "Deckbuilding is a great way to experience the game in a completely new way. Instead of adapting to the game, you can force the game to adapt to you. Deckbuilding opens up new strategies, new experiences, and ultimately can lead to more exciting games where you feel more invested. When you deckbuild,", "headingPath": "Why deckbuild?", "sharpsignalDocId": 279}]
- citations (raw)
- [{"page": 5, "quote": null, "headingPath": "Setup · The Golden Rule · Starter Decks · Corporation: · Runner:", "sharpsignalDocId": 279}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 279 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 279 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:23
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 Android: Netrunner — Rulebook (corpus doc 279) | Setup · The Golden Rule · Starter Decks · Corporation: · Runner: | p.5 | 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 |
| #2 | RULEBOOK Android: Netrunner — Rulebook (corpus doc 279) | Installing Cards · Playing Events · Removing Tags · Making a Run · Triggering [ Abilities | p.15 | 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 Android: Netrunner — Rulebook (corpus doc 279) | Installing Cards | p.13 | 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 Android: Netrunner — Rulebook (corpus doc 279) | Click Tracker · Remote Servers · Ice · Heap · Rig | p.6 | 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 Android: Netrunner — Rulebook (corpus doc 279) | Playing the Game · Turn Overview · Corporation's Turn · Rezzed and Unrezzed Cards · 1. Draw Phase | p.12 | 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 Android: Netrunner — Rulebook (corpus doc 279) | Installing Cards | p.13 | 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 Android: Netrunner — Rulebook (corpus doc 279) | Deckbuilding | p.24 | 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)) | 121 |
| #8 | RULEBOOK Android: Netrunner — Rulebook (corpus doc 279) | Why deckbuild? | p.24 | 0.029469 (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 Android: Netrunner — Rulebook (corpus doc 279) | Setup · The Golden Rule · Starter Decks · Corporation: · Runner: | p.5 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 283 ms · first delta 16738 ms · total 896762 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 878030 ms · retrieval 283 ms · ask 18438 ms · gateway work 18732 ms · total 896762 ms
- tokens in (the prompt the answerer read)
- 3377
- tokens out (what the answerer generated)
- 264
- tok/sec
- 135.4 tok/sec — 264 output tokens in 1.950 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 1s 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 207), 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.