06-reference

alphasignal cursor moe liquid ondevice agent

2026-08-05·reference·source: AlphaSignal·by Lior Alexander
agent-infrastructuremulti-agent-protocolson-device-inferenceopen-source

Why this is in the vault

Nous Research's Hermes Agent v0.20.0 ships a standardized agent-to-agent protocol plus "grounded research" (citation-backed responses) as first-class features — both are concrete external validation that the problems RDCO's own station-based brigade and citation-discipline work solve internally are becoming standardized/productized elsewhere.

Curation section

Zero third-party deep-fetches triggered — every item above is fully legible from AlphaSignal's own blurb depth, and none crossed the bar of "specific enough hook to justify a follow link" beyond what's already summarized.

Mapping against Ray Data Co

Hermes Agent's A2A protocol and "grounded research" citation feature are the load-bearing items, not the Cursor kernel headline. RDCO already runs a station-based skill-agent-brigade (station-spec-author → station-test-author → station-code-author → station-critic) that is functionally a hand-rolled agent-to-agent pipeline with no standard protocol underneath it — Hermes packaging that as A2A v1.0 is a signal the industry is standardizing exactly the coordination layer RDCO built bespoke. Worth a scan of A2A's actual spec next time the brigade pattern gets touched, to see if adopting a standard protocol reduces the custom glue currently living in station configs. The "grounded research" feature (verifiable citations attached to agent output) is a second, sharper parallel: it's the same instinct behind RDCO's "verification belongs to an independent worker" principle (routing vault writes and dispatch prompts through fresh-eyes critics) and the vault-note-schema's citation/quote discipline — except Hermes bakes citation-grounding into the model's output path rather than a post-hoc external gate. That's a capability gap worth tracking: RDCO's verification is currently all external-gate (a second worker checks), while this points toward verification-at-generation-time as a maturing alternative. Liquid AI's on-device 2.6B agent is weaker for RDCO specifically — no live on-device inference project exists (Squarely is a puzzle app, not an LLM-hosting surface) — but the 4x-smaller-than-Qwen3.5-9B tool-use result is a capability-frontier marker worth remembering if a future RDCO surface ever needs local, zero-marginal-cost agent inference.

⚠️ Sponsorship

Three sponsor placements. Mistral — top "In Partnership with" banner plus a dedicated section pitching Document AI (enterprise OCR/data-extraction: PDFs, scans, DOCX, PPTX, handwritten sources, 170+ languages, 98%+ accuracy claim). Notably, Mistral also appears as an unpaid editorial Signals item two sections later (open-weight 3B safety model) — same company shows up as both sponsor and organic news pick in one issue, which is worth flagging as a house-favor pattern even though the two Mistral mentions cover different products. Tiger Data — sponsors the mid-issue section pitching TimescaleDB/Postgres for querying AI event data (prompts, embeddings, eval logs, latency traces) at scale; cites a customer (Plexigrid) cutting query times from 5 minutes to 0.5 seconds. Bright Data — sponsors Signals item #2, pitching real-world video data (vs. synthetic) for training VLAs (vision-language-action models). None of the three sponsors' pitches overlap with the top editorial picks (Cursor MoK, Hermes v0.20.0, Liquid AI LFM2.5), so the news judgments read independent of the sponsor slate, aside from the Mistral dual-appearance noted above.

Related