Mythos

MythOS Content Topology is an architectural framework for organizing knowledge into interconnected memo clusters that are simultaneously optimized for human navigation and AI citation. It is a practical application of the @Recursive Mythic Engine — a system that encodes transformation through structural recursion — applied to the challenge of making what you know findable, quotable, and compounding. The framework operates on a single principle: a network of short, focused, well-linked memos outperforms a collection of long, comprehensive articles — for humans, for search engines, and for AI models. Each memo answers one question completely. The links between memos create a knowledge graph that search engines and AI systems can traverse to understand relationships, assess topical authority, and identify what to cite.

The Five Memo Types

Every memo in a @MythOS content topology serves one of five roles. The type determines its length, link density, and function within the cluster.

Pillar

The hub of a topic cluster. Defines the domain, summarizes its dimensions, and links outward to every memo beneath it. 500-800 words, 15-25 links. A cluster has exactly one pillar. It's the answer to the broadest query in your domain — "What is Reddit marketing?" — and every other memo in the cluster strengthens it.

Concept

A named framework, methodology, or idea that is original and citable. 300-500 words, 5-12 links. Concepts are the intellectual property of the graph — the things AI models quote when someone asks "how does X work?" Named frameworks get cited. Unnamed advice doesn't.

Entity

A node representing a person, company, product, or platform. 150-300 words, 3-9 links. The most common memo type and the most natural to write. Entities form the connective tissue of the graph — every concept needs entities to ground it, every story needs entities to populate it.

Story

A standalone narrative — a case study, incident, or experiment that illustrates a concept. 200-400 words, 3-7 links. Stories are the proof layer. They make abstract frameworks concrete and give AI models the specific, quotable examples that get cited in "what's an example of X?" queries. Tight enough to quote in a podcast.

Reference

A data-rich definition page for a tool, platform feature, or industry term. 200-500 words, 5-15 links. References are the factual backbone — dense with extractable statistics, dates, and specifications. They have the highest citation rate per word because they answer specific questions with specific data.

How the Topology Compounds

The power isn't in any single memo. It's in what happens when 30, 50, or 100 memos link to each other within a topic cluster.

  • Each new memo strengthens every memo it links to. A new story memo about a Reddit crisis response doesn't just add a page — it makes the pillar memo more authoritative, the concept memo more grounded, and the entity memos more connected
  • Every memo is its own entry point. A reader who discovers an entity memo through search can navigate to the concept, then to the pillar, then to related stories. An AI model that crawls the pillar follows links to cluster memos and identifies the entire network as authoritative
  • The graph compounds over time. Unlike a blog where old posts decay, a well-maintained memo topology grows stronger as new memos add links, update data, and create new pathways through the knowledge This is the same architecture that makes @Wikipedia the most-cited domain across every major AI system — with one critical advantage: voice. Wikipedia enforces neutrality. MythOS memos carry practitioner expertise. AI models increasingly cite both, but for different reasons. Wikipedia defines. MythOS advises.

The Recursive Element

The topology is recursive by design, in the tradition of the @Recursive Mythic Engine. Every memo is both a destination and a doorway. Every link is both a reference and an invitation. The reader who enters at any point can traverse the full graph — and each traversal deepens understanding of every node they touch. For the technical basis of why this architecture works for @Search Engine Optimization (SEO) and @Generative Engine Optimization (GEO), see @MythOS as SEO and GEO Infrastructure.

Related

  • @MythOS Content Topology: Implementation Guide — full specification for AI agents and practitioners building their own topology I didn't design this framework. I noticed it. After writing hundreds of memos over several years, the pattern emerged: the short, interconnected ones got read, shared, and cited. The long, comprehensive ones got bookmarked and forgotten. The network did the work that no single page could do alone. The five types formalize what was already happening naturally in my library. Pillar memos emerged because some topics needed a hub. Concept memos emerged because named frameworks got cited more than unnamed advice. Entity memos emerged because they're how I naturally think — short nodes with links. Story memos emerged because people retell stories, not frameworks. Reference memos emerged because data ages and needs its own container. The topology is how I think, encoded as architecture. That it also happens to be what search engines and AI models reward most aggressively is a happy accident — or proof that the systems indexing the internet are learning to read the way humans navigate.

Contexts

Created with 💜 by One Inc | Copyright 2026