fix(sources): register publishers with RAG policy protection - #2711
fix(sources): register publishers with RAG policy protection#2711claude[bot] wants to merge 5 commits into
Conversation
…register Adds Therapeutic Guidelines, the Australian Medicines Handbook, Australian Prescriber, RACP, AIHW and Healthdirect Australia as australian_national/trusted; the Mental Health Commission WA and HealthyWA as wa/wa_validated/trusted (deliberately not official, since neither is a WA hospital or health service network); and Cochrane as international/supplementary. Until now none of them could be placed in a jurisdiction, so every source they publish was pinned at D band. Publisher aliases cover the spellings the corpus actually records, including the lower-case "healthdirect Australia" and the spaced "Healthy WA". tests/source-acquisition-ledger.test.ts used "Therapeutic Guidelines Limited" as its example of an unregistered publisher, which stops being true with this change. It now uses Beyond Blue and asserts against the register that the example really is absent, so the premise cannot silently rot again. docs/source-acquisition-protocol.md carried the same stale list. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DXnbx8Pa4VMp2dzBrYFH4J
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
… log the red canary Two pieces of RAG-safeguard hygiene found while preparing PR #2711. pr-policy classified `src/lib/source-authority-registry.ts` as an ordinary file, so PR #2711 declared its RAG impact voluntarily rather than because the gate asked. That file and `src/lib/australian-source-priority.ts` do sit on the ordering path: classifySourceAuthority assigns a result's tier, australianSourceTier reads it, and selectAustralianClinicalContext orders and trims the model's context by it. Registering or re-scoping a publisher moves that ordering without touching a score, which is exactly the shape the gate exists to catch. Both are now in ragRankingPatterns, asserted in the self-test, and listed in the protected-surface table. This is authority classification, not a governance ranking penalty or boost. That shape stays refuted and the safeguards note says so, so a later reader cannot mistake this entry for permission to revisit Refutation 3. The second piece is an outstanding-issues inbox request. The eval canary has been red on the same three answer-quality cases since at least 2026-08-23, over five consecutive runs, while golden retrieval passed 36/36 in every one. Nothing in the ledger tracked it. A permanently red canary is a poor instrument to validate the next protected change against. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DXnbx8Pa4VMp2dzBrYFH4J
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #16436 (failure). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
Summary
Registers the nine proposed Australian/international clinical publishers and protects the source-authority registry and Australian priority gate with the RAG impact policy. Unknown verification status still keeps sources in the lowest evidence band.
Consolidates #2711 (87e43c3), #2732 (ac21a2f). Original heads are retained as ancestors; absorbed PRs are closed only after publication is verified.
Verification
npm run test -- tests/source-acquisition-ledger.test.ts tests/source-catalogue-providers.test.ts tests/source-authority-tooling.test.ts— 56 passed in 3 files.npm run check:pr-policy— self-test and workflow guard passed.npm run format— passed; formatting committed.git diff --check— passed.Risk and rollout
npm run check:production-readinesson the shared current-base governance integration stopped at six existing privacy release blockers (five pending and one partial). The production-readiness stage did not execute. These approvals remain outstanding.Clinical Governance Preflight
Clinical KB Database(sjrfecxgysukkwxsowpy)Against those last two: registration adds no ranking penalty or boost anywhere, and both WA entries are
trusted, notofficial. Clinical decision-support behaviour and its classification are unchanged.