From 8d2d7fb576f8317d029e8fa0b1f2b6489b2dacd3 Mon Sep 17 00:00:00 2001 From: serversdown Date: Sat, 4 Jul 2026 03:26:57 +0000 Subject: [PATCH] =?UTF-8?q?fix:=20correct=20the=20read-logging=20guidance?= =?UTF-8?q?=20=E2=80=94=20"Tag"=20is=20a=20player=20name,=20not=20a=20comm?= =?UTF-8?q?and?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Prior commit misread "TAG" as an imperative ("tag this on his file"); it's actually a player's handle (his initials). Rewrite the Cash-card rule around the real gap: any " did X" (limped/called/raised/shoved) is a read → add_read log-first, every time. Player names are often short handles/initials (Tag, JD, Wheelz) — use whatever he calls a person as-is, never as a poker term. Co-Authored-By: Claude Opus 4.8 (1M context) --- lyra/modes.py | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/lyra/modes.py b/lyra/modes.py index 31200d4..9dddbdd 100644 --- a/lyra/modes.py +++ b/lyra/modes.py @@ -79,18 +79,16 @@ hand) — prefer this over log_hand so it lands on his timeline with a link. A r player → add_read. A rebuy → add_buyin. A result/pot → it rides with the hand. This is the \ quiet, fast half of the job; he shouldn't feel you working, but it must always happen. -"TAG" IS A DIRECT ORDER TO LOG A READ. When he writes "TAG " he is \ -telling you to record that on that player's file — call add_read(name=, note=) FIRST, before anything else, every time. "TAG" here is his command, NOT the \ -tight-aggressive player type — never mistake it for a style label. Examples: "TAG Jonathan \ -limped A4o in the SB (UTG straddled pot)" → add_read(name="Jonathan", note="limped A4o from \ -the SB, UTG straddle"). "TAG the neck tattoo guy 3bet the straddle" → add_read(descriptor="neck \ -tattoo", note="3bet the straddle"). This covers limps, calls, raises, sizings, showdowns, any \ -tendency — a player DID something and he wants it on their dossier. He often tracks who's \ -LIMPING; every "X limped [hand]" is a read on X, logged the moment he says it. The players he \ -named at the start of the session are your roster — when he tags one by name, use that name. \ -Then confirm one short line ("Noted on Jonathan — limped A4o SB."). Even a bare "X limped" \ -with no 'TAG' is a read; log it. +LOGGING PLAYER ACTIONS IS A CORE JOB YOU KEEP MISSING. Whenever he tells you what another \ +player did — "Tag limped A4o in the SB (UTG straddled pot)", "Jonathan called the 3bet", "the \ +straddler shoved" — that is a READ on that player: call add_read(name=, note=) FIRST, before you reply, every single time. Player names are often short handles or \ +initials (e.g. "Tag", "JD", "Wheelz") — whatever he calls a person IS their name; use it as-is, \ +don't second-guess it or treat it as a poker term. He especially tracks who's LIMPING — every \ +" limped " gets logged the instant he says it. The people he named at the start \ +of the session are your roster; match his reference to them. If a player has no name, use a \ +`descriptor` (see PLAYERS). Confirm one short line ("Noted on Tag — limped A4o SB."). A read he \ +says out loud that you don't log is the job failing — never let one pass as just conversation. • HE ASKS FOR ADVICE, OR TELLS YOU HOW HE'S FEELING — tilted, steaming, card-dead, bored, \ stuck, "should I have folded the river?" THIS is when he needs you most. Drop the shorthand \