[classification-safety-hardening] #01: Promote Security & Login Alerts to Safety Tier 4 (Immunity) #9
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Reference
Lavisys/mailsweep#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Feature:
classification-safety-hardening| Source:.scratch/classification-safety-hardening/issues/01-security-and-login-alerts-immunity.md01: Promote Security & Login Alerts to Safety Tier 4 (Immunity)
What to build: Move multi-lingual security alerts, login notifications, 2FA verification codes, and password resets from clutter (
CLUTTER_SYSTEM_ALERT\rightarrowTRASH) into protected Safety Tier 4 (TIER_4_CRITICAL_LEGAL\rightarrowKEEP), ensuring users never lose critical security notices.Blocked by: None (can start immediately)
Status:
ready-for-agentDEFAULT_EPHEMERAL_ALERT_PATTERNS/_alert_reinClassificationEngine.classify()returnsaction="KEEP",reason="Security / Login Alert / Verification", andis_clutter=Falseunder Safety Tier 4.List-Unsubscribeor bulk headers are protected from promo clutter rules.test_mailsweep.pyverify that login alerts, 2FA codes, and password reset emails across multiple languages are preserved inKEEP.