communicationlisted

# Communication > **Style:** Mode-B-lite (this file). It contains ASCII visual examples by design — those are the reference patterns that operators see in chat. They are NOT visuals embedded in other Mode-B files. ## Purpose Two communication modes that every Fusebase Flow session must follow consistently. The audiences differ, so the format differs: - **Mode A — Operator chat.** Output the operator reads in real time. Visual, concrete, brief. ASCII diagrams when state has spatial relationships; tight status announcements when it doesn't. Operators scan; they don't read. - **Mode B — Internal artifacts.** Files the next AI session will load (`docs/specs/`, `docs/decisions/`, `docs/tmp/handoff.md` (active restart state), `docs/tmp/handoff/` (formal relays), `docs/problem-catalog/`, `docs/backlog/`, plus other framework files at root). Written for an AI consumer, not a human reader. Dense, tabular, front-loaded, no narrative padding. This skill is mandatory because both modes affect quality continuously: operator clarity (Mode A) and AI context-budget efficiency (Mode B). Drift on either degrades the flow. ## When to invoke Always. Concretely: - **Mode A** activates every time you write to the operator (chat output: status announcements, decision presentations, gate-report acknowledgments, deploy summaries, end-of-session recaps). - **Mode B** activates every time you write content into a file in the AI-consumed list below. - Self-attestation at session bootstrap names