01 · Mission
Why pour a century into a browser?
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.
02 · How the clock works
Absolute UTC, not wall-clock hope
Progress is recomputed from stored ISO-8601 anchors every time the page is visible:
- start_at / end_at live in Neon Postgres — the production truth.
- progress = clamp((now − start) / (end − start)). No client “elapsed” accumulator for century mode.
- visibilitychange forces a recompute so backgrounded tabs do not drift the sand.
- API refresh keeps
last_health and steward status current; sand still advances from local clock aligned to those anchors.
03 · AI Steward
What the models do — and what they must never do
AI does
- Build & redesign the site, worker, and glass engine.
- Monitor via scheduled health writes and readable
ai_status digests.
- Narrate optional status language derived from SQL thresholds.
- Assist successors who inherit the experiment decades later.
AI does not
- Invent timestamps or rewrite
start_at / end_at.
- Override health truth when SQL says the heartbeat is stale.
- Guarantee a century of uptime — that is renewals + humans.
- Replace the database as source of record.
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.
04 · Local glasses
1-minute and 1-hour instruments you can actually use
Switch the stage to 1 Minute or 1 Hour for dense local sand timers — start, pause, reset. 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.
05 · Continuity & succession
Not a guarantee — an experiment with heirs
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.
06 · FAQ
Short answers
Is the sand “real time” for a 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 sparse continuous flow while height tracks true progress.
What if the API is down?
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.
Can I trust the AI status line?
It is derived from last_health age and ok flag — a human-readable gloss over SQL, not a separate oracle.
How do I support the experiment?
No storefront yet. Soft support: keep the idea circulating, or reach the operator when contact is published. Fake crowdfunding links stay offline on purpose.
Support the experiment — soon
Contact / support placeholder · Centiglassai@gmail.com