Recurring Event Rule Explainer

How Recurring Event Rule Explainer works

Press Load model once: your browser downloads Gemma 4 E2B instruction-tuned (web build) (2.0 GB) from this site and keeps it in its cache. Then add your text and press Analyze locally. The model runs on this device using your graphics card, so nothing you enter is sent to a server. Until the model is loaded, or if your device cannot run it, the tool falls back to a simple keyword check and labels the result as the fallback.

Gemma 4 E2B instruction-tuned (web build) is a small open language model from Google. The tool sends it the instruction below plus your text, asks for a JSON answer with fixed fields, and shows each field as a card. It runs at temperature 0, so the same input gives the same answer on the same device, though different graphics cards can word it slightly differently.

Inputs longer than 6,000 characters are cut to that length before they reach the model, and the result says so. The model only sees what you paste: it does not look anything up.

The instruction the model gets

You explain a recurring calendar rule in plain English. The rule may be written in words or as an iCalendar RRULE (FREQ, INTERVAL, BYDAY, COUNT, UNTIL). Describe the pattern, when it ends and its exceptions. Do not list or compute specific future dates and do not convert time zones; copy times and zones as written.

What it returns

• Repeats: The repeat pattern in one plain sentence, e.g. 'Every other Tuesday at 10am Pacific'.
• Ends: When the series stops (a date, a count, an event, or 'no end date'), as written.
• Exceptions: Skipped dates, holidays or other exclusions mentioned.
• Ambiguities: Parts that calendar apps may read differently, such as 'every second Tuesday' (every other week, or the 2nd Tuesday of the month?).

Worked example

The model's output for the built-in sample, recorded on a desktop browser. Your run may word things slightly differently.

Recurrence note: Schedule every second Tuesday at 10am Pacific, skip company holidays, end after the December planning meeting.

Repeats

Every second Tuesday at 10am Pacific.

Ends

after the December planning meeting.

Exceptions

company holidays

Ambiguities

every second Tuesday

The model

The files are served from this site, versioned so a cached copy is never stale. Nothing is fetched from a third party while you use the tool.

Limitations

• Small language models make mistakes: they can miss an item, merge two, or state something more confidently than the text supports. Check the result against your input before you rely on it.
• It needs WebGPU and about 8 GB of memory, so it is offered on desktops and laptops, not on phones and tablets. Devices that cannot run it get the keyword fallback, clearly labelled.
• Results describe the input you gave, not the real-world situation behind it. Review them yourself before acting.

Good uses

• Triage calendar and scheduling notes before deeper review
• Prepare consistent labels for repeat workflows
• Reduce manual sorting on small batches
• Keep sensitive drafts in the browser preview