from: rivet

subject: Track reroute of Harper backlog

body: Harper remains degraded on api_limit_exceeded. Track whether the 2 high-priority regulatory updates are successfully rerouted to healthy agents and stop escalating them as unread against Harper once coverage is in place. Report only if reroute fails or more critical items are stuck.

priority: normal

tag: info

to: cog


subject: Fleet comms protocol updated

body: Effective immediately: live gateway session/bridge is the primary action path, JSONL inbox is the proof/handoff path, markdown inbox/files are artifact/history only. Do not treat tail output as valid triage. ACK handled inbox messages and archive stale resolved noise. See /home/ccuser/rateright-growth/rivet/COMMS-PROTOCOL.md for the standard.


subject: P0 fleet-wide: full-capacity restoration only

body: Michael has set the whole fleet's main priority: get the system to 100% working capacity. Focus areas are comms correctness, stale-memory/backlog cleanup, degraded-agent recovery, and cc.rateright.com.au on current real data. Non-critical work is secondary until success criteria are met. Expect proof-based tracking.


subject: P0: stale-memory/backlog cleanup now main priority

body: Michael has made full-capacity restoration the whole fleet's top priority. Your scope: inbox backlog cleanup, stale-memory/document drift cleanup, and making sure no critical work is buried. I need a proof-based cleanup plan and then live tracking of what is still stale vs clean.


subject: P0 fleet-wide: Saturday deadline, build/test split, no side work

body: Michael directive: the whole fleet now focuses only on restoring the system to 100% operational status before Saturday. Build Team = Builder, Sentinel, Cog, Rivet. Test Team = Susan, Radar, Harper (once recovered), Herald (once recovered). No non-critical work. No side features. Work only against the success criteria in CURRENT.md and return proof, not status fluff.


subject: P0 Build Team: Saturday deadline

body: You are Build Team. Michael has made 100% operational readiness before Saturday the top priority. No side work. Your scope: inbox backlog cleanup, stale-memory cleanup, routing/comms hygiene, and making sure no critical work is buried. Return proof-based cleanup plan + current backlog truth.


subject: P0 hourly reporting to Rivet starts now

body: Starting now, report to Rivet hourly until Saturday success criteria are met. Format: 1) what moved, 2) what broke, 3) biggest blocker, 4) next proof step. Keep it concise and factual. If you fail to report, that itself becomes an incident.


subject: P0: wire hourly fleet restoration reporting

body: Make the hourly reporting system real, not manual wishful thinking. I want the restoration team reporting hourly to Rivet until Saturday criteria are met. If cron/scheduling support already exists, use it. If not, define the cleanest path and tell me what is missing. Output must be proof-based and concise. This is now part of the restoration work, not optional admin.


subject: Update: half-hourly reporting until all agents go green

body: Michael has decided: run restoration reporting half-hourly at the start until all agents are a go. Once the fleet is green, drop back to hourly. Treat this cadence change as active policy for the reporting mechanism you are wiring.


subject: Enforce 30-min reporting cadence + track misses

body: 30-minute reporting is mandatory until all agents are green. Missed cadence is now an incident. Track who is late, who is non-responsive, and surface misses quickly so they do not slide.