ICS IDENTITY EVIDENCE · LOCAL ONLY · NOT A DUPLICATE CLEANER
Inspect ICS event identity
See recurrence masters, detached occurrences and differing revisions separately. Repeated UID alone does not mean an event is safe to delete.
Your file stays in this browser. This tool does not connect to a calendar, select a winning revision, expand recurrence rules, repair or rewrite files. Unsupported or ambiguous evidence stays unresolved.
No file or text processed.
Identity evidence
| Component | Role / grouping | UID | Original instance / current start | Revision evidence | Source SHA-256 / limits |
|---|
What these labels mean
A master identifies the recurrence set. A detached occurrence uses RECURRENCE-ID, the original scheduled time, not its moved DTSTART. Exact repeated bytes and different components for the same instance are separate observations. Neither is a deletion recommendation. Hashes cover captured event bytes only, not authenticity, correctness or import safety.
Limits: 5,000 components, 64 KiB per event, 4 MiB total source bytes, at most 128 components for one identity. Unknown timezone equivalence, unsupported RANGE directives and missing master evidence remain unresolved. This is not a complete RFC validator.