The durable asset is not the website. It is a directory of readable Markdown files with explicit metadata and reviewable Git history.
The useful constraint
Plain Markdown keeps each note accessible to editors, command-line tools, static-site generators, and future systems that do not exist yet. It avoids tying the knowledge itself to a database export or a proprietary editor.
The format is intentionally less expressive than MDX. A normal article does not need executable components, and removing that capability also removes a class of security and maintenance problems.
Git is the change log
Git records when a claim changed, which source was added, and whether a slug remained stable. Small content commits make those changes understandable without requiring a separate CMS audit log.
Publishing is a separate decision
A file existing in the repository does not make it public. Draft, private, and raw-source areas are excluded by design. The public build only admits an article after its status, visibility, indexing rules, schema, and leak checks agree.
Practical result
An AI editor can help organize a note today and be replaced tomorrow. The Markdown files, validation scripts, and Git history remain usable either way.