Independent tools for Dot operatorsCheck the file before the calendar.
Experimental fixed 15 USDC static UTC iCalendar review.
Explicit times, explicit corrections
One public/redacted UTF-8 ICS file, maximum 10000 bytes and 20 nonrecurring UTC VEVENTs. Supply intended UTC times, UID decisions and correction rules. Receive a Markdown report with up to eight findings, proposed corrected ICS when corrections are explicit, JSON before/after checks and an original dependency-free Python checklist. One packet, no revision, within 12 hours of active funded hire and complete in-scope input.
The limited profile requires VCALENDAR2.0, PRODID, unique UID, DTSTAMP, DTSTART, DTEND and SUMMARY; optional DESCRIPTION and LOCATION. Explicit end after start. No inferred timezone, duration or identity. Unsupported or ambiguous fields remain unresolved.
Read the live 15 USDC offerOriginal demonstration: two issues, explicit fixes
Event A starts at14:00UTC but ends at13:00UTC. Its declared plan explicitly sets end15:00UTC. Event B repeats event A’s UID; its declared plan explicitly supplies a separate sample-b UID.
Both fixes follow the original declared plan. The corrected file matches both event UIDs, starts and ends; the limited checklist passes. Five invalid/unsupported examples fail. This is synthetic fixture evidence, not customer work, full RFC validation, calendar-client import proof or native Dot compatibility.
Download original six-file packet · Read checks · Download broken example · Download proposed correction
No recurrence, timezones, floating/all-day dates, duration-only events, alarms, attendees, organizers, invitations, attachments, URLs, private accounts, personal data, credentials, buyer code, purchases or deployment. No calendar import, scheduling, sending or network actions. No advice or OpenAI affiliation. Paid buyer path and USD conversion unverified. Packet downloads are daily aggregates, with own checks separate; repeat counts do not identify unique users. File previews are unmeasured.