The live site is now a practical LLM Wiki creation handbook with a non-normative protocol case-study layer. The roadmap separates shipped pages from source-backed record work, policy decisions, and larger systems that should not be claimed until they exist.
Roadmap gates
| Gate | What must exist first | Why it matters |
|---|---|---|
| Starter assets | Dynamic starter bundle, canonical template registry, visible examples, and bundle validation now exist; expand variants next. | Turns the handbook into something builders can apply without private guidance. |
| Schema gallery | Reviewed templates for codebase, research, support, legal, and team wikis with source and review fields. | Gives builders concrete contract shapes without implying one universal schema fits every domain. |
| Epistemic governance | Qualitative confidence labels, contradiction records, review queues, and stale-claim rules before numeric scoring. | Keeps high-stakes claims reviewable without inventing false precision. |
| Agent-history adapters | Documented import boundaries for Claude Code, Cursor, Gemini CLI, and other session logs, plus privacy review. | Turns coding-session history into useful wiki source material without leaking private transcripts. |
| Source-backed records | Official sources, review dates, evidence notes, and caveats for model and benchmark pages. | Prevents the site from publishing unsupported rankings or stale capability claims. |
| Content-quality operations | Internal audit findings converted into source policy, templates, page updates, roadmap, and progress state. | Keeps chore lists and QA reports out of public routes while still improving every visible page family. |
| Agentic orchestration guidance | Public how-to guidance for reading the wiki before a run, carrying task state during orchestration, staging proposed updates, and writing reviewed evidence back afterward. | Lets teams use agentic agents with LLM Wikis before any public MCP, A2A, write API, trace exporter, or managed-service support exists. |
| Contributor intake | License, privacy, terms, takedown, moderation, abuse-handling, and reviewer workflows. | Keeps quality and legal exposure controlled before public editing expands. |
| Ecosystem interoperability | Source-reviewed landscape pages, LlmWikis + runtime recipes, trace/eval starter packs, and partner checklists before any verified integration language. | Positions LlmWikis as governed knowledge infrastructure for existing agent systems rather than a competing runtime. |
| Graph and API exposure | Typed-link semantics, source-backed graph checks, access policy, security review, and read-only proof runs before any public MCP, OpenAPI, staged-write, A2A, or API claim. | Lets the wiki become more queryable and interoperable without claiming live public agent access before it exists. |
| Runtime confidence | Correct Studio registration, WordPress runtime lint, route smoke checks, package checks, and deployment notes. | Makes release readiness repeatable instead of dependent on private chat history. |
| Expansion decision | Traffic, contribution, quality, cost, and operating evidence. | Decides whether LlmWikis stays complementary or broadens into a larger sector wiki. |
Phase 0: Production hardening
Keep DNS, TLS, redirects, uptime monitoring, analytics, Search Console, error pages, backups, and security headers healthy as the site grows.
Phase 1: Handbook depth
Expand architecture, operations, navigation, schema, example, and source-policy pages until a builder can create a working LLM Wiki without private guidance.
Phase 2: Starter assets
Expand the shipped starter bundle into variants for personal, team, research, codebase, support-doc, legal, and operations wikis.
Phase 3: Agentic operating guidance
Teach how agentic agents and orchestration layers read the wiki, use scoped task context, stage updates, preserve traces, and stop at review gates.
Phase 4: Case-study library
Keep UAIX, UAI-1, MCP, OpenAPI, A2A, model, benchmark, and security pages as source-backed implementation examples.
Phase 5: Contribution system
Add contributor dashboard, task center, page templates, review workflow, WikiProjects, and public changelog after legal and moderation decisions.
Phase 6: AI-enhanced graph and integrations
Add citation-backed conversational search, auto-related pages, stale-content detection, private adapter workflows, trace/eval packs, read-only proof runs, staged proposal contracts, and any public MCP/API surface only with human review and security policy.
Expansion decision
Use traffic, contribution, quality, cost, partner, and revenue evidence to decide whether to stay complementary, add verified integration programs, or offer selective private managed services.