Audit Event Engine — 23/10 11:32 → 26/10 11:13 UTC

Audit Score

92.4/100 · previous n/a · delta n/a · rolling-three n/a · trend-building 0/3 · direction n/a · confidence LOW

Component	Score
Precision	23.1/30
Recall	19.6/20
Accuracy	24.8/25
Reliability	25.0/25

TP=47 · FP=14 · FN=1 · valid-actions=48 · event-checks=47 · failed-sources=11 · incident-controls=0/0 · sources=1835 · formula=1 · retrospective=no

En bref

Relecture : complète. J'ai relu une par une 1 835 sources, 199 fiches d'événements et 1 554 paires de doublons possibles. J'ai aussi relu les 6 propositions retenues, les 55 sources en échec ou en reprise et l'incident fournisseur. Il reste 0 élément à relire. 4 fiches sont exclues faute de preuve : une source réduite à un lien, ou un fil non capturé.
Validation du dossier : passée. verify_audit_bundle.py a vérifié le rapport, le score et l'historique, avec la sortie 0. Les limites de preuve sont listées dans le détail technique.
Corrections en production : rien n'a été modifié. Tout ce qui suit est une recommandation, en attente de ton accord.

1. À trancher

Cas (tweet)	Question	Ma recommandation
Application d'un tiers chez un fournisseur : jeu de poker « Distracted » propulsé par Arcium, fiche E100249 (tweet), même jeu filtré dans un autre post (tweet) · Perceptron qui s'installe sur Walrus, fiche E100234 (tweet)	Le 14/10, tu as dit qu'une fonction du fournisseur qui s'active dans le produit d'un tiers est un événement du fournisseur. Le 23/10, tu as dit qu'un produit tiers rend le tiers sujet. Le prompt du 24/10 ajoute : « une app qui consomme l'API d'un fournisseur n'est pas un usage direct ». Le moteur actuel republie ces deux cas 3 fois sur 3. Laquelle de ces règles s'applique ?	Le tiers est le sujet, sauf si le fournisseur annonce lui-même une nouvelle fonction. Je supprimerais donc E100249 et E100234, puis je ferais préciser cette frontière à la prochaine calibration.
Chainlink : une annonce « TODAY: New integrations », trois fiches le même jour (E100231 CCIP sur Gravity, E100232 CRE sur Solana, E100233 ACE sur Theorem) (tweet)	Trois partenaires différents dans une seule annonce : est-ce une fiche ou trois ? Ta règle sur le découpage vise les changements d'une même chose (cas Polygon). Ici, ce sont trois intégrations distinctes.	Garder E100231 et E100233. Supprimer E100232 : rendre CRE disponible sur une chaîne de plus, c'est étendre une fonction existante, donc un simple élément (ta décision du 23/10).
Sommet trimestriel NEAR réservé aux fonds, fiche E100229 du 28/10 (tweet)	Le contenu est une mise à jour trimestrielle de l'équipe (valide), mais l'accès se fait sur invitation, et le prompt exclut les événements privés.	Garder, selon la règle « dans le doute, on garde ». Le moteur actuel le republie 3 fois sur 3.
Lisk : dernier jour pour lancer un transfert par le pont, fiche E100248 (tweet)	Cette échéance préparatoire était déjà laissée ouverte le 23/10. La fermeture de la chaîne, le 02/11, a sa propre fiche (E98520).	Supprimer E100248 : l'échéance fait partie de la fermeture de la chaîne. Les rejeux sont instables (2 sur 3).
LitVM, fiche E3166 rattachée au LTC (tweet)	Une proposition retenue déplace le mainnet LitVM du T4 2026 au T1 2027, d'après la feuille de route officielle de LitVM. Mais LitVM est une couche construite par LiteForge sur Litecoin : selon ta règle du 23/10, un tiers sur la chaîne d'un projet suivi devient lui-même le sujet.	Accepter le report au T1 2027 et garder la fiche : la Litecoin Foundation présente LitVM comme les smart contracts de Litecoin. Si tu tranches « tiers », je supprimerai la fiche à la place.
Velvet : airdrop $VELVET du 10/12 annoncé avec l'époque 13 des Gems (tweet)	Les récompenses de trading payées dans le jeton de la plateforme sont de la promotion (ta décision du 14/10). Mais un airdrop daté est une catégorie valide, et l'airdrop précédent (E591) est publié.	Publier l'airdrop du 10/12 seul, sans l'époque ni les Gems. Je relancerai la source après ton accord.
PancakeSwap : fin des sorties du CAKE depuis opBNB le 23/11 (tweet)	La fermeture d'une route de pont est un élément de produit existant. Mais une date limite qui oblige les détenteurs à agir ressemble à une échéance de migration.	Ne pas publier : c'est une route d'un pont tiers (LayerZero) qui ferme, et le jeton CAKE lui-même ne change pas.
Intégration PROM × Sonvia, rejetée à tort (tweet)	L'image dit en toutes lettres « Integration prom × SONVIA » : c'est le même cas que ta décision SI87122 (Alphio). Le moteur ne la publie qu'une fois sur trois au rejeu.	Relancer la source pour publier l'intégration du 23/10, sans « More updates soon ». Ce cas servira de témoin à la prochaine calibration.
Quatre fiches plus anciennes au cas limite : garde-fou Decred v2.1.7 E99964 (lien), compétence agent Filecoin E98883 (lien), livre blanc MiCA de Sei E100150 (lien), SunSwap × Symbiosis E100124 (lien)	Aucune décision passée ne couvre ces cas : un garde-fou de sécurité nommé, une compétence pour agents, un dépôt réglementaire, un partenariat annoncé par le protocole lui-même.	Les garder (règle « dans le doute, on garde »), sans action.
10 fiches anciennes sans preuve suffisante : LitVM T4 hors proposition, Seeker, DigiDollar, migration SSV, GasFree, portail PancakeSwap, auto-rollover Kamino, RLUSD, arrêt de la L2 Nillion, etc.	Le lien, l'image ou le fil n'ont pas été capturés, donc la source ne permet pas de trancher.	Les garder, sans action. Une seule exception : Nillion E99097 est daté au « 31/12 » à partir de « dans les prochaines semaines » ; je propose de le passer en mois estimé.

2. Sans doute métier

30 actions sur la fenêtre, à appliquer en un seul lot sur ton « go », plus 52 actions sur le stock ancien, séparées :

Fiches créées dans la fenêtre : 8 suppressions et 5 corrections.
Suppressions : une opération entre deux tiers sur Stellar, une vidéo d'un tiers sur Canton, une paire en won pour BMT alors que BMT est déjà coté sur Upbit, une séance de Meridian en doublon de la conférence, l'extension des incitations Aero à Ethereum, l'hébergement d'un nœud Elysium, l'explication vidéo Livepeer, et le doublon de la fin du pont Gravity.
Les 5 corrections portent sur le titre, le temps des verbes et la source de preuve.
Propositions retenues : 3 à accepter (report de Glamsterdam sur Hoodi, burn SKY au 13/09, LitVM au T1 2027) et 3 à refuser (Nillion, ZKsync, PendleLoop). Avant chaque acceptation, je vérifierai sans écrire les fiches liées qui pourraient être touchées.
Sources bloquées : 11 sources à ignorer. Aucune ne contient d'événement.
Stock ancien : 27 suppressions et 25 corrections. C'est la même nature de défauts que celles que tu avais choisi de ne pas toucher le 23/10. Je les applique seulement si tu le dis explicitement.

La liste ligne par ligne, avec le lien et la raison de chaque action, est sur la page détaillée.

3. Moteur

Prompts Expert et réviseur (Core 6807489e), 4 classes d'erreur encore recréées au rejeu :
une séance de la propre conférence du projet publiée à part (Meridian), 3 fois sur 3 ;
des incitations existantes étendues à une nouvelle chaîne (Aero), 3 fois sur 3 ;
une vidéo explicative qui dit « en cours de livraison » publiée comme une sortie (Livepeer), 2 fois sur 2 ;
une application d'un tiers chez un fournisseur (Arcium, Walrus), 3 fois sur 3. Celle-ci dépend de ta décision ci-dessus.

Prochaine calibration à faire avec prompt-calibration. Non testé. - Étape Identity (contrôle de la liste fermée) : quand l'agent choisit un identifiant hors de la liste autorisée, la source est bloquée dès la première fois. C'est arrivé à 4 sources en 3 jours ; aucune ne contenait d'événement. Correction proposée : traiter ce cas comme les autres sorties invalides du modèle, avec une seule nouvelle tentative avant le blocage. Non testé. - Brouillon manquant (réponse de l'Expert) : dans 3 rejeux sur 54 (Gravity, Livepeer), l'Expert a omis le brouillon d'un élément publiable, et le passage a échoué au lieu d'être réparé. Je ne l'ai pas vu en production dans la fenêtre. À surveiller. Non testé. - Déjà corrigé par les changements du 24/10, d'après les rejeux : - opération de tiers sur Stellar : 0 republication sur 3 ; - vidéo d'un tiers sur Canton : 0 sur 3 ; - doublon de la fin du pont Gravity : le moteur met maintenant à jour E99303, 3 fois sur 3 ; - rapprochement invalide : 1 seule source bloquée, avant le déploiement ; aucune après.

Détail technique

Périmètre et preuves

Fenêtre : 2026-10-23T11:32:12.724106Z → 2026-10-26T11:13:01.603814Z (DB now() au gel). Inventaire des files capturé au même instant.
1 835 sources, 1 891 tentatives, 1 817 ledgers. Décisions finales : REJECT 1 162, FILTERED 468, DUPLICATE 96, MIXED 54, PUBLISH 24, UPDATE 11, CANCEL 1, SKIPPED_MANUAL 8, sans décision (bloquées) 11.
Relecture des décisions de source : PASS 1 804, FINDING 31, EXCLUDED 0, PENDING 0.
Fiches : 199, dont 42 créées dans la fenêtre. Relecture des champs : PASS 105, FINDING 90, EXCLUDED 4, PENDING 0. Brouillons : 0. Revues basse confiance en attente : 0.
Doublons : 42 fiches scannées, 1 554 paires : DISTINCT 1 549, AMBIGUOUS 5, DUPLICATE 0. Les 5 paires ambiguës sont tracées dans le registre : Gravity ×2, Meridian, JST, Aero.
Propositions retenues (global) : 6. Revues de source entière : 0.
Reprises et échecs : 55 sources. 37 reprises attendues et terminées. 18 sources à ignorer : 7 déjà ignorées le 23/10 et 11 bloquées dans la fenêtre. Les décomptes sont faits par famille et phase d'échec depuis la dernière relance manuelle.
Incident fournisseur : génération 128, x_timeline/coin_home_timeline, llm_capacity/expert. 1 cycle de pause, 1 alerte OPENED et 1 alerte RECOVERED livrées (165779/165781). Conforme.
Versions live : Core 1nswAXAfsck9e9uC 6807489e (publiée = éditable), Processor awrB2Ymt3iZPp14k 163c7d7d, o4cmp66lDjKDOF4v cf9dedfe, API 936abc6. Avant le 24/10 07:36 UTC : Core 9862a18f et API f09d3b9.
Production mutated: no.

Rejeux

Autorisés par Anthony le 26/10 : plafond 1,50 $. 54 passages (18 cas × 3), sans écriture : garde SQL en lecture seule, persistance bloquée, fiches candidates figées. 367 appels LLM et 53 embeddings ; coût visible 0,90 $.
Témoins : CoinDepo republié 3 fois sur 3, Holo × Kwaxala 3 sur 3, arrêt Gravity 1 passage terminé (2 échecs « brouillon manquant »).
Limite : les rejeux de BMT (SI130462) sont faussés, car BMT n'est plus suivi ; le rejet vient de l'ancrage, pas du rapprochement.

Constats par famille

Faux PUBLISH dans la fenêtre : E100218, E100220, E100236, E100237, E100244, E100246, E100247, E100250. Cas douteux : E100229, E100232, E100233, E100234, E100248, E100249.
UPDATE erronés : E229 a reçu à confiance 100 une note d'interview non datée sur CantonBFT (SI130345) : description à restaurer. E100047, E98805 et E100223 ont été réécrits avec une perte d'information. Les propositions retenues sur E100162 (×3), E99097 et E100144 sont à refuser.
Faux négatifs : PROM × Sonvia (règle déjà décidée). Cas douteux : Velvet, CAKE, Distracted.
Indicateur de suivi : BMT et ABT étaient suivis au moment de la décision (ancrage présent dans le ledger), puis ne l'étaient plus. Ce n'est pas un défaut du moteur.
Sources bloquées (11) :
4 par la liste fermée d'Identity ;
4 par des échecs de téléchargement d'images, tous entre 09:52 et 10:08 UTC le 26/10 ;
1 par un délai dépassé du fallback média ;
1 par un source_post_id hors contexte ;
1 par un rapprochement invalide, avant le correctif.

Aucune ne contenait d'événement de calendrier.

Champs persistés

Chaque fiche exportée a été relue contre la source et le contrat de champs. Les 90 constats et les 4 exclusions sont reliés à un marqueur du registre ci-dessous.

Lot « sans doute métier », ligne par ligne

Fenêtre 23/10 → 26/10 et files (30)

Action	Fiche / source	Lien	Raison
Supprimer	E100218 TheHUB Node Deployment	tweet	Placing the chain's own node in a colocation facility is internal infrastructure with no investor-facing state change and no completion moment; the builder perk is a commercial side detail. The valid cores of this source are already held by E98847 and E100219.
Supprimer	E100220 First Institutional Repo	tweet	The transition belongs to Ascend/M1X (untracked); Stellar's own operation or capability does not change, it only hosts a demonstration deal. Official @StellarOrg amplification does not make XLM impacted.
Supprimer	E100236 Builder Engine Delivery	tweet	The only timing is an ongoing-delivery caption in an educational 'self-sovereign' explainer video; no launch moment or release is stated. No retainable dated core in the source.
Supprimer	E100237 Townhall Q&A	tweet	The townhall is a session inside Meridian on the same day as the existing E99613; it is a part of that event, not an independent transition. Its Q&A detail can enrich E99613's description instead.
Supprimer	E100244 Bridge Access Ends	tweet	Duplicate of E99303 (same Gravity Alpha bridge end); keep E99303 corrected to 25/10 20:00 PDT with the official @GravityChain proof. Replays now UPDATE E99303 3/3.
Supprimer	E100246 CIP-0129 Discussion	tweet	Content release on a third-party channel discussing a proposal; no source-stated purpose of presenting Canton team updates and no timing for the burn proposal itself.
Supprimer	E100247 Upbit KRW listing	tweet	E97472 (Upbit listing, 21/08) already carries bubblemaps among its coins, i.e. BMT already had spot access on Upbit (BTC/USDT markets); a KRW pair is a new market on the same venue, not first access. BMT is also untracked in the snapshot.
Supprimer	E100250 Ethereum pool incentives live	tweet	Aero's existing gauge/incentive mechanism is extended to Ethereum pools (the UI already lists Base and Robinhood Chain pools); no new program, season or first protocol deployment is stated.
Corriger	E100216 SoDEX Builder Codes	tweet	Impact summary frames the event around the Buildathon prize pool and finalists instead of the Builder Codes capability. Fix: Impact summary: 'SoSoValue launches SoDEX Builder Codes, letting builders earn ongoing Builder Fee revenue from their products. No direct SOSO token mechanism is announced, so the effect stays limited.'
Corriger	E100223 Buyback & burn upgrade	tweet	Description not in present tense. Fix: Rewrite: 'The JST Buyback & Burn mechanism moves to a model anchored in recurring ecosystem revenue. About $20.34M in surplus reserves will be deployed in phases from Q4 2026 while a minimum $50M reserve is kept.'
Corriger	E100225 Largest Perp DEX Merges	tweet	Title/description use a superlative and never name the merged party; third-party proof link. Fix: Title 'gmTrade Merger'; description 'gmTrade merges with GMX on Solana.'; set link to the official GMX post.
Corriger	E100226 Builder Fees live	tweet	Third-party news proof link and past-tense description. Fix: Description 'GMX Builder Fees go live on Solana, letting developers earn fees on trades routed through their apps.'; link to GMX official post.
Corriger	E100242 Pi Desktop 0.6.4 Release	tweet	Title contains the project name/ticker 'Pi'. Fix: Title 'Desktop App 0.6.4' or 'SoloHost Remote Access'.
Accepter la proposition retenue	E3166 · SI130249	tweet	SI130249: @LTCFoundation quoting @LitecoinVM; the attached official LitVM roadmap image (OCR) reads 'Q1 2027 - Mainnet Launch' (Q4 2026 now carries V2/TGE/Audits). E3166 (LitVM smart-contract mainnet, Q4 2026 from a July LTC Foundation post) is superseded by the project's own newer roadmap. Accept the move to Q1 2027 estimated; no other field changes (no-write Cascade preview required).
Accepter la proposition retenue	E98533 · SI129900	tweet	SI129900: official Sky Frontier Foundation monthly report linked by @SkyEcosystem states 'On September 13, the first SKY burn was completed'. E98533 is dated 14/09 from the announcement post (14/09 13:22 UTC). Official source, one-day correction of a past event, no other change. Accept (low stakes; Cascade preview required).
Refuser la proposition retenue	E99097 · SI129772	tweet	SI129772: 'Still holding NIL or ETH on Nillion L2? start bridging today' is a user-task reminder (Expert: no timing). The proposal rewrites E99097's description and drops the shutdown facts (L2 rewards claim window). No calendar change. Reject.
Accepter la proposition retenue	E99120 · SI130194	tweet	SI130194: Lido reports that on ACDE #248 Ethereum core developers postponed the Glamsterdam upgrade on the Hoodi testnet (previously 26/10) with no new date, and Lido prepares a rollback vote. Postponement without a new date = CANCEL (MOVED_NO_DATE). E99120 should leave the calendar today; a new event when a new date is set. Accept the CANCEL (no-write Cascade preview required).
Refuser la proposition retenue	E100144 · SI130221	tweet	SI130221: '@money2020' photos of a ZKsync session at a multi-project conference (attendance). The proposal rewrites E100144's description with conference wording; no calendar change. Reject.
Refuser la proposition retenue	E100162 · SI130565	tweet	SI130565: RT of a third-party explainer (@0xCharlie_DeFi). Reconciliation moved E100162 from 22/10 to 23/10 because a 23/10 post says 'now live' for Loop-to-Long Base tokenized stocks; the 22/10 02:01 UTC official 'Introducing PendleLoop' post is the launch. Earliest official source controls; reject the redate.
Ignorer la source bloquée	SI129760	tweet	Source 129760: Aave RT of a third-party post: Sentora curated markets live on Aave V4 (already calendared as E100204, 22/10). Reconciliation PRIMARY_SOURCE_NOT_CONTRIBUTOR twice under API f09d3b9 (before the 24/10 salvage fix). reconciliation_invalid_output/reconciliation 2/2 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI130030	tweet	Source 130030: Ronin 'FT: @0xSunflowerLand' wrapper (PoD leaderboard spotlight). Identity selected an ID outside the allowed set (blocked at first occurrence). core:identity_closed_set_violation/identity 1/5 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI130047	tweet	Source 130047: Reental commentary on BNB tokenization metrics. Expert timeout then Identity closed-set violation. expert_transient/expert 1/2 -> RETRY; core:identity_closed_set_violation/identity 1/5 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI130064	tweet	Source 130064: Sky RT of a Grove podcast clip (media appearance). Identity closed-set violation. core:identity_closed_set_violation/identity 1/5 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI130211	tweet	Source 130211: ArtificiallyInu meme on NVDA mentions. Media LLM timeout (Baseten 180 s) twice. media_transient/media 2/2 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI130987	tweet	Source 130987: Solana weekly newsletter recap (Alpenglow already shipped, JPM funds, xStocks metrics). Identity closed-set violation. core:identity_closed_set_violation/identity 1/5 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI131291	tweet	Source 131291: Shuffle RT of a user casino win. Expert source_post_id outside the supplied context twice. expert_transient/expert 2/2 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI131474	tweet	Source 131474: Bitget MCAT Simple Earn 30% APR (promotion). Source image download failed twice (burst 26/10 09:52-10:08 UTC). media_transient/media 2/2 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI131478	tweet	Source 131478: Ronin PoD Season 6 halfway leaderboard (metric). Source image download failed twice (same burst). media_transient/media 2/2 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI131484	tweet	Source 131484: Toobit Separate Isolated Margin on futures (derivative setting). Expert schema failure then image download failed twice (same burst). expert_transient/expert 1/2 -> RETRY; media_transient/media 2/2 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.
Ignorer la source bloquée	SI131492	tweet	Source 131492: RaveDAO x ADE industry mixer recap (ceremony/attendance). Source image download failed twice (same burst). media_transient/media 2/2 -> BLOCK. Bounded and alerted; no calendar claim at risk. Recommendation: exact skip.

Stock ancien (seulement sur accord explicite) (52)

Action	Fiche / source	Lien	Raison
Supprimer	E200 AxCNH Incentives	tweet	The source says the incentives are 'continuing', i.e. an extension of an existing reward campaign on one Unitus market, not a new program or season. No other timed claim exists.
Corriger	E229 Logical Sync Upgrades	tweet	Restore the pre-update description ('Logical Synchronizer Upgrades are live on Canton Network with the Canton 3.5 release, allowing major protocol upgrades to complete automatically without complex data migration or application disruption.') and drop the CantonBFT/TPS text from description and impact summary; keep date 29/06/2026 and proof 2071682867076477049.
Supprimer	E1194 Institutional TRX Staking	tweet	A custodian adding TRX to its existing institutional staking service is an asset added to a third party's existing product; TRON's own staking is unchanged. The stored proof is a factless emoji reply, and the title contains the ticker.
Supprimer	E11369 Guardian Agent Blackbox	tweet	The product belongs to umanitek and only uses OriginTrail's existing knowledge graph; OriginTrail's own operation does not change, so TRAC is context, not subject.
Supprimer	E16363 Console Onboarding	tweet	As stored, the event is an onboarding redesign of the existing Akash Console (fewer setup steps), an interface change rather than a new protocol capability; the source tweet is a bare link and shows no other dated transition.
Supprimer	E22065 Gacha Launch	tweet	BONKUJI is a third-party gacha app; BONK's own state does not change, and the proof is a factless reply with no timing.
Supprimer	E36329 rFLR Rewards Live	tweet	rFLR is Flare's ongoing incentive program with recurring distributions; this post announces another claim batch, not a new program or season.
Supprimer	E53440 Simple Mode Trading Bots	tweet	A trading-bot feature inside OKX's existing app does not name or change OKB; it is both a wrong identity and an existing-product item.
Supprimer	E61402 wFIAT Stablecoins Live	tweet	The transition is Ripio's stablecoins deploying on Celo; Celo's own operation does not change, so the CELO attachment is wrong and Ripio is the subject.
Supprimer	E95789 FC Barcelona Deal Renewed	tweet	A renewal of a corporate sports sponsorship by the exchange is a brand deal, not a crypto project state change, and the stored text does not name WBT.
Supprimer	E96239 Windrose Server Hosting	tweet	One more game template in Flux Cloud's existing hosting catalog is a catalog addition, not a new capability of the Flux network.
Supprimer	E96526 Core Security Release	tweet	The release names only security updates in a patch version, with no new capability or network change.
Supprimer	E96647 Beta Feature Update	tweet	The listed items are interface features of an existing beta app; 'clearer staking tools' is a UI change, not a new staking program, and the source is a third-party RT.
Supprimer	E96817 1.6B Supply Milestone	tweet	A supply threshold crossed by a continuous burn is a metric milestone, not a discrete burn operation, and the source is a third-party projection.
Supprimer	E97386 LLY Stock Listing	tweet	A third-party tokenized stock arriving on Solana does not change Solana; no tracked direct subject remains.
Corriger	E97472 Upbit Listing	tweet	Set description to 'Upbit opens GWEI trading in BTC and USDT markets at 13:00 KST.' and keep only GWEI on this event; create/verify a separate entry for tracked NIL; drop untracked BMT/BICO links.
Supprimer	E97646 Dynamic Terminal Live	tweet	As stored, the 'terminal' is a unified interface over DAMM v2's existing operations; no new underlying transaction or market capability is named, and the proof is a truncated personal RT.
Supprimer	E97726 sUSDD Incentives Launch	tweet	USDD rewards stacked on an existing Pendle pool are a pool incentive campaign on another project's token, not a Pendle economic program; PENDLE's own state is unchanged.
Supprimer	E97960 Core v26.8 Release	tweet	The release names only dependency updates (Tor, OpenSSL) and unspecified hardening; no new capability or protocol change for users. Same family as Mina 4.0.1 / TRON 4.8.2.3 maintenance releases.
Supprimer	E98011 USDT0 Integration	tweet	The announcer is USDT0 and the transition is USDT0's deployment on Stellar; Stellar's own operation does not change. The only stored coin is XLM, so the event is attached to a context chain; the valid core would be a USDT0 event, which is not tracked here.
Supprimer	E98072 Pineapple Mortgages Onchain	tweet	The transition is a third party (Pineapple) issuing tokenized mortgages on Injective plus a cumulative-value milestone; Injective's own functioning does not change and no partnership is stated by Injective. INJ is context, Pineapple untracked.
Supprimer	E98351 Flex USDC Vault Live	tweet	A single new vault on Yearn's existing vault platform, announced by Flex (a third party whose markets the vault lends to), is a catalog addition, not a new Yearn capability. The collateral teaser has no timing.
Supprimer	E98364 First Cross-Border Payment	tweet	The subject is U.S. Bank's own stablecoin pilot; Stellar's operation does not change, so XLM is context and the bank is not a tracked crypto subject. Title/description also cite a 'first cross-border payment' absent from the captured source.
Supprimer	E98800 OP Stack payment cycle	tweet	Two third parties completed a test payment cycle using OP Stack software; Optimism's own operation does not change and no live product launch or Optimism partnership with timing is stated. Title also contains the ticker 'OP'.
Supprimer	E99072 OnRe Fixed Rates	tweet	Kamino fixed-rate borrowing already existed (E98876, 22 Sep, auto-rollover of fixed-rate positions), so enabling it in one more market (OnRe/ONyc) is a handled-item addition, not a new capability.
Corriger	E99303 Alpha Mainnet bridge ends	tweet	Fold E100244 into 99303 (or vice versa): one event 'Alpha Mainnet bridge ends', date 25/10/2026 with time 8:00 PM PDT, official @GravityChain proof 2113794400119574580, present-tense description without repeated date; delete the duplicate. If reviewers judge 31 Oct asset-access deadline distinct, keep 99303 but relink/rewrite it.
Corriger	E99613 Meridian 2026 Conference	tweet	Relink 99613 proof to @StellarOrg 2113726913541779861; optionally mention the SDF townhall Q&A in its description; delete E100237 as duplicate part of 99613.
Supprimer	E99678 Vaults on Monad, Robinhood	tweet	Existing Plume vault products (nOPAL, FACTOR) become reachable on additional chains/venue; this is coverage of an existing product, not a new Plume capability or first spot access of PLUME.
Supprimer	E99682 Execution Layer Live	tweet	The launch is RAVN's own execution layer, announced by RAVN, routing through existing THORChain swaps; THORChain's operation does not change. RAVN is the subject and is untracked.
Supprimer	E99691 TokenPocket Integration	tweet	A third-party wallet, announcing on its own account, routes swaps through SunSwap; SunSwap's own operation does not change and no partnership is announced by Sun. The subject is TokenPocket's wallet feature.
Corriger	E100139 Referral Staking Cycle 4	tweet	Title e.g. 'Staking Cycle 4'; description: 'Cycle 4 of the Referral Staking Program begins, adding minimum LP fee eligibility for stakers and direct compounding of USDC rewards into staked MET.' (drop top-referrer and retroactive bonuses).
Supprimer	E100145 eTAO Update Discussion	tweet	Novelty Search is Opentensor's own recurring show; the source schedules an episode discussing an already-made protocol update, which the 23/10 decision explicitly classes as routine. Published 21/10 under the older rule, but it does not survive current policy; eTAO itself is not this event.
Corriger	E38742 Waypoint Migration	tweet	The description adds an unsupported 'or lose access' consequence. Fix: 'Ronin Waypoint's migration grace period ends at 11:00 ET / 15:00 UTC / 22:00 VN, after which Waypoint is fully sunset and the migration to Ronin Stash is complete.'
Corriger	E43879 Mainnet Launch	tweet	The proof URL does not show the October 2026 timing or the described launch facts; the timing-bearing 10-23 source is not the proof. Fix: Set the link to the post that states the October launch timing (likely 2113594231541715052), after checking it.
Corriger	E49046 Metaplex Genesis Liquidity	tweet	Legacy event with the project name in the title and a quoted description. Fix: Retitle 'Genesis Liquidity Grants' and remove the quote marks (or leave as untracked legacy).
Corriger	E96945 USDG Market Launch	tweet	The title describes the first market rather than the X Layer deployment. Fix: Retitle 'X Layer Deployment'; description 'Pendle deploys on X Layer, opening its first market with USDG, supporting PT-USDG, YT-USDG and LP strategies.'
Corriger	E96947 NEAR Earn Vaults	tweet	Title contains the main project ticker. Fix: Retitle 'Earn Vaults Launch'.
Corriger	E97361 Buyback Program	tweet	Description written in future tense. Fix: 'WINkLink allocates 100% of oracle service revenue to quarterly WIN buybacks, with burn data published on-chain.'
Corriger	E97677 V3 Launch	tweet	Succinct (PROVE) attached as coin without being named in the source. Fix: Remove PROVE from coins and drop the SP1/PROVE clause from the impact summary.
Corriger	E98286 0x02 CSM Mainnet	tweet	Impact summary invents a 'capital multipliers' incentive consequence. Fix: Impact: 'The 0x02 CSM lets independent operators run Lido validators with up to 2,048 ETH, widening permissionless access to Lido staking.'
Corriger	E98821 cUSDT live on Ethereum	tweet	Host chain ETH attached as coin to a Zama product launch. Fix: Remove ETH from coins and drop the ETH sentence from the impact summary.
Corriger	E99081 Alpenglow live on devnet	tweet	Official proof replaced by a less authoritative third-party commentary post. Fix: Restore the official Anza/Solana devnet activation post as link.
Corriger	E99087 Offchain Support Ends	tweet	Support wind-down dated from a reminder post's publication date instead of the stated end of support. Fix: Date the end of support (~25 Oct, estimated) from official dates; present-tense description 'LayerZero DVN and Executor offchain support ends for low-activity chains...'.
Corriger	E99122 Burn CIP lands	tweet	Impact summary describes an unverified burn-schedule mechanic unrelated to the traffic-burn description. Fix: Impact: 'CIP-0129 makes every mainnet synchronizer burn Canton Coin to pay for traffic, adding a usage-linked burn for CC.'; re-anchor date/proof to the official approval post.
Corriger	E99515 v2.22.0 Upgrade	tweet	Impact summary adds unsourced consequences (legacy wallets, loss risk, repositioning). Fix: Impact: 'Terra upgrades to v2.22.0 and temporarily freezes affected wallets pending a Terra Governance decision.'
Corriger	E99563 Mainnet Launch	tweet	Official proof replaced by a personal account post; description adds nothing beyond the title. Fix: Relink to https://x.com/DuskFoundation/status/2113150216186794150; description: 'Dusk Domains gives each Dusk address one readable .dusk name, from 10 DUSK a year.'
Corriger	E99689 Revenue Share Launch	tweet	Description/impact carry later recap metrics instead of describing the launch. Fix: Description: 'THORChain activates REVSHARE, paying SwapKit 20% of the fees it earns on swaps SwapKit routes, so the integrator can lower its fees.'; drop metrics from impact.
Corriger	E99855 Alpha V6 Vote Passed	tweet	Title/description rewritten to the vote outcome instead of the neutral vote event. Fix: Title 'Alpha V6 Upgrade Vote'; description: 'AZTEC holders vote on the Aztec Alpha V6 upgrade payload, bringing security improvements and faster Ethereum-Aztec transfers.'
Corriger	E99869 Season 2 Claims	tweet	Description converts the stated 11 AM ET time into an unlabelled 15:00. Fix: Description: 'Season 2 airdrop claims open at 11 AM ET on Arbitrum with no lockup or vesting; the allocation totals 225 million CHIP (2.25% of supply).'
Corriger	E100001 5th Buyback & Burn	tweet	Event dated 16 Oct while the completion announcement is 17 Oct. Fix: Set date to 17 Oct 2026 unless the linked on-chain burn is dated 16 Oct.
Corriger	E100047 Unity Submissions Begin	tweet	Description repeats the event date and leads with a preparatory validation step rather than the submissions opening. Fix: Description: 'Numerai tournament submissions open on Unity, where agents can engineer their own features.'
Corriger	E100129 Agentic copy trading live	tweet	Impact summary asserts a significant utility boost not in the source and omits the private-beta restriction. Fix: Impact summary: 'Virtuals App adds agentic copy trading through Butler in private beta, executing copied trades across chains within user limits. Access is limited to a private beta, so near-term effect on VIRTUAL is bounded.'

Registre des constats

Une ligne par identifiant du registre de score ; le détail (source, raisonnement, critique, attendu) est dans les paquets du dossier.

FP-129723-0-UPDATE · faux positif 129723:0:UPDATE

FP-129772-0-UPDATE · faux positif 129772:0:UPDATE

FP-129814-0-PUBLISH · faux positif 129814:0:PUBLISH

FP-129827-0-PUBLISH · faux positif 129827:0:PUBLISH

FP-129858-0-UPDATE · faux positif 129858:0:UPDATE

FP-130221-0-UPDATE · faux positif 130221:0:UPDATE

FP-130227-0-PUBLISH · faux positif 130227:0:PUBLISH

FP-130279-0-PUBLISH · faux positif 130279:0:PUBLISH

FP-130345-0-UPDATE · faux positif 130345:0:UPDATE

FP-130370-1-PUBLISH · faux positif 130370:1:PUBLISH

FP-130387-0-PUBLISH · faux positif 130387:0:PUBLISH

FP-130462-0-PUBLISH · faux positif 130462:0:PUBLISH

FP-130565-0-UPDATE · faux positif 130565:0:UPDATE

FP-130710-0-PUBLISH · faux positif 130710:0:PUBLISH

SRC-129760 · exclu du score : TECHNICAL WATCH: watch-level, contained (held/no-write) or on a linked historical event; recorded without score loss.

SRC-129772 · exclu du score : Outcome counted as FALSE_POSITIVE FP-129772-0-UPDATE.

SRC-129814 · exclu du score : Outcome counted as FALSE_POSITIVE FP-129814-0-PUBLISH.

SRC-129827 · exclu du score : Outcome counted as FALSE_POSITIVE FP-129827-0-PUBLISH.

SRC-129858 · exclu du score : Outcome counted as FALSE_POSITIVE FP-129858-0-UPDATE.

SRC-129860 · exclu du score : FIELD_DEFECT WATCH: watch-level, contained (held/no-write) or on a linked historical event; recorded without score loss.

SRC-129907 · défaut content/minor sur 129907:0:PUBLISH

SRC-129956 · exclu du score : FIELD_DEFECT WATCH: watch-level, contained (held/no-write) or on a linked historical event; recorded without score loss.

SRC-129983 · exclu du score : FALSE_PUBLISH AMBIGUOUS: second pass POLICY_UNCLEAR; human decision required, no score loss asserted.

SRC-130008 · exclu du score : ArcBlock (ABT) was tracked at decision time (coin_resolution tracked_coin_ids=[arcblock], has_tracked_anchor=true); x_event_monitoring changed afterwards. Not an engine defect (ROOT-TRACKING-FLAG-DRIF

SRC-130022 · exclu du score : FALSE_PUBLISH MINOR: second pass POLICY_UNCLEAR; human decision required, no score loss asserted.

SRC-130171 · exclu du score : FALSE_PUBLISH AMBIGUOUS: second pass POLICY_UNCLEAR; human decision required, no score loss asserted.

SRC-130221 · exclu du score : Outcome counted as FALSE_POSITIVE FP-130221-0-UPDATE.

SRC-130227 · exclu du score : Outcome counted as FALSE_POSITIVE FP-130227-0-PUBLISH.

SRC-130279 · exclu du score : Outcome counted as FALSE_POSITIVE FP-130279-0-PUBLISH.

SRC-130310 · exclu du score : FALSE_PUBLISH MINOR: first-pass finding overturned or downgraded by the second pass (KEEP_LOW_IMPACT).

SRC-130316 · défaut content/minor sur 130316:0:UPDATE

SRC-130319 · défaut content/minor sur 130319:0:PUBLISH

SRC-130340 · FALSE_NEGATIVE

SRC-130345 · exclu du score : Outcome counted as FALSE_POSITIVE FP-130345-0-UPDATE.

SRC-130370 · exclu du score : Outcome counted as FALSE_POSITIVE FP-130370-1-PUBLISH.

SRC-130387 · exclu du score : Outcome counted as FALSE_POSITIVE FP-130387-0-PUBLISH.

SRC-130462 · exclu du score : Outcome counted as FALSE_POSITIVE FP-130462-0-PUBLISH.

SRC-130470 · exclu du score : Velvet airdrop of 10/12 inside an epoch campaign: trading-reward promotion (10-14) vs airdrop class; human decision required.

SRC-130540 · exclu du score : FALSE_PUBLISH AMBIGUOUS: second pass POLICY_UNCLEAR; human decision required, no score loss asserted.

SRC-130556 · exclu du score : FALSE_PUBLISH AMBIGUOUS: second pass POLICY_UNCLEAR; human decision required, no score loss asserted.

SRC-130563 · exclu du score : Arcium-protected third-party game: provider-vs-third-party boundary still open (10-14 vs 22-23/10 decisions); also covered by E100249 from SI130556. Human decision required.

SRC-130710 · exclu du score : Outcome counted as FALSE_POSITIVE FP-130710-0-PUBLISH.

SRC-131153 · défaut content/minor sur 131153:0:UPDATE

SRC-131282 · exclu du score : CAKE opBNB bridge-out deadline: route removal on an existing bridge vs migration deadline; human decision required.

SRC-131448 · défaut content/minor sur 131448:0:UPDATE

FLD-200 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The source says the incentives are 'continuing', i.e. an extension of an existing reward campaign on one Unitus market

FLD-229 · exclu du score : Event outcome already counted as FALSE_POSITIVE; field defect not double counted.

FLD-1194 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: A custodian adding TRX to its existing institutional staking service is an asset added to a third party's existing pro

FLD-1427 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-3166 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): The only captured proof is a truncated third-party news RT about the 2027 halving; neither the Q4 2026 bound nor whether LitVM is a Litecoin-o

FLD-11369 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The product belongs to umanitek and only uses OriginTrail's existing knowledge graph; OriginTrail's own operation does

FLD-16363 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: As stored, the event is an onboarding redesign of the existing Akash Console (fewer setup steps), an interface change

FLD-22065 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: BONKUJI is a third-party gacha app; BONK's own state does not change, and the proof is a factless reply with no timing

FLD-36329 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: rFLR is Flare's ongoing incentive program with recurring distributions; this post announces another claim batch, not a

FLD-38742 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-43879 · défaut provenance/minor sur 129717:0:UPDATE

FLD-49046 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-53440 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: A trading-bot feature inside OKX's existing app does not name or change OKB; it is both a wrong identity and an existi

FLD-57036 · exclu du score : Named proof limitation or demonstrably non-defect lint: Lints missing_impact/missing_impact_summary are not defects: legacy import (confidence NULL), where impact is NULL by legacy design. ApeX Omni i

FLD-61402 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The transition is Ripio's stablecoins deploying on Celo; Celo's own operation does not change, so the CELO attachment

FLD-95077 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): Legacy event on an untracked coin with no stored source; whether a Seeker-specific app with exclusive features is a new product or just new di

FLD-95789 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: A renewal of a corporate sports sponsorship by the exchange is a brand deal, not a crypto project state change, and th

FLD-96239 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: One more game template in Flux Cloud's existing hosting catalog is a catalog addition, not a new capability of the Flu

FLD-96526 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The release names only security updates in a patch version, with no new capability or network change.

FLD-96647 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The listed items are interface features of an existing beta app; 'clearer staking tools' is a UI change, not a new sta

FLD-96817 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: A supply threshold crossed by a continuous burn is a metric milestone, not a discrete burn operation, and the source i

FLD-96945 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-96947 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-96994 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): The tweet text gives no launch or activation timing, and the stored description only says the locks are 'offered'; the media (not captured) is

FLD-97138 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): The stored event dates a migration reminder to the publication day without any transition timing, which is unsupported as stored; the uncaptur

FLD-97361 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-97386 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: A third-party tokenized stock arriving on Solana does not change Solana; no tracked direct subject remains.

FLD-97472 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-97646 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: As stored, the 'terminal' is a unified interface over DAMM v2's existing operations; no new underlying transaction or

FLD-97677 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-97726 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: USDD rewards stacked on an existing Pendle pool are a pool incentive campaign on another project's token, not a Pendle

FLD-97960 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The release names only dependency updates (Tor, OpenSSL) and unspecified hardening; no new capability or protocol chan

FLD-98011 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The announcer is USDT0 and the transition is USDT0's deployment on Stellar; Stellar's own operation does not change. T

FLD-98072 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The transition is a third party (Pineapple) issuing tokenized mortgages on Injective plus a cumulative-value milestone

FLD-98272 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): The only source is a non-official commentator; 'now supports' is a durable state, not proof the feature started on 08 Sep, and the official Bi

FLD-98286 · défaut impact/minor sur 129897:0:UPDATE

FLD-98351 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: A single new vault on Yearn's existing vault platform, announced by Flex (a third party whose markets the vault lends

FLD-98364 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The subject is U.S. Bank's own stablecoin pilot; Stellar's operation does not change, so XLM is context and the bank i

FLD-98766 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): An official 'Introducing' with 'Accessible via Binance Wallet' supports a same-day launch reading, but with no project yet available ('first p

FLD-98800 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: Two third parties completed a test payment cycle using OP Stack software; Optimism's own operation does not change and

FLD-98821 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-98876 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): Auto-rollover is plausibly a new protocol capability (retainable core), but the captured text has no live/now/today wording and the 22 Sep dat

FLD-98883 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): An official agent skill that wraps the existing Warm Storage upload can be read as developer tooling/interface over an existing function (excl

FLD-98885 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): The captured source contains only a link, so neither the planned-vs-executed status nor any timing can be verified; 'planned for deployment' i

FLD-98949 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99072 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: Kamino fixed-rate borrowing already existed (E98876, 22 Sep, auto-rollover of fixed-rate positions), so enabling it in

FLD-99081 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99087 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99097 · exclu du score : Event outcome already counted as FALSE_POSITIVE; field defect not double counted.

FLD-99122 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99303 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99363 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99515 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99563 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99578 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99613 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99678 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: Existing Plume vault products (nOPAL, FACTOR) become reachable on additional chains/venue; this is coverage of an exis

FLD-99682 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: The launch is RAVN's own execution layer, announced by RAVN, routing through existing THORChain swaps; THORChain's ope

FLD-99689 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99691 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: A third-party wallet, announcing on its own account, routes swaps through SunSwap; SunSwap's own operation does not ch

FLD-99855 · défaut content/minor sur 130237:0:UPDATE

FLD-99869 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-99964 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): Unlike Verge's unnamed 'hardening', this version names a concrete new node behavior (halt on impossible spends) that would have stopped a prio

FLD-100001 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-100047 · exclu du score : Same unit/family 130316:0:UPDATE/content already counted under SRC-130316; no double counting.

FLD-100079 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-100086 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-100124 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): Unlike 99691, the announcer is SunSwap itself, framing a strategic partnership, which the 10-14 decision treats as a valid same-day event; but

FLD-100129 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-100134 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-100139 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-100145 · exclu du score : Deletion recommended for a linked/historical event outside window decision units: Novelty Search is Opentensor's own recurring show; the source schedules an episode discussing an already-made protocol

FLD-100149 · exclu du score : Field defect on a linked/historical event not created or mutated in the window; data recommendation, no window score loss.

FLD-100150 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): The tweet is link-only, so the exact framing (regulatory milestone vs a third-party exchange's disclosure filing for its listing) cannot be ch

FLD-100216 · défaut impact/minor sur 129752:0:PUBLISH

FLD-100218 · exclu du score : Event outcome already counted as FALSE_POSITIVE; field defect not double counted.

FLD-100219 · exclu du score : Named proof limitation or demonstrably non-defect lint: Persisted link is a TheHUB post and the rendered source text is only a t.co link (linked MIXED source 129814 has empty text), so the 'network up

FLD-100220 · exclu du score : Event outcome already counted as FALSE_POSITIVE; field defect not double counted.

FLD-100223 · défaut content/minor sur 129860:0:PUBLISH

FLD-100224 · exclu du score : Named proof limitation or demonstrably non-defect lint: Sky Q3 report + Foundation insights call, month precision Oct 2026 estimated; source text is only a t.co link (MIXED source 129900 empty), so wh

FLD-100225 · exclu du score : Same unit/family 129907:0:PUBLISH/content already counted under SRC-129907; no double counting.

FLD-100226 · défaut provenance/minor sur 129907:1:PUBLISH

FLD-100230 · exclu du score : First-pass deletion proposal overturned by the second pass (KEEP).

FLD-100234 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): Read as a partnership announced by Perceptron, it is a dated Walrus event; read as a third-party app adopting a storage provider still in prog

FLD-100236 · exclu du score : Named proof limitation or demonstrably non-defect lint: Persisted proof post only says Livepeer's builder stack is self-sovereign; the 'builder engine is being delivered' claim must come from the thre

FLD-100241 · exclu du score : First-pass deletion proposal overturned by the second pass (KEEP_LOW_IMPACT).

FLD-100242 · exclu du score : Same unit/family 130319:0:PUBLISH/content already counted under SRC-130319; no double counting.

FLD-100245 · exclu du score : First-pass deletion proposal overturned by the second pass (KEEP).

FLD-100246 · exclu du score : Event outcome already counted as FALSE_POSITIVE; field defect not double counted.

FLD-100247 · exclu du score : Event outcome already counted as FALSE_POSITIVE; field defect not double counted.

FLD-100248 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): Preparatory deadline of the already-listed chain closure E98520; humans explicitly left this boundary open.

FLD-100249 · exclu du score : POLICY_UNCLEAR (doubt rule, keep pending human decision): Arcium is the randomness/compute provider, not the host chain (Solana), so the 10-14 provider rule supports keeping; but the transition is a t

FLD-100250 · exclu du score : Event outcome already counted as FALSE_POSITIVE; field defect not double counted.

FLD-100254 · exclu du score : Severity WATCH: watch-level; no score loss asserted.

PAIR-326-100250 · exclu du score : Pair AMBIGUOUS: E100250 recommended for deletion (counted as FALSE_POSITIVE).

PAIR-99303-100244 · exclu du score : Pair AMBIGUOUS: human check, no score loss asserted.

PAIR-99303-100245 · exclu du score : Pair AMBIGUOUS: human check, no score loss asserted.

PAIR-99613-100237 · exclu du score : Pair AMBIGUOUS: E100237 recommended for deletion (counted as FALSE_POSITIVE).

PAIR-100221-100223 · exclu du score : Pair AMBIGUOUS: human check, no score loss asserted.

HELD-130249-LITVM-MAINNET-Q1-2027 · exclu du score : Held proposal is correct (official source: date move or postponement); accept recommended; the guard held it for review, no score loss.

HELD-129900-SKY-BURN-DATE · exclu du score : Held proposal is correct (official source: date move or postponement); accept recommended; the guard held it for review, no score loss.

HELD-129772-NILLION-BRIDGE-REMINDER · exclu du score : Held proposal correctly withheld by the guard (no mutation); reject recommended; outcome counted as FP-129772-0-UPDATE.

HELD-130194-HOODI-GLAMSTERDAM-POSTPONED · exclu du score : Held proposal is correct (official source: date move or postponement); accept recommended; the guard held it for review, no score loss.

HELD-130221-ZKSYNC-MONEY2020-PHOTO · exclu du score : Held proposal correctly withheld by the guard (no mutation); reject recommended; outcome counted as FP-130221-0-UPDATE.

HELD-130565-PENDLELOOP-REDATE · exclu du score : Held proposal correctly withheld by the guard (no mutation); reject recommended; outcome counted as FP-130565-0-UPDATE.

RETRY-127644-SKIPPED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-127790-SKIPPED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-127837-SKIPPED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-128948-SKIPPED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-129320-SKIPPED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-129471-SKIPPED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-129622-SKIPPED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-129760-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-130030-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-130047-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-130064-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-130211-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-130987-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-131291-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-131474-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-131478-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-131484-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

RETRY-131492-BLOCKED · exclu du score : Retry budget bounded and alerted; a still-blocked source is counted by the scorer as a terminal failure; exact skip recommended or applied.

ROOT-IDENTITY-CLOSED-SET · exclu du score : Identity selected an ID outside the allowed set and blocked 4 sources at first occurrence (none carried a calendar claim); counted by the scorer as terminal failures, no double counting.

ROOT-MEDIA-DOWNLOAD-BURST · exclu du score : Four sources blocked by image download failures in one 15-minute burst on 26/10 (09:52-10:08 UTC); none carried a calendar claim; counted as terminal failures, no double counting.

ROOT-THIRD-PARTY-HOST-CHAIN · exclu du score : Third-party product/transaction on a host chain or provider still published (Stellar repo, Arcium game, Walrus storage); outcomes counted as FALSE_POSITIVE units; no double counting.

ROOT-TRACKING-FLAG-DRIFT · exclu du score : Not scored: BMT and ABT were tracked at decision time and untracked afterwards (x_event_monitoring dynamic).