Centennial Note: A 100-Year Personal Knowledge System

Centennial Note is not another note-taking app. It is a personal knowledge ecosystem engineered for longevity—100 years of usability, no matter how technology changes. The system combines a lightweight digital core (plain-text Markdown files with a strict schema, stored in a version-controlled repository) with a physical analog backup (archival-quality index cards stored in a fireproof safe, updated quarterly). The digital side is designed to be readable by any text editor now and in the future, while the analog side ensures survival even if the grid fails. The system uses a modified Zettelkasten method with atomic notes, universal timestamps, and a cross-reference map that is regenerated algorithmically. The user maintains a single master index (digital) and a paper-based cross-media concordance. A companion app (optional) provides search and graph visualization, but the core data is independent. Centennial Note comes with a 50-page manual titled 'The Long Now of Knowledge' that includes instructions for future generations on how to reconstruct the system from scratch using only basic tools.

Most productivity systems are ephemeral. Apps shut down, file formats become obsolete, servers go dark. A lifetime of notes can vanish or become unreadable within a decade. Even if data survives, the structure and linking often rely on proprietary logic that future software won't replicate. There is no personal knowledge system designed with a century-long horizon in mind—one that treats information as a legacy, not a fleeting utility.

• Create a note format that is human-readable and machine-parsable, using only plain text with a strict YAML front matter and CommonMark Markdown body.
• Develop a cross-referencing scheme that works both digitally and on paper, using alphanumeric IDs and a separate index file/hard-copy concordance.
• Build a lightweight, open-source desktop app (Electron-free, maybe Tauri) that provides search, graph views, and quarterly export to analog format.
• Design a physical analog sync ritual: every three months, print out changed notes on acid-free paper and store in a partitioned archive box.
• Ensure all digital components can be regenerated from the analog backup if digital is lost (manual transcription guides).
• Write a comprehensive manual and release it under a Creative Commons license.

• Not a collaborative platform – single-user first.
• Not a database with complex queries – only flat files and a search index built on ripgrep or SQLite FTS.
• Not a polished commercial product – the app will be functional but minimal.
• Not a cloud service – everything runs locally; sync can be done via git or rsync, but no central server.
• Not a replacement for task management – it's for knowledge, not to-dos (though tasks can be notes).

Plain text (Markdown with YAML front matter), Git (for version control and optional remote sync), VS Code (as primary editor), Tauri or Rust + WebView for the companion app, SQLite for full-text search index, Pandoc for export, archival paper (acid-free, 20lb+, lignin-free), pH-neutral pens and ink, fireproof and waterproof storage boxes, scanners for digitization (if needed), Zettlr or Obsidian as alternative editors (but not required).

The system has three layers: (1) Digital Core: a folder structure with subdirectories by year, then by month. Each note is a .md file with a timestamp-based filename (e.g., 2025-03-15-001.md) and a YAML header containing ID, title, tags, and outgoing links. (2) Analog Archive: a set of pre-printed index cards (4x6) with a unique barcode sticker for each note, stored in chronological order within a partitioned archival box. A separate 'Concordance' card file maps IDs to titles and physical locations. (3) Sync and Access Tool: a CLI script that generates the analog index from the digital folder, prints scheduled cards, and validates cross-references. The companion app provides a graph viewer and full-text search over the SQLite index. The architecture is designed so that if the digital layer disappears, the analog layer is sufficient to manually reconstruct all notes; if both exist, the digital provides speed and linking.

• User inertia: the quarterly analog sync ritual may feel tedious and be abandoned.
• Future material degradation: even with archival materials, analog notes may fade over a century; scanning and digital redundancy mitigate this.
• Digital format shift: Markdown is very stable, but if it becomes truly obsolete, the analog backup provides a fallback; the manual includes instructions to transcode.
• Low adoption: the system demands discipline and long-term thinking; may only appeal to a niche.
• Technological discontinuity: the app relies on current OS and hardware; a truly long-term solution must be maintainable by future users with unknown tech. The manual addresses this by teaching how to rebuild from scratch.

• How many levels of hierarchy are optimal for both digital and analog without becoming unwieldy? (Currently: year > month > note, but a flat structure might be simpler for analog indexing.)
• Should the concordance be printed on paper or stored as a separate digital file that is re-printed quarterly? (Paper is more robust but harder to update.)
• What barcode symbology to use for analog notes? Code 128 or QR? QR carries more data but may degrade faster.
• Is a physical safe deposit box for the analog backup overkill, or should it be distributed across multiple locations?

The project required a level of personal commitment and foresight that I couldn't sustain at the time. I had started the manual and built a prototype digital folder structure, but the analog ritual design and the app development stalled when my day job consumed all my energy. The idea remains a beautiful what-if, and I still think about it whenever I lose notes from a dead app.

Inspired by the Long Now Foundation and the idea of 'slow data'. The analog cards are meant to be stored in a custom wooden box with a family heirloom feel. The manual should include instructions for creating new notes using only a typewriter or even handwriting, with clear rules for cross-referencing. The whole system should be generational: a parent could pass it to a child as a living record of their thinking.