wiki-comparison-page-routing

name: wiki-comparison-page-routing description: >- When creating or ingesting wiki pages that compare 3+ items (tools, models, frameworks, platforms, etc.), route them to wiki/comparisons/ — NOT wiki/concepts/. This prevents multi-item comparison pages from accumulating in the concepts/ directory where they're hard to find and require cleanup. trigger: >- When creating ANY new wiki page, or when ingesting articles/newsletters/X posts/blog content that compare 3+ items (not just "A vs B").

Wiki Comparison Page Routing

Purpose

Multi-item comparison pages (3+ items) MUST be placed in wiki/comparisons/, never in wiki/concepts/. This skill defines the routing rule and provides a decision tree for all wiki page creation workflows.

Core Rule

Why the distinction matters

Multi-item comparison pages have a fundamentally different structure from concept pages:

• Comparison pages: tables, matrices, axes, scoring rubrics, decision frameworks
• Concept pages: explanatory prose, architecture diagrams, deep dives, intellectual genealogy

Putting comparison pages in concepts/ creates:

1. Discovery failure — users browsing concepts/ don't expect comparison tables
2. Hybrid structure confusion — concepts trying to be comparisons end up shallow on both
3. Cleanup debt — every comparison-in-concepts is a future moved_from entry (we've accumulated 6+ already)

Decision Tree

When creating/ingesting a new wiki page, ask:

Is the page about a single concept/technique/architecture?
  YES → wiki/concepts/ ✓
  NO  → Does it compare 2 items?
           YES → wiki/comparisons/ ✓
           NO  → Does it compare 3+ items?
                    YES → wiki/comparisons/ ✓
                    NO  → Is it about a person/org/tool?
                             YES → wiki/entities/ ✓
                             NO  → Reconsider: should this page exist?

When This Skill Should Fire

Load this skill in any workflow that creates wiki pages:

1. wiki-concept-from-research — before Step 4 (writing phase), check: "Is this comparing 3+ items?"
2. wiki-ingestion-pipelines — all ingestion sections (newsletter, blog, X bookmarks, X accounts scan, active crawl, dreaming)
3. documentation-page-ingestion — when ingesting comparison-style docs
4. wiki-entity-enrichment-from-article — when the article is a survey/comparison roundup

Concrete Examples

✅ Correct routing

❌ Wrong routing (historically corrected)

Frontmatter Convention

Comparison pages use type: comparison and may include moved_from: if consolidated from concepts/:

type: comparison
tags: [comparison, {topic-domain}, ...]
moved_from:
  - concepts/old-page-name.md

Edge Cases

2-items that grow

A head-to-head comparison ("A vs B") may later expand to include C, D, E. That's fine — it stays in comparisons/. The rule is about the page's nature (comparative), not a fixed item count.

Comparison as a section within a concept page

A concept page MAY contain a comparison TABLE as a subsection (e.g., concepts/agent-sandboxing.md has an "Isolation Technology Spectrum" table). This is acceptable because the page's primary purpose is to explain a concept, not to be a comparison portal. The table supports the explanation.

Litmus test: If you removed all comparison tables from the page, would it still be a coherent concept page? YES → concepts/ is fine. NO (the page IS the comparison) → must go to comparisons/.

Newsletter/blog articles that ARE comparisons

When ingesting a survey/comparison article (e.g., "9 AI Agent Harnesses Compared"), create the page in comparisons/ even if the source is a typical concept-creation pipeline. The page type follows the CONTENT, not the pipeline origin.

Integration with Existing Skills

wiki-concept-from-research

After Step 3 (differentiation check), add a routing check before Step 4:

Comparison check: Is this page comparing 3+ items (tools, models, frameworks)?

• YES → Create at wiki/comparisons/<name>.md with type: comparison
• NO → Continue to Step 4, create at wiki/concepts/<name>.md

wiki-ingestion-pipelines

In every ingestion section (newsletter, blog, X bookmarks, X accounts scan, active crawl, dreaming), add:

Before creating a concept page: Check if the article is a comparison/survey of 3+ items. If yes → route to wiki/comparisons/, not wiki/concepts/.

wiki-entity-enrichment-from-article

After Step 0 (Page Placement Decision), and before creating any concept page, add a routing check:

Comparison routing check: Is the article comparing 3+ items or is the user explicitly asking for a comparison across multiple tools/harnesses/systems?

• YES → Create at wiki/comparisons/<name>.md with type: comparison
• NO → Create at wiki/concepts/<name>.md

Litmus test: If all comparison tables were removed, would the page still be a coherent concept page? If NO → comparisons/.

Pitfalls

• Don't move single-concept pages to comparisons/ — pages like agent-sandboxing.md (technology spectrum analysis) are concepts, not comparisons
• Don't create comparison stubs in concepts/ "for later" — they accumulate and require cleanup. Create in comparisons/ from the start
• Head-to-heads ARE comparisons — "A vs B" belongs in comparisons/, not entities/ or concepts/
• Comparison portals ≠ entity pages — individual tool pages go to entities/; the comparison of all tools goes to comparisons/
• Entity enrichment sessions often spawn comparison pages — When enriching an entity page (e.g., OpenClaw) and the user simultaneously asks for a comparison (e.g., "compare memory systems with Claude Code and Codex"), the comparison page must go to comparisons/, even though the primary task was entity enrichment. The entity page gets updated sections; the comparison is a separate page in comparisons/.
• Memory/harness-system comparisons specifically — comparisons of agent memory architectures, context management approaches, or harness features across 3+ harnesses are comparison pages, not concept pages. Validated 2026-05-17: agent-memory-systems-comparison (OpenClaw/Claude Code/Codex/Hermes) was initially created in concepts/, user corrected, moved to comparisons/ in same session. The pattern: entity enrichment + comparison → entity page updated, comparison page in comparisons/.