Most digital clocks reset, soft-delete, or vanish when a product dies. Centiglass treats duration as infrastructure: a public instrument whose meaning is the unbroken chain from start_at to end_at, not a marketing countdown.
The visual glass is theater for a sober claim — that absolute timestamps, health logs, and human succession can keep a single experiment alive longer than any one app stack.
Progress is recomputed from stored ISO-8601 anchors every time the page is visible:
last_health and steward status current; sand still advances from the local clock aligned to those anchors.AI is the day-to-day steward of Centiglass: it helps build the glass engine, ship redesigns, write health digests, and brief whoever inherits the experiment. SQL timestamps remain the sole source of time. The steward does not invent, smooth, or override them.
start_at / end_at.Production truth is the health log: drift, skew, ok flags, and checked_at. If the steward heartbeat ages past policy windows, the console shows degraded state in plain language.
Switch the stage to 1 Minute, 1 Hour, or Custom for dense local sand timers — start, pause, reset. Custom accepts presets (30s → 4h) or any duration from 30 seconds to 24 hours. These demos run entirely in your browser; they do not write to Neon.
Use them as focus glasses, meeting markers, or a quick check that the particle engine still feels honest at human scale. Century mode remains the public instrument synced to the API.
Centiglass is not a promise that this exact stack will run until 2126. Continuity depends on domain renewals, Cloudflare/Neon (or successors), paid plans, and people willing to hand the keys forward.
The honest posture: keep anchors immutable, keep health auditable, document succession, and treat every redesign as stewardship — not a soft reset of the century.
Yes in the sense that chamber fill is derived from absolute timestamps. Particle drip is illustrative densification — at century scale a literal grain-per-second stream would be invisible, so the engine shows a sparse continuous flow while height tracks true progress.
The console enters degraded mode and continues from last-known or baked-in fallback anchors (2026-09-21 → 2126-09-21 UTC). Heartbeat fields mark the failure clearly.
It is derived from last_health age and ok flag — a human-readable gloss over SQL, not a separate oracle. AI does not invent time.
No storefront yet. Soft support: keep the idea circulating, or reach the operator when contact is published. Payment links stay offline on purpose.