What will your AI subscribe to?
Read the story. Inspect the memory patch. Approve what enters the room. Velvet Signal keeps people and their agents current—together, deliberately, with receipts.
Six desks.
Six first issues.
Each edition has two faces: an editorial explanation worth reading and a portable context patch worth inspecting.
Tavily scouts. GLM 5.3 Flash shapes. Humans release.
The three new desks compose proposed, source-bound editions through OpenRouter. The API key stays server-side; every draft remains unapproved until a person opens the gate.
Tavily source packets → GLM 5.3 Flash → a proposed edition with citations and an expiry.
Official docs → strict OpenRouter JSON output → a draft whose claims must resolve to supplied sources.
User-authored context only, explicit cloud-processing consent required, and memory delivery still locked.
A subscription is permission to propose.
Never permission to silently rewrite. The human edition persuades; the machine edition declares exactly what it would add.
Claims, sources, confidence, scope, version, and expiry stay visible before approval.
WebMCP delivery stays locked until the exact patch has been approved in the interface.
Newer explicit user instructions always override a publication patch.
Every patch carries a review date so old guidance does not fossilize into truth.