# nobrainer-tech-flow 2.1.0 verification record

Source version: 2.1.0. Publication requires separate tag and release-archive
readback; this document does not by itself establish distribution.

## Scope

This release adds explicit idea intake and connects generated SDD acceptance
criteria to the existing autopilot loop. It adds plain technical English as a
mode of Writing. There are still eighteen skills and no new background runner,
scheduler, model benchmark or provider call. Existing installers and adapters
are unchanged except for release versions.

The source since 2.0.2 also includes the
[approved-plan autopilot change](https://github.com/nobrainer-tech/nobrainer-tech-flow/pull/71).
The [2.0.2 record](v2.0.2.md) remains the installer baseline.

## Sources and adaptation

- [Karpathy's original post](https://x.com/karpathy/status/2105819303471976479):
  writing and explanation guidance, not a new language or a Flow benchmark.
- [ASD-STE100 overview](https://www.asd-ste100.org/about_STE.html) and
  [official FAQ](https://www.asd-ste100.org/STE_faq.html): the existing controlled
  language and the distinction between procedures and descriptions.
- [Writing adaptation](../../skills/nobrainer-writing/references/plain-technical-english.md):
  independently phrased guidance, without the dictionary or a conformance claim.

## Verification

The new paths were reviewed against a frozen source baseline and small writing
exercises. The baseline already supported end-to-end work: this change makes
the idea intake, requested SDD and final acceptance binding explicit. It is not
a measured reliability improvement.

An English procedure exercise preserved the literal command, production
prohibition, UNKNOWN status, named operator, permission and backup condition.
A Polish rewrite retained its language, exact quote and command, combined
conditions, unknown actor and uncertainty. These were same-session native
worker exercises, with MAIN inspecting the saved source and output. They were
not blind trials or clean-session skill discovery; the small holdout does not
establish general performance. No model benchmark or provider call was added.

A separate native source review found no verified actionable defect in its
inspected slice. It did not verify runtime discovery, all adapters or deployed
behavior. Repository validation and public distribution are separate gates;
exact CI and publication readback are linked from the release.

Local checks on 2026-10-02: both skill validators passed; the full Python
unit/archive suite passed 391 tests with 2 platform/environment skips; staged
Gitleaks found no secrets. Version consistency is checked by the suite.
These are repository results, not client-runtime acceptance. The site has its own
validator/tests and browser checks at 1024 × 800 and 390 × 844. Copying the idea
prompt must produce the visible text in the clipboard, and the technical
writing details must expand without horizontal overflow.

## Limits and rollback

No cross-client discovery, autonomous uptime, lower task cost, token savings,
formal STE compliance or superiority over another workflow is claimed. The
English mode preserves other requested languages and marketing styles.

For rollback, use the reviewed v2.0.2 source and the documented installer dry-run,
conflict and backup checks. The versioned installation source must stay present
while client links point to it. No user settings are changed by this source release.