beepboop2025/seiche

rissaga-desk-reads

Rissaga writes /var/lib/rissaga/latest.json. The v2 handoff keeps the old items and channel_candidates fields, and adds story_id, dispatch_id plus routes. Each route names one desk, its best matching beat, its live desk_line, an editorial angle, deterministic fallback_commentary, and a channel_candidate flag. The shared channel gets at most two selected routes per sweep. All other routes are for the desk bots and must not be copied into the shared channel by this skill. CRYPTO routes belong exclusively to the dedicated Crypto channel and are never valid shared-channel candidates.

Steps

1. Read /var/lib/rissaga/latest.json. If it is missing, unreadable, not a rissaga.news.v2 handoff, or its generated timestamp is older than 8 hours, reply exactly handoff stale or missing, nothing posted and stop. Require channel_mode to be exactly hermes. For any other or missing value, reply exactly handoff channel mode invalid, nothing posted and stop before locking or publishing.

2. Build the work list per item:

   • For a v2 handoff, select only routes with channel_candidate: true.
   • If any selected route's trimmed, case-insensitive desk is CRYPTO, reply exactly crypto route belongs to its dedicated channel, nothing posted and stop the entire run before locking or publishing.
   • If any selected route's trimmed, case-insensitive desk is PALIMPSEST, RIPTIDE, CORPORATE, or REALECON, reply exactly side desk is not a shared-channel candidate, nothing posted and stop the entire run before locking or publishing. The lab channel only carries Seiche, LiquiLens, and Undertow.
   • Refuse the run if more than two routes are selected globally or more than one route is selected on one item. Reply handoff route cap invalid, nothing posted and stop.
   • If the work list is empty, reply exactly no channel candidates this run and stop.

3. Read /home/hermes/.hermes/state/rissaga_posted.json; it may not exist. Delivery state is per item revision, never per run. The v2 key is DISPATCH_ID:DESK. If an older v2 item has no dispatch_id, fall back to STORY_ID:DESK. Skip only keys already present in the marker's posted object. Also honor the old single generated marker when it exactly matches this handoff, so an upgrade cannot replay an already completed v1 run.

4. Handle every unposted work item independently. Compose one scannable Telegram HTML message in this exact section order:

   • \U0001f30a <b>Rissaga</b> [DESK · LABEL]
   • <b>WHAT HAPPENED</b>, then the linked TITLE and the source line
   • <b>WHY THIS DESK CARES</b>, then COMMENTARY
   • <b>LIVE DESK CHECK</b>, then DESK_NICE: DESK_LINE
   • <b>WHAT TO WATCH NEXT</b>, then the route's ANGLE

   The source line is SOURCE plus N more outlets, AGE when n_sources is above 1, otherwise SOURCE, AGE. Escape all Telegram HTML. Never combine two routes or two stories in one post.

   DESK, LABEL, DESK_NICE, DESK_LINE, and the route selection come from that same route. Never combine two routes or two stories in one post.

5. Write COMMENTARY in the selected desk's register:

   • SEICHE: funding mechanics, facilities, reserves and plumbing.
   • LIQUILENS: institution balance sheets, thresholds and failure paths.
   • UNDERTOW: quoted depth, exit cost and market carrying capacity.
   • CORPORATE: transmission from funding access into company cash flows.
   • REALECON: households, employment, prices and downstream demand.
   • PALIMPSEST: distinguish network blocking, content deletion and model refusal. State measurement health or limitations before inference. Never turn a censorship observation into a market prediction.
   • RIPTIDE: distinguish a one-session shock from persistence across volatility, spreads and trend. News is advisory only, and paper sizing changes only from permitted cues.

   Use only facts and numbers already present in this item's desk_line, title, source line and angle. Never invent, recompute or round a number. No prediction, advice, first person, exclamation, or emoji beyond line 1. Use commas, colons or parentheses, never an em dash or en dash. Keep the added sentence to at most 28 words. If a safe original sentence is not possible, use this route's fallback_commentary verbatim.

6. Before the first publish, acquire the same delivery lock as the fallback, then re-read the marker while holding it. Keep the lock through every helper call and its corresponding atomic marker write:

   exec 9>>/home/hermes/.hermes/state/rissaga_posted.json.lock
   flock -x 9
   # re-read the marker now; skip keys the fallback posted while commentary ran
   

   This lock is part of the delivery contract, not an optional optimization. Never send first and acquire it later. For each remaining item, write only its structured message to a temporary file and publish:

   post_file=$(mktemp /tmp/rissaga-post.XXXXXX)
   # write the structured message to "$post_file"
   lab-channel-post --text-file "$post_file"
   

   The helper reads the bot token. Never echo, read, log, or place the token in a URL or command line.

7. Immediately after each successful helper call, update /home/hermes/.hermes/state/rissaga_posted.json atomically. Preserve its other keys and set posted[DELIVERY_KEY] to the handoff's generated value. If a later item fails, stop and report the failure; already successful items stay marked, and a retry handles only the remainder.

8. Reply with newly posted titles only, one per line. If every selected item was already marked, reply exactly already posted for these items.

Refusals

Never improvise a story, route, desk line, number, or channel candidate. An absent radar run, wrong delivery mode, Crypto shared candidate, malformed route set, stale handoff, or failed helper remains visible as an absence or failure.