Ruling — Android: Netrunner

You asked

How do I take my turn?

Answered counted as answered

Asked with: Android: Netrunnerbg-124742-en-1e

The rules for taking a turn depend on whether you are playing as the Corporation or the Runner. Players alternate turns, beginning with the Corporation.[1][2]

**Corporation's Turn**

The Corporation's turn consists of three phases performed in the following order:

1. Draw Phase: The Corporation draws one card from R&D.[1]

2. Action Phase: The Corporation uses three clicks to perform actions.[1][2] A player can only spend clicks during their Action phase and must spend all of them.[1]

3. Discard Phase: The Corporation discards down to his maximum hand size, if necessary.[1]

**Runner's Turn**

The Runner's turn consists of two phases performed in the following order:

1. Action Phase: The Runner uses four clicks to perform actions.[3] A player can only take actions during their Action phase and must spend all four clicks during that phase.[3] Possible actions include:

* Drawing one card from the stack.[3]

* Gaining 1 credit.[3]

* Installing a program, resource, or piece of hardware.[3]

* Playing an event.[3]

* Removing one tag (costing 2 clicks).[3]

* Making a run.[3]

When the Runner spends clicks on an action, they cannot take another action until the current action fully resolves.[3]

2. Discard Phase: The Runner discards down to his maximum hand size, if necessary.[3]

**General Turn Rules**

* **Timing of Abilities:** Whenever there is an opportunity to trigger paid abilities, rez cards, and/or score agendas (usually at the beginning of a turn and after each action), the player currently taking their turn gets the first opportunity to act.[4] The player can trigger as many abilities, rez as many cards, and/or score as many agendas as they wish in any order of their choosing.[4]

* **Sequence of Play:** After the active player finishes, the other player gets the opportunity to act.[4] When that player is finished, the first player gets the opportunity to act once again.[4] Once both players have had at least one opportunity to act and a player declines to act, no more abilities can be triggered, cards rezzed, or agendas scored until the next opportunity.[4]

[1] RULEBOOK Android: Netrunner — Rulebook · p.12 · Playing the Game · Turn Overview · Corporation's Turn · Rezzed and Unrezzed Cards · 1. Draw Phase

[2] RULEBOOK Android: Netrunner — Rulebook · p.3 · Game Overview · Object of the Game · Corporate Factions · Runner Factions · Neutral Cards

[3] RULEBOOK Android: Netrunner — Rulebook · p.15 · Runner's Turn · 1. Action Phase · Drawing One Card · Gaining One Credit

[4] RULEBOOK Android: Netrunner — Rulebook · p.21 · Timing Priority · Prevent or Avoid · Self-referential Language · Negative Effects

🔧 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 345 ms · ask 17622 ms · total 17980 ms
single-flight (PR-5): queued 0 ms · generation 17980 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 12, "score": 0.048139, "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": 32, "score": 0.047883, "snippet": "= Paid abilities can be triggered Corporation's Draw Phase Turn begins ('When your turn begins' conditionals meet their trigger conditions) Draw one card Take actions After each action: Phase ends after abilities are triggered following the last spent action Discard down to maximum hand size End of ", "headingPath": "TIMING STRUCTURE OF TURNS · 2. Corporation's Action Phase · 3. Corporation's Discard Phase · 1. Runner's Action Phase · 2. Runner's Discard Phase", "sharpsignalDocId": 279}, {"page": 15, "score": 0.047493, "snippet": "The Runner's turn is divided into two phases, which he performs in the following order: Action Phase: The Runner has [ [ [ [ with which to perform actions. Discard Phase: The Runner discards down to his maximum hand size, if necessary. In his Action phase, the Runner takes actions by spending [ [ [ ", "headingPath": "Runner's Turn · 1. Action Phase · Drawing One Card · Gaining One Credit", "sharpsignalDocId": 279}, {"page": 12, "score": 0.03125, "snippet": "In his Action phase, the Corporation takes actions by spending [ [ [ . He can only take actions during his Action phase, and he must spend all three of his clicks during his Action phase. The Corporation can perform any of the following actions as many times as he likes, and in any combination, prov", "headingPath": "2. Action Phase", "sharpsignalDocId": 279}, {"page": 18, "score": 0.030769, "snippet": "When accessing multiple cards, the Runner accesses them one at a time in any order he likes. For example, the Runner may access a card from HQ, then an upgrade installed in the root of HQ, and then another card from HQ, if he has the ability to do so. When accessing multiple cards from R&D, the Runn", "headingPath": "Accessing Multiple Cards · Concluding the Run", "sharpsignalDocId": 279}, {"page": 15, "score": 0.030303, "snippet": "The Runner begins the game with a maximum hand size of five cards, but card effects can increase or decrease this limit (see 'Brain Damage' on page 20). If the cards in the Runner's grip exceed his current maximum hand size at the beginning of the Discard phase, he must discard down to his maximum h", "headingPath": "2. Discard Phase", "sharpsignalDocId": 279}, {"page": 18, "score": 0.029851, "snippet": "After the Runner has passed all of the ice protecting the attacked server, he has one final opportunity to jack out. If he chooses to continue, the Corporation has one final opportunity to rez cards. After rezzing cards, the run is considered to be successful and the Runner accesses the Corporation'", "headingPath": "3. Access Phase · Stealing Agendas · Trashing Cards", "sharpsignalDocId": 279}, {"page": 5, "score": 0.029412, "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}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 12, "quote": null, "headingPath": "Playing the Game · Turn Overview · Corporation's Turn · Rezzed and Unrezzed Cards · 1. Draw Phase", "sharpsignalDocId": 279}, {"page": 3, "quote": null, "headingPath": "Game Overview · Object of the Game · Corporate Factions · Runner Factions · Neutral Cards", "sharpsignalDocId": 279}, {"page": 15, "quote": null, "headingPath": "Runner's Turn · 1. Action Phase · Drawing One Card · Gaining One Credit", "sharpsignalDocId": 279}, {"page": 21, "quote": null, "headingPath": "Timing Priority · Prevent or Avoid · Self-referential Language · Negative Effects", "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 8, 2026 10:00

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. How much wider that pool was is set gateway-side and is NOT REPORTED for this ruling, and neither are the answerer's final rows — so rulesage has nothing of its own to show beside these.

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)	Playing the Game · Turn Overview · Corporation's Turn · Rezzed and Unrezzed Cards · 1. Draw Phase	p.12	0.048139 (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)	TIMING STRUCTURE OF TURNS · 2. Corporation's Action Phase · 3. Corporation's Discard Phase · 1. Runner's Action Phase · 2. Runner's Discard Phase	p.32	0.047883 (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)	Runner's Turn · 1. Action Phase · Drawing One Card · Gaining One Credit	p.15	0.047493 (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)	2. Action Phase	p.12	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)	Accessing Multiple Cards · Concluding the Run	p.18	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)	2. Discard Phase	p.15	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)	3. Access Phase · Stealing Agendas · Trashing Cards	p.18	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 Android: Netrunner — Rulebook (corpus doc 279)	Setup · The Golden Rule · Starter Decks · Corporation: · Runner:	p.5	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.

the passages the answerer read: NOT RECORDED for this ruling. Any of three things leaves this empty, and they are all different from the answerer having had nothing to read: this ask may never have reached a gateway at all; a multi-book ask keeps each book's own context on that book's own page rather than here; or the gateway build that answered may simply not report it. What this NEVER means is that the answerer read nothing — an answer was composed from passages either way, and their absence here is a gap in what we were told, not in what it read.

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Android: Netrunner — Rulebook (corpus doc 279)	Playing the Game · Turn Overview · Corporation's Turn · Rezzed and Unrezzed Cards · 1. Draw Phase	p.12	no quote on the wire
[2]	RULEBOOK Android: Netrunner — Rulebook (corpus doc 279)	Game Overview · Object of the Game · Corporate Factions · Runner Factions · Neutral Cards	p.3	no quote on the wire
[3]	RULEBOOK Android: Netrunner — Rulebook (corpus doc 279)	Runner's Turn · 1. Action Phase · Drawing One Card · Gaining One Credit	p.15	no quote on the wire
[4]	RULEBOOK Android: Netrunner — Rulebook (corpus doc 279)	Timing Priority · Prevent or Avoid · Self-referential Language · Negative Effects	p.21	no quote on the wire

generation — timing and the path taken

timing split: retrieval 345 ms · first delta 14494 ms · total 17980 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 345 ms · ask 17622 ms · gateway work 17980 ms · total 17980 ms
tokens in (the prompt the answerer read): 3488
tokens out (what the answerer generated): 498
tok/sec: 146.8 tok/sec — 498 output tokens in 3.392 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 41s 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 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.