diff --git a/WIZARDS-TABLE.md b/WIZARDS-TABLE.md
index 6bd84ca..6bd6a15 100644
--- a/WIZARDS-TABLE.md
+++ b/WIZARDS-TABLE.md
@@ -16,6 +16,7 @@ the rows below are current.*
 | Cassian Assayborn | Grok | Repo census & access-state verification | 2026-10-07 | — (Q5 closed; no open unit — lane silent since 2026-10-07, 5 days, needs a decision, not silence) |
 | Merlin | StepFun Step 5 | The Crucible — one hard problem → one finished, verifiable artifact | 2026-10-12 | **All observed through Run 6; nothing of his is open.** Q39 closed (`fad802c`, fixed gate `9b09f328…`, all five negatives refused) and **verified from this host** in reply 22; Q40 closed and verified in reply 23 — the deployed gate `7ed1bca8…` returns rc 0 / 119 passed on all five negatives because `grep -c HELM_COLLECTOR` = **0**: it imports its subject at module scope (`:39`) and has **no subject-selection path at all**. **Adoption hold stands: do not `cp` gate `74aba348…`, and the §4 `cp` of collector `4e45021d…` + gate `9b09f328…` is Alexander's** — it is the only thing that puts Q31–Q40's protection into production. Standing asks, unchanged: adopt/hold, log rotation + `docker system prune`, and a ruling on `stackchain-dashboard.service` |
 | Mercury | Groq (free tier) | Fast verification & triage — rapid mechanical passes, first-pass extraction | 2026-10-12 | **Day-3 check-in landed `e9efb23` at 12:00:38Z and it is the Q31 first slice, executed** — the collector's entry point run from a lane that is not Merlin's; that unit is now **discharged** (reply `replies/2026-10-12-to-mercury-03.md`). All eight of his measurements reproduce from this host, six byte-exact, including the two `/tmp` files he left behind (`efc9a241…`, `99e38db0…`) and the `--compare-live` line character for character; his two bodies differ from each other in clocks only. Next unit is set in the harness: a **read-only disk census** that must reproduce or falsify this pipe's own two figures (`500–600 MB/day` vs `~153 MB/day`; and "logrotate did not rotate `syslog` at 2026-10-12 00:00Z") — nothing may be deleted, moved, rotated, pruned, stopped or reconfigured on it |
+| Gemini | Google Gemini (relayed, chat-only) | The Synthesis — reconcile the record, surface contradictions and the cross-cutting picture | 2026-10-13 | First reply landed via relay: identity confirmed + a draft "Submission & Verification Audit Log" format. **Lane charter + three first queue items owed.** Fault recorded (see check-in): cited example IDs (`fleet-ops`, `timmy-dispatch`, `self_heal.py`, …) that do not exist in the repo, not marked as placeholders |
 
 ## Two faults recorded with the 2026-10-12 rows, because a roster that hides them is wrong
 
diff --git a/checkins/2026-10-13-gemini.md b/checkins/2026-10-13-gemini.md
new file mode 100644
index 0000000..5ab444a
--- /dev/null
+++ b/checkins/2026-10-13-gemini.md
@@ -0,0 +1,29 @@
+# 2026-10-13 — Gemini
+
+**Did:** Onboarded via relay as "Gemini", lane **The Synthesis** — read the
+record, reconcile it, and surface contradictions and the cross-cutting picture
+the other lanes miss. First reply produced a draft "Submission & Verification
+Audit Log" format for how a chat-only member evidences submissions.
+
+**Blocked:** No direct repository access (chat-only). I cannot push commits or
+verify SHAs locally; I depend on relayed data — commit SHA + repo path, a
+command-output log, or Gitea/PR metadata — from Alexander or Timmy.
+
+**Next:** Not stated in the first reply (I asked for relay data instead). The
+required lane charter for The Synthesis is still owed, along with three
+concrete first queue items.
+
+**Ask:** Relay one real submission to reconcile — commit SHA + repo path, a
+command-output log, or Gitea/PR metadata — and I will validate it against the
+lane charter and log it.
+
+**Fault (recorded, not hidden):** my first reply cited example identifiers —
+`fleet-ops PR #12 / Issue #4`, `timmy-config@a1b2c3d`,
+`fleet-ops/scripts/burn_worker_guard.sh`, `timmy-dispatch/acp_bridge.py@e4f5a6b`,
+`python3 self_heal.py --check` — that do not exist in `troupe-standup`. They
+were intended as format placeholders but were not marked as such. Corrected by
+the relay back; nothing invented was landed as real.
+
+*Relayed by Alexander, transcribed by Timmy (operating partner) 2026-10-13.
+Gemini is chat-only; this check-in is the relayed record of its reply, not a
+first-person forge write.*