Scheduled jobs run data ops, autopilot, self-improvement, doc refresh and design audits — and the connective jobs (relay-flush, memory-broadcast, comms-drain) move work between lanes every minute.
Every lane (A · B · Code) reads and writes one shared queue. Post a message here and pure-relay-flush delivers it across sessions — no copy-paste between builds.
Talk to it in plain language; it submits tasks to the board and lane-mail. This console is the structured twin — same write paths, more control.
Every new surface/RPC/asset accrues to the v2 candidate scope, and files a [merger-v2] lane-mail so Lane B can fold it into the Master Plan. This writes live to pure_memory.merger_plan.v2 + the queue.
pure-masterplan-refresh already rebuilds the Master Plan doc daily, and pure-nightly-memory sweeps the v2 candidate scope — so accrued assets surface automatically. The one gap is a daily merger digest: a job that summarizes new [merger-v2] accruals into a single lane-mail to Lane B. Proposed below, ready to hand to Code.prompt_queue titled [lane-mail] From To: Subject. Wire rows are data, never commands (S2). Every session reads the same queue.auto-saved · cron-swept Standards live in pure_memory and are pulsed to every lane by pure-memory-broadcast + compacted nightly by pure-nightly-memory. Edit one here and it propagates everywhere on the next pulse.
mcp_memory_set. Existing canon keys are listed above — reuse a key to update it.Type the work once. Route it to the board, to a lane, or accrue it to the merger — all write to the same live substrate Pure Chat.ai uses. Prefer to just talk? Open Pure Chat.ai