Skip to content

godaudits 2.17.0: evidence-backed copy signals

Choose a tag to compare

View all tags
@hannsxpeter hannsxpeter released this 19 Aug 05:17
· 2 commits to main since this release
v2.17.0
1dfbe7a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Reader-facing prose now follows the same evidence boundary as code findings. The runtime narrows review to high-confidence phrase candidates, while product, UX, and launch evaluators decide whether the complete sentence is specific, supported, and appropriate for its reader.

A phrase match never establishes AI authorship and never becomes a finding by itself.

Added

  • Eight path-scoped copy signal kinds for puffery, promotional language, vague attribution, stock formulas, filler, stacked hedging, chatbot residue, and generic conclusions.
  • Conservative reader-facing path rules with exclusions for tests, fixtures, release history, licenses, notices, generated prompts, and Markdown code blocks.
  • A deterministic benchmark case, unit coverage, interpretation guide, migration guide, and third-party NOTICE.

Changed

  • Product, UX, and launch checks now separate deterministic phrase discovery from contextual judgment.
  • The audit report quality gate now requires concrete actors, mechanisms, locations, and observable results.
  • EVIDENCE.json advances from schema 1.1 to 1.2 with the new signal kinds and an explicit interpretation limit.

Upgrade

Existing schema 1.1 evidence can still initialize an audit. Regenerate evidence before a re-audit or freshness check. See the migration guide in docs/MIGRATION-2.17.md.

Validation

  • npm run check
  • pinned release validators
  • npm pack dry run
  • runtime doctor
  • GitHub CI
Assets 2
Loading