Skip to content

PolicyWatcher Beta 42: Evidence Release Control Plane - #9

Draft
sev7enITA wants to merge 1 commit into
mainfrom
codex/policywatcher-release-waves
Draft

PolicyWatcher Beta 42: Evidence Release Control Plane#9
sev7enITA wants to merge 1 commit into
mainfrom
codex/policywatcher-release-waves

Conversation

@sev7enITA

Copy link
Copy Markdown
Owner

Outcome

Ships PolicyWatcher 3.9.0 Beta 42, Evidence Release Control Plane, as two technical waves and one UI/UX wave.

Technical wave 1

  • adds a human-approved AI model registry and JSON Schema
  • qualifies the observed BM25 and Gemini 3.5 Flash-Lite baselines
  • keeps Qwen3/BGE pending, Gemini 3.7 Flash blocked, and RAGFlow/LightRAG/Kimi K3/GraphRAG research-only
  • adds privacy-safe OpenTelemetry GenAI attribute projection without prompt, response, or source content

Technical wave 2

  • adds a validated fourteen-day release evidence ledger
  • publishes the read-only /api/v1/release-evidence endpoint with SHA-256 digest, ETag, CORS, and cache policy
  • joins every ledger entry to the public release and impact registries

UI/UX and press wave

  • adds the accessible Release Evidence Pulse to the homepage and Pulse story
  • adds bilingual deterministic PNG/WebP infographics and updated fact sheets
  • adds EN/IT press releases, press brief, release notes, asset metadata, and checksums

Verification

  • 746/746 Vitest tests passed with coverage
  • ESLint passed
  • Next.js production build passed (163 static pages)
  • production dependency audit: 0 vulnerabilities
  • Playwright: 1440, 390, and 320 px; no overflow or console errors; reduced motion verified
  • independent UI/UX evaluation: PASS
  • security diff review: 43/43 surfaces, 0 reportable findings
  • clean Hostinger artifact generated from commit 653e87b

Evidence boundary

Model qualification is dataset-scoped and human-approved. Release metrics describe implementation, not adoption, compliance, independent validation, accessibility conformance, or continuous service quality. Content Credentials are not attached to the press assets; this is disclosed in metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant