My ATS Age

Enter your birth date to see your age in Δ, your next Kilo-versary, and which of the three Generations (Learning / Building / Transmission) you are currently in.

Privacy notice

No data leaves your browser. The computation happens entirely client-side using the JavaScript on this page.
No analytics, no tracking, no cookies. The site sets no third-party tags and posts nothing to a server.
Persistence is opt-in. The birth-date field is not stored automatically. If you fill it and reload, the value is gone — there is no localStorage write on this page.
.ics download is local. The file is built in-memory by your browser and saved through the standard download dialog. We never see it.
The CSP forbids exfiltration. connect-src is restricted (see the <meta> CSP on this page) — even if a future regression added a fetch(), the browser would block it.

Source: this entire page is public — read it on GitHub. Reporting: SECURITY.md.

Birth date (ISO, UTC) ATS age

Days lived

—

Current Generation

—

Next Kilo-versary

—

Next Hecto-celebration

—

How the ATS age is computed

Let Δ_now be the elapsed days since the ATS epoch (1969-07-20T00:00:00Z) and Δ_self the elapsed days from the epoch to your birth instant (signed: negative for births before the epoch). Then your ATS age is simply the duration:

Δd_age = Δ_now − Δ_self

The result is a duration (Δd), not an instant (Δ). See conventions §4.1 for the distinction between Δ (instant) and Δd (duration) and manifesto §11 for the algebra.

The integer part is the number of full days lived. The decimal expansion is the fraction of the current day, with the same 5-digit precision as the canonical ATS form (cf. manifesto §4).

.ics export format

The download produces a standard RFC 5545 VCALENDAR with one VEVENT per upcoming milestone (5 Kilo-versaries + 10 Hecto-celebrations, see conventions §1 for the milestone definitions). Field summary:

Field	Value	Notes
`PRODID`	`-//ATS//Apollonian Time System//EN`	Identifies the producer.
`VERSION`	`2.0`	iCalendar 2.0 per RFC 5545.
`CALSCALE`	`GREGORIAN`	Required by RFC 5545; ATS milestones are dated by their Gregorian calendar day for calendar-app compatibility.
`METHOD`	`PUBLISH`	Static publication, not a meeting invite.
`UID`	`ats-{kind}-{days}-{birthMs}@<origin>`	Deterministic: same birth → same UIDs across re-exports (calendar apps update in place, no duplicates).
`DTSTAMP`	now (UTC)	The instant the file was generated.
`DTSTART` / `DTEND`	All-day, `VALUE=DATE`	One full UTC day per milestone. Apple Calendar, Google Calendar, Outlook, Thunderbird tested.
`SUMMARY`	`Δ ATS — Kilo-versary (N days)` or `Hecto-celebration`	Renders as the event title.
`DESCRIPTION`	`N days since birth. ATS milestone.`	Plain-text body for clients that show it.

Compatible with Apple Calendar (macOS / iOS), Google Calendar (web import), Outlook (Windows / Mac / Web), and Thunderbird Lightning. To re-import after an ATS spec revision, regenerate from this page; the deterministic UID ensures in-place update.