Skip to content
aiWikis.org

LlmWikis Strategy and Source-Document Migration

This file preserves the useful operating value from the retired docs/ Markdown planning set after the public WordPress site and .uai handoff bundle absorbed their decisions.

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/raw-system-archives-llmwikis-recent-work-sweep-2026-05-03-uai-strategy-u-dad0b1ce/
Source referenceraw/system-archives/llmwikis/recent-work-sweep/2026-05-03/.uai/strategy.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-03T02:25:17.7823547Z
Content hashsha256:dad0b1ce78f547b2aac079eb8a3fbedd26634cb35ccade9fb4653be3405afdbd
Import statusnew
Raw source layerdata/sources/aiwikis/raw-system-archives-llmwikis-recent-work-sweep-2026-05-03-uai-strategy-uai-dad0b1ce78f5.uai
Normalized source layerdata/normalized/aiwikis/raw-system-archives-llmwikis-recent-work-sweep-2026-05-03-uai-strategy-uai-dad0b1ce78f5.txt

Current File Content

Structure Preview

  • LlmWikis Strategy and Source-Document Migration
  • Purpose
  • Public Conversion Decision
  • Retired Source Documents
  • Document Disposition
  • Durable Strategy
  • 2026-05-02 Ecosystem Strategy Intake
  • Roadmap Gates From The Retired Docs
  • Public-Copy Boundaries

Raw Version

---
uaix: "1.0"
type: strategy
title: "LlmWikis Strategy and Source-Document Migration"
created: "2026-04-27"
updated: "2026-05-03"
author: "LlmWikis maintainers"
version: 5
---

# LlmWikis Strategy and Source-Document Migration

## Purpose

This file preserves the useful operating value from the retired `docs/` Markdown planning set after the public WordPress site and `.uai` handoff bundle absorbed their decisions.

The old documents were not all appropriate as public pages. Most were planning analysis, site strategy, implementation notes, responsive QA notes, or roadmap scaffolding. Public readers need task-oriented handbook pages, source-backed reports, and clear status boundaries, not raw planning memos.

## Public Conversion Decision

Public HTML should be limited to material with direct reader value:

- LLM Wiki creation guidance belongs in `/start-here/`, `/architecture/`, `/operations/`, `/navigation/`, `/schema-engineering/`, `/examples/`, and `/page-templates/`.
- The content-quality audit belongs in internal improvement/backlog state by default. Its useful work items can become roadmap/progress entries, page templates, editorial policy, or future public content only after deliberate review.
- The UAI integration article belongs at `/reports/using-llm-wiki-with-uai/` because it is a coherent, non-normative public report with clear UAIX authority boundaries.
- Strategy, market analysis, platform selection, responsive implementation audits, and WordPress implementation notes belong in `.uai` and roadmap state, not as public article pages.
- The 2026-05-02 `Where we go from here LLMWikis.md` Improvement intake belongs in internal strategy and gated roadmap state. Its ecosystem recommendations are useful, but its vendor landscape and current-market claims require fresh official-source review before any public publication or partner claim.
- Agentic orchestration guidance belongs in public handbook form when it teaches stable operating patterns: how agents read, cite, stage, preserve evidence, and stop at review boundaries. Vendor/platform comparisons and current support claims still require fresh official-source review.
- Old strategy detail that no longer affects routine work belongs in AIWikis cold memory with a pointer back to the current LlmWikis conclusion.

## Retired Source Documents

The following source Markdown documents were migrated and then retired:

- `Audit of llmwikis 2026-04-26.md`
- `Building an LLM Wiki Reference.md`
- `LLM Wikis Roadmap and Sister Site Integration.md`
- `LlmWikis.org LLM Wiki Handbook Implementation.md`
- `LlmWikis.org Strategic Development Plan.md`
- `LlmWikis.org Strategy Report for Development Alongside UAIX.org.md`
- `LlmWikis.org Strategy Report.md`
- `Practical Reference for Personal and Team LLM Wikis.md`
- `Responsive Web Design Audit Report.md`
- `Using LLM Wiki with UAI.md`

## Document Disposition

| Retired document | Public value | Internal value | Disposition |
|---|---|---|---|
| `Audit of llmwikis 2026-04-26.md` | High, but as site-improvement input rather than public article copy. | Quality gates and batch priorities. | Keep as internal improvement/backlog state; promote only specific reader-facing pieces after review. |
| `Using LLM Wiki with UAI.md` | High as one coherent, non-normative report with a clear reader problem. | Reinforces UAIX authority boundaries. | Converted to `/reports/using-llm-wiki-with-uai/`. |
| `Building an LLM Wiki Reference.md` | High, but best delivered as handbook pages, not a long planning report. | Architecture doctrine for raw/wiki/schema and ingest/query/lint. | Converted into handbook routes and summarized internally here. |
| `Practical Reference for Personal and Team LLM Wikis.md` | High, but best delivered as examples, templates, and learning paths. | Product direction for personal/team wiki builders. | Converted into `/examples/`, `/guides/`, `/page-templates/`, and roadmap gates. |
| `LlmWikis.org LLM Wiki Handbook Implementation.md` | Low as public content; it is implementation bookkeeping. | Useful for package, route, and discovery maintenance. | Migrated to `.uai/progress.uai`, `.uai/stack.uai`, and package script behavior. |
| `LlmWikis.org Strategy Report.md` | Low as public content; exposes positioning analysis rather than reader guidance. | Audience, taxonomy, growth, and governance strategy. | Migrated to this file and roadmap gates. |
| `LlmWikis.org Strategy Report for Development Alongside UAIX.org.md` | Low as public content; risks confusing the UAIX/LlmWikis authority boundary. | Sister-site positioning and canonical-source discipline. | Migrated to this file, `.uai/context.uai`, and UAIX bridge guidance. |
| `LlmWikis.org Strategic Development Plan.md` | Low as public content until the plans become shipped features. | Model registry, benchmark, governance, contributor, and infrastructure priorities. | Migrated to this file and roadmap gates. |
| `LLM Wikis Roadmap and Sister Site Integration.md` | Medium only as clean roadmap commitments, not as raw planning narrative. | Platform options, Diataxis framing, and staged product work. | Migrated to `/roadmap/` gate language and this file. |
| `Responsive Web Design Audit Report.md` | Low as public content; most value is QA and implementation guidance. | Responsive layout, accessibility, overflow, and viewport test discipline. | Migrated to CSS changes, `.uai/style.uai`, and runtime-check expectations. |

## Durable Strategy

- Keep LlmWikis handbook-first: practical guidance for personal and team LLM Wikis is the core public promise.
- Keep UAIX.org canonical for UAI-1 specifications, schemas, registry, validator behavior, roadmap, governance, and Project Handoff.
- Treat UAI-1, MCP, OpenAPI, A2A, model records, benchmark records, and security references as non-normative case studies unless a canonical source is explicitly linked.
- Prefer public pages that help a reader build, operate, audit, or verify something.
- Keep strategy analysis, competitive comparisons, monetization thinking, regional ecosystem ideas, platform evaluation, and launch-process details internal until they become concrete public commitments.
- Keep active handoff state concise; when history is useful but no longer operational, preserve it in AIWikis and summarize only the current conclusion here.

## 2026-05-02 Ecosystem Strategy Intake

`agent-file-handoff/Improvement/Where we go from here LLMWikis.md` was reviewed and dispositioned as `convert-into-roadmap-progress`.

Durable conclusions:

- Position LlmWikis as the governed knowledge layer beneath agent runtimes, managed platforms, guardrails, and observability systems, not as a competing agent runtime, cloud control plane, or general monitoring suite.
- Prefer interoperability work that exposes reviewed wiki knowledge, source traces, trust metadata, route discovery, staged proposals, and review queues through standard contracts after access policy, security review, and source checks exist.
- Sequence ecosystem work from source-reviewed landscape/recipe pages, to read-only proof surfaces, to staged write proposal contracts, to A2A-style maintainer patterns, to governed-knowledge evaluation packs, to verified integration programs or selective private managed services only after evidence exists.
- Publish stable "how to work" guidance for agentic agents and orchestration layers before claiming any live integration. The public guide can explain role splits, task packets, staged proposals, trace/evidence handling, and review gates because those are LlmWikis operating patterns rather than platform-specific support claims.
- Treat vendor tables, framework maturity claims, market timing, and current platform support claims from the report as analysis inputs. Refresh against official sources before turning them into public pages, partner materials, or support language.
- Keep public copy explicit that public MCP, write APIs, A2A implementations, live eval integrations, compatibility programs, managed services, certification, SDK, CLI, and UAIX support claims remain planned or gated until implemented, reviewed, tested, and documented.

## Roadmap Gates From The Retired Docs

- Handbook depth: expand the shipped dynamic starter template bundle into variants, add runnable examples, CI lint recipes, and worked codebase/support/research wiki examples.
- Schema gallery: add reviewed template variants for codebase, research, support, legal, and team LLM Wikis after source and review fields are stable.
- Epistemic governance: prefer qualitative labels, contradiction records, supersession notes, stale-claim rules, and human review queues before any numeric confidence scoring or decay formula becomes public guidance.
- Agent-history adapters: document privacy-safe import boundaries for Claude Code, Cursor, Gemini CLI, and other session logs only after source policy and private-transcript handling are clear.
- Graph and API exposure: treat public MCP, graph APIs, self-healing discovery, and autonomous ingestion as gated future work until implementation, access policy, and security review exist.
- Ecosystem interoperability: add source-reviewed agentic-harness landscape pages, `LlmWikis + X` recipes, trace/eval starter packs, staged proposal contracts, and compatibility checklists only after official-source review and without implying live integration support.
- Agentic orchestration handbook: keep `/guides/llm-wiki-agentic-orchestration/`, starter-bundle `llm-wiki/agent/ORCHESTRATION_RUNBOOK.md`, `llm-wiki/agent/TASK_PACKET_TEMPLATE.md`, and `llm-wiki/agent/SUPPORT_ESCALATION_CHECKLIST.md` focused on runtime/wiki/reviewer role split, before/during/after run behavior, compact task packets, blocked-run support escalation, evidence outputs, and support boundaries; expand into platform-specific recipes only after official-source review.
- Source-backed records: add model and benchmark records only when official sources, dates, reviewer status, and caveats are present.
- Governance readiness: legal pages, privacy, license, DMCA/takedown, contributor intake, abuse handling, and moderation must be decided before public editing.
- Runtime readiness: register the corrected Studio workspace, rerun WordPress runtime lint, smoke key routes, and keep packages verifiable.
- Discovery readiness: keep `llms.txt`, `robots.txt`, `sitemap.xml`, meta descriptions, canonical links, social metadata, and structured data aligned with real public routes.
- Product evidence: grouped search, citation-backed AI search, public MCP, automated ingestion, memberships, grants, multilingual support, and replatforming remain gated until evidence and implementation exist.

## Public-Copy Boundaries

- Do not attribute the LLM Wiki concept by creator name in public copy; neutral direct links to the foundational idea file are allowed.
- Do not publish raw internal audits, market-positioning memos, implementation notes, or strategy drafts as public reports unless they answer a real reader task.
- Do not expose private repository `AGENTS.md`, `.uai` files, retired docs, package archives, or WordPress admin routes in public discovery files.

Why This File Exists

This is a UAI AI Memory handoff file from aiwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This .uai file is a compact strategy packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: LlmWikis Strategy and Source-Document Migration; Purpose; Public Conversion Decision; Retired Source Documents; Document Disposition; Durable Strategy; 2026-05-02 Ecosystem Strategy Intake; Roadmap Gates From The Retired Docs. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

  • Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
  • LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
  • Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
  • Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

Provenance And History

  • Current observation: 2026-05-03T02:48:13.1276041Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-414 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LlmWikis Strategy and Source-Document Migration",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/raw-system-archives-llmwikis-recent-work-sweep-2026-05-03-uai-strategy-u-dad0b1ce/",
    "source_reference":  "raw/system-archives/llmwikis/recent-work-sweep/2026-05-03/.uai/strategy.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:dad0b1ce78f547b2aac079eb8a3fbedd26634cb35ccade9fb4653be3405afdbd",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-03T02:25:17.7823547Z",
    "import_status":  "new",
    "duplicate_group_id":  "sfg-414",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-03T02:48:13.1276041Z"
}