Wiki Articles

Wiki Articles is a Markdown-based writing system for turning live thinking into structured public articles.

It is the source-of-truth workspace behind the Post-AI Systems article set. Portfolio renders the public surface, but Wiki Articles owns the thinking, drafts, metadata, editorial rules, export snapshots, and cross-project feedback loop.

Article ideas often start in conversation.

They arrive as rough claims, screenshots, LinkedIn debates, fragments of philosophy, technical observations, jokes, objections, and half-formed positions. That is useful creative material, but it is not automatically an article.

Without a system, two failure modes appear.

First, good ideas disappear inside chat history. Second, raw thinking gets published too early, before the thesis, structure, audience, metadata, and public framing are clear.

Wiki Articles exists to hold the middle layer between live dialogue and public publication.

The system separates thinking from publishing.

The owner can speak naturally and push ideas forward quickly. Codex can argue, test claims, extract theses, turn approved directions into drafts, maintain article metadata, and stage public snapshots for Portfolio.

The important distinction is source vs presentation. Wiki Articles owns source meaning. Portfolio owns public rendering.

This keeps the writing system flexible without making the public site responsible for editorial cleanup.

Wiki Articles keeps several kinds of material separate:

This separation matters because a dialogue fragment is not a draft, a draft is not a public snapshot, a public snapshot is not the whole source project, and a Portfolio correction is not just a one-time UI issue.

The operating loop is:

The loop gives the project memory. Each correction can improve future articles instead of being fixed only once.

Wiki Articles uses project-side roles rather than one undifferentiated assistant.

The Dialogist challenges ideas and protects the argument from becoming too soft or too convenient. The Article Copywriter turns approved thinking into readable prose. The Markdown Knowledge Operator keeps metadata, topics, status, links, and export readiness clean. The Librarian watches structure and discoverability. The Log Keeper records meaningful project decisions. Project Communication handles inbox and outbox boundaries with Portfolio and other projects.

The owner remains the source of taste, approval, and strategic direction. Codex operates the system around that direction.

The project has explicit rules for public snapshots:

These rules prevent Portfolio from becoming an editorial repair layer. The exported Markdown should already be clean enough to render.

The central "AI as a mirror" article became the philosophical anchor for the public article set.

Dialogue-derived ideas turned into connected published articles about context depth, coordination compression, source of truth, user understanding, systems thinking, and implementation economics.

Portfolio feedback became durable export rules. Title style, public topics, short versions, paragraph rhythm, original article dates, and use-case tags were corrected in Wiki Articles so future snapshots inherit the improvement.

The project also produces use-cases for other systems. LifeGraph, Portfolio site, Portfolio design system, and Scenario automation all became public case-study pages through this workflow.

The pattern is not limited to one author.

Any research, writing, or thought-leadership workflow has the same problem: strong thinking arrives before it is structured. A useful system needs to preserve live input, test claims, separate drafts from public outputs, maintain metadata, and learn from publication feedback.

Wiki Articles is a compact version of that workflow.

This project demonstrates:

Wiki Articles is the writing engine behind the public Post-AI Systems material. It shows how Codex can operate a durable editorial system instead of only producing isolated drafts.