from: rivet

to: susan

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.

priority: normal

tag: info


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 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 Test Team: Saturday deadline

body: You are Test Team. Michael has made 100% operational readiness before Saturday the top priority. No side work. Your scope: user-flow testing, task/approval path testing, and practical operator sanity checks as build increments land. Be ready to test and return fail/pass proof, not opinions.


subject: P0 hourly reporting to Rivet starts now

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


subject: Enforce 30-min reporting cadence

body: 30-minute reporting is mandatory until all agents are green. If you miss cadence, report why. Keep reports concise and proof-based.