Ruling — Anachrony

← Anachrony

You asked

How does a Blink action work — what do I spend and which dice do I roll?

Answered counted as answered

Asked with: Anachronybg-185343-en-1e · Anachrony: Fractures of Timebg-272077-en-1e

To perform a Blink action, follow these steps:

1. Move 1 Flux Core from your supply to the leftmost empty space of your Fracture Device.[1]

2. Choose an already-placed Exosuit on the Main board that contains a Worker you wish to move.[1]

3. If the Worker in the Exosuit is not an Operator, roll both the Flux and the Glitch dice.[1]

4. If the Flux die's number is greater than the number of visible empty spaces on your Fracture Device, place 1 Glitch marker on the location shown on the Glitch die; if the Endgame Conditions die face is rolled, place 1 Glitch marker on 2 different Endgame Conditions.[1] (Note: Skip this step if Blinking with an Operator [2]).

5. Move the chosen Exosuit to a different space belonging to a different Action and activate that Action as usual.[2][1]

6. After activating the Action, take the Worker out of the Exosuit and retrieve it as you normally would in the Clean Up Phase.[2]

[1] RULEBOOK Anachrony: Fractures of Time — Rulebook · p.7 · BLINKING

[2] RULEBOOK Anachrony: Fractures of Time — Rulebook · p.8 · BLINKING · SUMMARY OF A BLINK ACTION: · CHANGE IN THE MINE RESOURCE ACTION

🔧 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 5664 ms · total 5744 ms
single-flight (PR-5): queued 0 ms · generation 5744 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 12, "score": 0.032018, "snippet": "Before resolving a potential Impact, roll the two Trajectory dice , then count the total number of (-) and (+) symbols on the Trajectory die roll's result; next to the Doomsday track slots where the 'Save Earth' and 'Seal Fate' Trackers currently are. Three things can happen based on the result: If ", "headingPath": "B) CHECK FOR IMPACT · OPTIONAL RULE - PLANNED EXPERIMENTS", "sharpsignalDocId": 270}, {"page": 9, "score": 0.031514, "snippet": "All spaces on the Player boards are either Worker spaces or Free Actions - Exosuits are not needed to activate them. The Supply Action is printed on every Player board between the Active and Tired columns. Spend Water equal to the number printed on the Water symbol below your current position on the", "headingPath": "PLAYER BOARD ACTIONS · Worker specifics · FORCE WORKERS", "sharpsignalDocId": 270}, {"page": 6, "score": 0.031025, "snippet": "Each player secretly hides 0-2 Warp tiles in their hand (hide the other Warp tiles to maintain secrecy). Reveal them simultaneously and place them on the present Timeline tile (the order is not important). In player order, each Player immediately receives any asset shown on the selected Warp tile(s)", "headingPath": "WARP PHASE 4 · ACTION ROUNDS 5 · IMPORTANT: Free Actions", "sharpsignalDocId": 270}, {"page": 11, "score": 0.03055, "snippet": "After flipping the Superproject above the following Era's Timeline tile, also flip the face-down Level 1 Experiment card below it. Then, place a face-up Level 2 Experiment card from the top of the stack below each Timeline with no Experiment card below it. Example: NEW ACTION - EXPERIMENT The Doomsd", "headingPath": "PREPARATION PHASE - CHANGES 1 · Worker specifics", "sharpsignalDocId": 270}, {"page": 4, "score": 0.03009, "snippet": "Each player picks a Path to play, and receives its respective Player board . Players may choose whether they use the A side or B side - all players must use the same side. Give players the coloured components matching their Path color ( 6 Exosuits, 9 Warp tiles, 8 Path markers and the Morale and Tim", "headingPath": "PLAYER SETUP", "sharpsignalDocId": 270}, {"page": 10, "score": 0.029644, "snippet": "Geniuses may be used as any kind of Worker when placed on Action spaces, but they may NOT be spent as another kind of Worker, or sent back in time to remove a Worker Warp tile. Whenever paying a Worker cost of an Action (typically when building Superprojects), the Worker can be spent from either the", "headingPath": "FREQUENTLY OVERLOOKED RULES", "sharpsignalDocId": 270}, {"page": 6, "score": 0.02901, "snippet": "Retrieve every Worker from every Exosuit on the Main board and all Workers placed on the Player boards' Worker spaces. If the Action was marked Motivated, place the Worker in its owner's Active column (to the right of the Supply Action space); otherwise place it in the Tired column (to the left of t", "headingPath": "A) RETRIEVE WORKERS · B) CHECK FOR IMPACT · C) CHECK FOR GAME END · D) NEXT ERA · ACTIONS", "sharpsignalDocId": 270}, {"page": 13, "score": 0.028595, "snippet": "4 4 6 5 The Chronobot doesn't use Workers to take Main board Actions, only empty Exosuits. 1 1 It never pays costs of Actions and ignores everything printed on the Action spaces and Collapsing Capital tiles. It always picks the topmost available space on Capital Actions. 2 1 2 If there are no availa", "headingPath": "ACTION ROUNDS PHASE 5 · General rules of the Chronobot's Actions: · Construct", "sharpsignalDocId": 270}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 7, "quote": null, "headingPath": "BLINKING", "sharpsignalDocId": 869}, {"page": 8, "quote": null, "headingPath": "BLINKING · SUMMARY OF A BLINK ACTION: · CHANGE IN THE MINE RESOURCE ACTION", "sharpsignalDocId": 869}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 270 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 270 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.92154 of 752 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 12, 2026 20:48

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 Anachrony — Rulebook (corpus doc 270)	B) CHECK FOR IMPACT · OPTIONAL RULE - PLANNED EXPERIMENTS	p.12	0.032018 (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 Anachrony — Rulebook (corpus doc 270)	PLAYER BOARD ACTIONS · Worker specifics · FORCE WORKERS	p.9	0.031514 (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 Anachrony — Rulebook (corpus doc 270)	WARP PHASE 4 · ACTION ROUNDS 5 · IMPORTANT: Free Actions	p.6	0.031025 (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 Anachrony — Rulebook (corpus doc 270)	PREPARATION PHASE - CHANGES 1 · Worker specifics	p.11	0.03055 (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 Anachrony — Rulebook (corpus doc 270)	PLAYER SETUP	p.4	0.03009 (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 Anachrony — Rulebook (corpus doc 270)	FREQUENTLY OVERLOOKED RULES	p.10	0.029644 (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 Anachrony — Rulebook (corpus doc 270)	A) RETRIEVE WORKERS · B) CHECK FOR IMPACT · C) CHECK FOR GAME END · D) NEXT ERA · ACTIONS	p.6	0.02901 (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 Anachrony — Rulebook (corpus doc 270)	ACTION ROUNDS PHASE 5 · General rules of the Chronobot's Actions: · Construct	p.13	0.028595 (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 80 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 — 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 Anachrony: Fractures of Time — Rulebook (corpus doc 869)	BLINK STABILIZER · FRACTURE DUPLICATOR · FRACTURE INVERTER · AMETHYNIA TECHNOLOGY CENTER · FAR-FUTURE PLANTATIONS	p.18	#10	0.016129 (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 re-ranker chose it
#2	RULEBOOK Anachrony: Fractures of Time — Rulebook (corpus doc 869)	BLINKING · SUMMARY OF A BLINK ACTION: · CHANGE IN THE MINE RESOURCE ACTION	p.8	#9	0.016393 (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 re-ranker chose it
#3	RULEBOOK Anachrony: Fractures of Time — Rulebook (corpus doc 869)	513 FRACTURE DEVICE CAPACITOR · 514 FLUX SCRUBBER · 515 BLINK SUPPRESSION BYPASS · 516 COMPOUND WARP	p.16	#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
#4	RULEBOOK Anachrony: Fractures of Time — Rulebook (corpus doc 869)	THE FRACTURE DEVICE	p.8	#18	0.012821 (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 Anachrony — Rulebook (corpus doc 270)	Example: · Worker specifics · RECRUIT · RESEARCH 2 · WORLD COUNCIL	p.7	#34	0.010638 (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 Anachrony: Fractures of Time — Rulebook (corpus doc 869)	PATH OF UNITY	p.22	#33	0.010753 (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 Anachrony: Fractures of Time — Rulebook (corpus doc 869)	Princess Zuriel · Prophet Augurus · S.O.T.E.R. · FRACTURES OF TIME · VARIABLE ANOMALIES · NEW COLLAPSING CAPITAL TILES · …	p.20	#28	0.011364 (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
#8	RULEBOOK Anachrony: Fractures of Time — Rulebook (corpus doc 869)	BLINKING	p.7	#11	0.015873 (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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Anachrony: Fractures of Time — Rulebook (corpus doc 869)	BLINKING	p.7	no quote on the wire
[2]	RULEBOOK Anachrony: Fractures of Time — Rulebook (corpus doc 869)	BLINKING · SUMMARY OF A BLINK ACTION: · CHANGE IN THE MINE RESOURCE ACTION	p.8	no quote on the wire

generation — timing and the path taken

timing split: retrieval 79 ms · first delta 4055 ms · total 5744 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 5664 ms · gateway work 5744 ms · total 5744 ms
tokens in (the prompt the answerer read): 3265
tokens out (what the answerer generated): 229
tok/sec: 139.1 tok/sec — 229 output tokens in 1.646 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 8s 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 198), 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.