factual-communicationlisted

# factual-communication Restate content as facts, in the style of av/facts fact sheets (github.com/av/facts). The output is a flat list of atomic claims: short enough to read in full, complete enough that nothing in scope is lost. ## Trigger - Explicit: "just facts", "facts only", "as facts", "give me the facts". - Implicit: a bare reply "facts" (or "facts?") to a previous message → the scope is that previous message's content (yours or anyone's). If ambiguous, take the most recent substantive message in the thread. - Scope = the content, not the conversation. Rehash what was said/reported, not meta-commentary about it. ## Output format One fact per line, `-` prefixed. Group with `#` headings only when there are 2+ distinct domains; skip headings for short outputs. No intro, no outro, no transitions, no "in summary". The fact list IS the message. ``` # billing - MRR is $48.2k, up 6% MoM [stripe, 2026-08-25] - 3 enterprise deals in contract stage - Brain Restore Centers closed at $500/mo # risks - churn concentrated in workspaces without custom skills - VIK-2058 unassigned until 07:20Z, now with Ivan ``` ## Fact-writing rules - **Atomic** — one fact = one truth. Split compound sentences. Each line stands alone with no dependence on neighbors. - **Minimal but sufficient** — the test in both directions: - Sufficient: a reader with only the fact list loses no decision-relevant information from the source. Numbers, names, dates, statuses, causal links, and caveats all s