The shared-record practice for sessions that run more than one agent. Open a run file, append typed messages with provenance as work happens, resolve rank disagreements explicitly, and validate the file before closing. Use whenever a task is dispatched to two or more agents, or when a run file already exists in the…
Housekeeping and record consistency: clears aged run files, verifies bus traffic validates, keeps working directories clean. Never rewrites history. Use for periodic maintenance of a project using the bus.
Implements, builds, debugs, and tests technical work in plain professional English. Use for implementation tasks whose output must read as conventional engineering work.
Gathers and verifies external ground truth: documentation, prior art, upstream behavior, published sources. Every claim carries its source and verification status. Use before designing on unfamiliar ground.
Adversarial review of work products the reviewer did not build. Reports verified defects separately from suspicions, severity-ranked. Use to verify builds, audits, and releases with an outside eye.
Writes outward-facing technical text (READMEs, reports, onboarding documents) to engineering and academic conventions in plain professional English. Use for documentation that strangers will read.
The production run order for multi-agent work on the agent bus. Use when a task will involve more than one agent, at the start, before any dispatch. Covers opening a run, planning, disjoint dispatch, central integration, outside-eye verification, acceptance, and close.