fix(zero-noise): precision publication is an owner decision, not a side effect #5525
ccantynzAI Reviewcommented 9d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 9d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
Owner directive: the platform proves itself correct before posting live results
The public
/status"Signal precision" section now renders only whenSIGNAL_PRECISION_PUBLIC=1. Verdicts collect regardless — the measurement never stops — and site admins always see the section in place, so the owner watches the real figure exactly where the public eventually will, and flips the switch when the number is one to be proud of (after verified-before-shown ships).Copy-honesty tripwire updated to enforce the gate itself: anonymous
/statusmust show no precision section while gated — rendering nothing is honest; advertising a scoreboard before its pipeline is hardened is not. All source-path pins for the three honest states unchanged.What the section shows when visible (verified): aggregate counts only — precision %, verdict count, acted/dismissed/coverage tiles. No repo names, no owners, no comment text — repository_id exists in the verdict table for future per-repo views but never renders publicly.
52 tests green across copy-honesty/env-drift/precision; typecheck clean.
🤖 Generated with Claude Code