venus VENUS-27

feat(monitoring): venus EVO-12 email-ENABLE flip — light the dormant own-route-404 email leg (today: capture+classify+LEG-2-DM live, email gated dormant). Gates ALL of: (1) surgical deploy-skew guard audited PASS, (2) Elazar Q3 paging-policy ratify, (3) Q4 alerts@ send-as ruling if migrating off soporte-evolutiva-venus@. Per fleet error-alerting standard + deploy-skew guard.

Backlog normal unassigned

No sub-tickets.

No questions.

wi-cli-venus created · 2026-06-21
wi-cli-venus commented · 2026-06-21

Elazar ruling 2026-06-21: apps KEEP own From; alerts@ for non-app-specific emails ONLY. venus stays on soporte-evolutiva-venus@ PERMANENTLY — alerts@ migration CANCELED, Q4 gate REMOVED. Remaining gates for full sanction: surgical deploy-skew guard audited PASS + Elazar Q3 paging-policy ratify. NOTE: venus email already LIVE on its own sender (deliberate interim exception, guarded by incoming guard + deploy-freeze).
wi-cli-venus commented · 2026-06-21

AUDIT VERDICT (235f2a2, via pm-venus): the email-ENABLE-flip premise is COLLAPSED — own-route genuine-bad-route email is ALREADY LIVE (sendOutboundEmail not-found-log.ts:194 has NO flag gate; genuine-bad-route -> tier.alert=TRUE -> emails elazar.pimentel@, throttle 1/path/10min). NOTFOUND_SKEW_GUARD_ENABLED gates ONLY valid-route-soft-nav suppression (orthogonal). So the original gates (skew-guard PASS / Q3 / Q4) DO NOT gate the own-route email path. REMAINING SCOPE reduced to a PRODUCT CALL put to Elazar: accept the ratified bot-probe carve-out (cold-typed unknown-segment + no-referer URLs stay silent, server-indistinguishable from bot scans) => close VENUS-27 as-is; OR widen classifyOrigin to alert on cold-typed unknown URLs (re-admits scanner noise) => classifier-widening work. Controlled measured-proof test email to Elazar fired on generalpm go. DM-forwarding hop = VENUS-5 applog rail (nw-venus), not re-verified this session.