Digital Legacy & Longevity

Preservation Architecture

Specifications for decadal survival, static HTML exports, and zero vendor lock-in.

Most personal websites die when their creator stops paying for a SaaS subscription, when a database provider updates their billing model, or when a hosting platform shuts down.

This journal is built under a decadal survival covenant. It is engineered to remain legible thirty years from now, regardless of the fate of any individual tool.

The Five Pillars of Survival

1. Plain-Text & Open Database Dual Format

Every entry exists simultaneously in standard PostgreSQL and as standard Markdown/MDX files in Git. If PostgreSQL ever becomes unavailable, the entire site can be compiled directly from the /content folder.

2. Offline Static Archive Exporter

The project includes an automated static archive builder (npm run export:archive) that creates a zero-dependency HTML/CSS folder viewable directly in any web browser without a local server.

3. Permanent, Semantic URLs

All routes follow the permanent convention: /entries/YYYY/MM/DD/slug with permanent aliases and automatic redirects for legacy links.

4. Zero External Runtime Dependencies for Readers

No remote CDN fonts, no third-party JavaScript trackers, and no external comment widgets. Readers download self-contained pages that function indefinitely.

5. RSS Syndicate & Sitemap Permanence

Full-content feeds are syndicated at /rss.xml and /feed.xml so subscribers store copies on their own devices.

Emergency Restoration Protocol

In the event that the primary VPS or domain is disrupted:

Clone the repository from Git backup.
Run node scripts/init-db.js to restore the database container on any fresh host.
Or run node scripts/export-archive.js to generate static HTML for Cloudflare Pages, GitHub Pages, or local offline disks.

Loading Archive

Connecting to sovereign datastore...