Human Writing Rules 1.2.0

Human Writing Rules 1.2.0 — 2026-09-28

This release adds a practical workflow for existing Markdown drafts and a
locally installable CLI distribution. The normative profile remains 1.0.0.
The installable tarball is distributed through GitHub Releases; publication to
the npm registry is not part of this release.

Changes

• hwr review preserves supplied text while collecting structured findings.
  hwr edit can apply one material-finding revision cycle and re-review it.
  Inputs, hashes, stage records, diffs and separated output remain inspectable.
• hwr init creates a pinned project configuration and partial task without
  replacing an existing configuration directory.
• sources snapshot and runs check now execute natively on Node.js, with
  TypeScript/Python response parity and boundary tests.
• The npm tarball contains compiled runtime code, modules, schemas and Python
  compatibility tools. A smoke test installs it offline outside the repository
  and exercises native commands and both editing modes without devDependencies.
• A frozen corpus contains 24 RU/EN semantic editing exercises, including
  unchanged controls. Rating validation preserves missing cases and failures.
• Comparative-pilot tools prepare repeated plans, execute explicitly authorized
  single-response model arms, export blinded samples and aggregate declared
  ratings while retaining disagreement and hard failures.
• Six native resolver obligations have scoped automated evidence. The remaining
  194 requirements stay planned; full implementation conformance is not claimed.
• Twelve canonical offline release gates include TypeScript, package installation
  and corpus integrity alongside the existing Python and registry checks.

Compatibility and boundaries

Existing object IDs, RFC semantics, JSON records, source snapshots and workflow
commands keep their 1.x contracts. Editing commands initially require text-only
tasks; they do not silently discard a requested visual. They require a supplied
task/evidence record and a trusted adapter. An incomplete brief remains blocked.

Python 3.9+ remains necessary for editing, lifecycle and provider adapters,
benchmarks and release validation. Node.js 20.10+ is required for the CLI.
Source-checkout verification needs development dependencies. No new production
dependency or framework was added.

The semantic corpus and offline adapters are fixtures, not measured model
quality. Live comparative runs, human ratings and independent external review
remain unperformed. The experimental benchmark measures single-response context
conditioning, not the complete staged editing workflow. It supports no general
claim that HWR improves every text.

Verify and package

npm ci
npm run verify
npm pack --pack-destination /tmp

The release tag identifies the source commit verified by GitHub CI. The
publication procedure is in RELEASING.md. See the
editing guide and
comparative pilot protocol.

Install the release archive

Download human-writing-rules-1.2.0.tgz and SHA256SUMS from the assets below, verify the checksum, then install:

npm install -g ./human-writing-rules-1.2.0.tgz
hwr --version

Source commit: 7feeae1ab5c18297716143f88fe8ff41c9249a49.

Release CI checks all twelve gates on Python 3.9 and 3.12.

Human Writing Rules 1.1.1

Human Writing Rules 1.1.1

This patch release makes the existing editing rules easier to apply and fixes
CLI version reporting. The stable 1.0.0 normative profile is unchanged.

What changed

• Added a practical editing guide with six Russian and English examples. It
  shows how to remove empty setup, simplify bureaucratic wording, correct an
  unsupported promise, and preserve a material limitation. Two examples show
  when clear prose should remain unchanged.
• Clarified preservation of the supplied author's voice, comparison of meaning
  across revisions, and the requirement to tie style findings to a concrete
  reader problem. Review guidance now explicitly addresses when to stop editing.
• Fixed hwr --version and top-level help to report the installed distribution
  version from package.json, rather than the specification revision. A
  regression test checks both outputs outside the repository and without Python
  on PATH.
• Updated English and Russian README navigation, related guides, and repository
  positioning around evidence boundaries, review contracts, and audit records.

Compatibility

Existing configs, active object IDs, schemas, JSON envelopes, and workflow
commands retain their 1.x contracts. The distribution version is 1.1.1;
doctor continues to report specification revision 1.0.0.

The six editing exercises are informative examples. They are separate from the
catalog of 21 reviewed publication examples and do not establish measured
improvements in model output quality.

The internal stability review remains non-independent. Unported commands and
release validators still require the Python compatibility backend.

Verification

npm ci
npm run verify

Verification includes TypeScript typechecking and CLI tests, Python unit tests,
and the eight manifest-defined release gates. CI runs the suite on Node.js 20
with Python 3.9 and 3.12. Core verification remains offline after dependency
installation; live provider adapters require explicit opt-in.

Human Writing Rules 1.0.0

Human Writing Rules 1.0.0

The first stable release defines a vendor-neutral editorial specification for
AI-assisted articles, social posts, and optional illustrations.

What is stable

• RFC-0001 through RFC-0006 form the active normative 1.0.0 profile.
• All 50 registered runtime objects are active.
• Active RFC, requirement, and object identifiers retain their meaning across
  the 1.x line and are not silently reused.
• Breaking normative, schema, protocol, or identifier changes require a new
  major version and migration notes.

Included

• RU and EN language foundations;
• article and social-post workflows;
• 11 topic foundations and 6 platform families;
• source-integrity, human-signal, visual-integrity, and review contracts;
• an offline reference runner and guarded editorial lifecycle;
• 200 mapped normative requirements and 10 conformance fixture cases;
• 16 reviewed examples covering every registered topic and platform family;
• evaluator-neutral benchmark and visual-acceptance contracts;
• deterministic registry generation and eight offline release gates.

Important boundaries

Stable specification status does not claim that every writing engine, or the
bundled reference tooling, has proven full implementation conformance. The
requirements matrix currently contains implementation obligations awaiting
engine-specific evidence.

The stability assessment was internal and not independent. This release does
not include public comparative model-quality results or inter-rater reliability
evidence. These limitations are recorded in
release/stability-review.json.

Upgrade

Users of 0.2.0-draft should follow
MIGRATING-TO-1.0.md. Historical audit artifacts
remain pinned to the revisions that produced them.

Verification

npm run release:verify

The command runs the manifest-defined release gates offline. The optional live
provider adapter remains opt-in and requires credentials supplied through the
environment.