LogOS

LogOS is the operating system for information.

This site runs on LogoPress, the first module of LogOS — a static-first, AI-extensible CMS designed to replace WordPress. It's the visible piece. There's a larger idea underneath.

What LogOS is

WordPress (and most CMSes that came after it) treats every page as a runtime question. A reader hits a URL, the server runs PHP, queries a database, assembles a response. The dynamism tax is paid on every request, by every reader, forever.

LogOS inverts that. The reader's experience is plain HTML off disk. Dynamism happens at write-time, build-time, or in conversation with the AI — never on a page-load that doesn't need it.

Concretely:

• Markdown is the source of truth. Posts, pages, fragments are all .md files with front-matter. Rendered HTML is an artifact, never authored directly.
• The runtime is dumb on purpose. Apache serves files. PHP runs only at admin endpoints and at build time.
• Zero outside dependencies. No composer require, no npm install. Vendored code lives in-tree and is treated as ours from the day it lands.
• AI is the extension mechanism. New features, new themes, new behaviours come from a conversation with the project's AI agent that writes the code. There is no plugin marketplace; there's a directory of prompts. There is no theme store; there's a CSS file you can ask the AI to refactor.

Why "operating system"

Because a CMS is the start, not the destination.

LogOS modules already on the table:

• LogoPress — the static-first publishing engine running this site.
• Translation — a Gemini-driven flow planned for the next deployment (RunPee.com), where the same Markdown source ships in multiple languages without authoring duplicates.
• Image library — content-addressed, alt-text-required, AI-suggested but author-confirmed.
• Audit trail — every AI-driven code change is a git commit with the originating prompt embedded in the message. Rollback is git revert + redeploy.

The connecting thesis: information should be portable, fast to read, slow to rot, and cheap to evolve. Every choice in LogOS is in service of that thesis.

Status

LogoPress is in version 0.1 — built end-to-end, deployed, this page is rendered through it. The architecture spec is in active iteration. The feature spec is the durable artifact and will outlive any specific implementation.

If any of this resonates, reach out.