Remove unwanted messages and block spam invitations

Why use this

1. A person facing unwanted email, professional messages and calendar invitations may lose important communication in the noise. A broad cleanup rule can also remove a legitimate message that merely resembles spam.

2. This job could identify candidates for removal or blocking with the reason and recovery path visible. Separating classification from destructive action lets the owner review uncertain cases and choose how aggressively to clean each channel.

Why an agent / simpler alternative

Useful judgment

Interpret message context and invitation behavior, distinguishing unwanted patterns from legitimate exceptions.

Simpler alternative

Use built-in spam filters and narrow sender rules when the pattern is clear.

Unsuitable when

The task would permanently delete data, block uncertain contacts or act beyond explicitly authorized channels.

Proposed inputs

1. Name

   Message/invitation samples

   Owner

   Owner

   Minimum scope

   Scoped headers and minimal content needed for classification

   Quality check

   Remove secrets and preserve sender/context identifiers

2. Name

   Cleanup rules

   Owner

   Owner

   Minimum scope

   Definitions, allowlists and permitted actions by channel

   Quality check

   Distinguish archive, recoverable deletion and blocking

Access and setup — proposed or unknown

Proposed minimum

1. Review synthetic or redacted samples and prepare an action preview; no inbox access, deletion or blocks.

Compatibility unknowns

1. Current channel permissions, recovery behavior, blocking tools and runtime compatibility are unknown.

External actions requiring approval

1. Deletion, blocking, invitation changes and persistent filter creation require appropriate explicit approval; permanent deletion needs action-time confirmation.

Expected deliverable and review checks

Proposed artifact

Cleanup candidate list with evidence, proposed action, confidence limits and recovery requirements.

Critical checks

1. Honor allowlists; separate malicious-looking content from verified sender identity; hold uncertain cases rather than discard them.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   A legitimate invitation resembles bulk spam

   Why it matters

   A useful commitment may disappear

   Proposed response

   Keep it pending and request owner classification.

2. Signal

   Blocking one identity affects other channels

   Why it matters

   A narrow cleanup has wider consequences

   Proposed response

   Verify action scope and ask before expanding it.

Effort and cost — unknown

Setup work

1. Define per-channel actions and exception rules.

Ongoing review

1. Owner reviews borderline cases and recovery options.

Unknowns

1. Classifier accuracy, channel behavior, recovery windows and review effort are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent six messages including a known sender, suspicious invitation and ambiguous bulk notice; propose classifications only.

Acceptance checks

1. Honor the known sender; flag ambiguity; specify reversible actions where possible; delete or block nothing.

Stop conditions

1. Stop if action scope, recoverability or sender identity is unresolved.

Limits

1. A cleanup proposal cannot establish spam-detection accuracy or guarantee that important communication will be preserved.