feat: add verification queue for ambiguous AI-Radar signals - #4
Open
Felix8686 wants to merge 8 commits into
Open
feat: add verification queue for ambiguous AI-Radar signals#4Felix8686 wants to merge 8 commits into
Felix8686 wants to merge 8 commits into
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ai-radar | 349cefb | Commit Preview URL Branch Preview URL |
Sep 03 2026, 02:58 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Recent production alerts showed that page-level changes and catalog observations can still become noisy or misleading high-value pushes. At the same time, dropping ambiguous changes risks losing genuinely valuable free-credit, pricing, API, or release intelligence.
What changed
page_changeand exactlinked_pagecandidates.verification_queueinstead of being directly classified/pushed.discovered_modelcatalog observations are retained only as low-priority internal data and can never directly trigger P1.xxx changedobservations can never directly reach Telegram.expires_atvalues from model-event rows and forces one safe full generic-web fetch to establish link baselines.Safety / deployment order
npm run checkon this branch.0007_verification_queue.sql.ai-radar-mvponly if all checks pass.mainis unchanged and is not the target branch.