# nobrainer-tech-flow 2.1.1 verification record

Source version: 2.1.1. This corrects the communication defaults introduced with
[2.1.0](v2.1.0.md). Publication is a separate tag and source-archive check.

## Scope

One Flow communication policy governs operational prose between agents and
user-facing replies. Agent exchanges default to plain technical English, while
user replies are written directly in the requested language. Team, Dispatcher and Sessions reference the same policy. The unchanged
bootstrap already routes to Flow, which owns that default. Existing task schemas,
source literals, language overrides, permissions and evidence remain binding.

Writing selects TECHNICAL for English technical artifacts when no other mode
is requested. Other languages use natural plain language with the same factual
contract. Marketing, creative work and author voice keep their purpose.

There is no additional translation call, provider, model setting, benchmark,
runtime process or skill. This policy concerns visible messages, not hidden
reasoning. It does not claim full ASD-STE100 compliance or performance savings.

## Evidence and limits

The frozen v2.1.0 baseline already passed the two small communication exercises;
its instructions did not mandate the agent-language default. This release makes
the policy explicit. The same two pressure cases and three fresh holdout
exercises passed meaning checks, including a Polish worker-language override,
exact code/JSON/quoted warnings, and a warm Polish marketing artifact. MAIN
checked the actual saved outputs and literal preservation. Same-session exercises are not a blind causal comparison
or proof that every client loads and follows the skill.

Release gates: source/link/version validators, adapter and installer-link
regressions, full Python tests, staged secret scan, semantic pressure and holdout
checks, source review, and separate release/archive readback. The release notes
link exact CI results after validation. No cross-client runtime or cost claim
is inferred from these gates.

## Rollback

Use the reviewed v2.1.0 source and the documented installation dry-run and
backup checks. No persisted schema or data migration is introduced. Keep the
source checkout present while client links point to it. Explicit user language
and style instructions override the new default without a rollback.