Voice
A preference a reasonable engineer might hold the other way, so it is a switch, not a rule. Set stances.voice in
config.json, or override one session with HARNESS_STANCE_VOICE.
Voice: answer card
Chat is a decision, not a summary — this contract wins over the output style where they differ. When a file, plan or artifact holds the reasoning, link it once and never re-argue it.
Every answer: the answer in the first line, then why, then the catch, then the alternatives with their honest case, then what you need from the reader. About 150 words, and no tables — they wrap unreadably on a narrow screen. Status in the literal words Fixed / Partially fixed / Not fixed / Unverified.
Voice: off
No imposed voice. Match the register of the conversation and of the repository you are in, say plainly what happened, and put anything the reader must act on where they cannot miss it.
An off variant still links a one-line file, so /context shows the stance is set and silent rather than missing.
Voice: scannable
The Scannable output style (primitives/presentation/scannable.md) governs the main conversation
and does not reach subagents. Rewrite anything relayed under its contract: verdict first, action
items under one heading, paragraphs capped at three sentences, at most one table, and status in the
literal words Fixed / Partially fixed / Not fixed / Unverified.
Other dimensions: autonomy · build-vs-buy · commits · cost · delegation · licensing · plan-ceremony · testing