LLMWikis Decisions Log

LLMWikis Decisions Log is a uai-system source file exposed by AIWikis.org with provenance, current content, and generated explanation.

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-decisi-ea3341dc/
Source reference	raw/system-archives/llmwikis/internal-memory-reorg/2026-05-01/.uai/decisions.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-04-28T22:09:16.0489169Z
Content hash	sha256:ea3341dcd814df356117175d75884ef779814c09fd5667a52d189b3a03004239
Import status	unchanged
Raw source layer	data/sources/llmwikis/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-decisions-uai-ea3341dcd814.uai
Normalized source layer	data/normalized/llmwikis/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-decisions-uai-ea3341dcd814.txt

Current File Content

Structure Preview

• LlmWikis Decisions Log
• [2026-04-28] Preserve LlmWikis starter bundle source ownership
• [2026-04-28] Treat AIWikis dogfood as handoff package QA input
• [2026-04-28] Treat LlmWikis as prelaunch until first production release
• [2026-04-28] Permanently retire public content-quality audit routes
• [2026-04-27] Archive already-dispositioned intake files
• [2026-04-27] Split file intake into Content and Improvement buckets
• [2026-04-27] Add readme.human as the human-facing handoff companion
• [2026-04-27] Treat file intake as immediate review, not passive indexing
• [2026-04-27] Reframe the public site as an LLM Wiki creation handbook
• [2026-04-26] Treat the WordPress implementation as the production package surface
• [2026-04-26] Turn the UI/UX blueprint into the WordPress launch surface
• [2026-04-26] Launch complementary to UAIX first
• [2026-04-26] Use WordPress for the first launch surface
• [2026-04-26] Adopt the UAIX Project Handoff pattern
• [2026-04-26] Register structured content types early

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 12978
• Preview characters: 11938

---
uaix: "1.0"
type: decisions
title: "LlmWikis Decisions Log"
created: "2026-04-26"
updated: "2026-04-28"
author: "LlmWikis maintainers"
version: 9
---

# LlmWikis Decisions Log

## [2026-04-28] Preserve LlmWikis starter bundle source ownership

**Decision:** LlmWikis.org is the source publisher for `llm-wiki-starter-bundle.zip`. Dogfood consumers such as AIWikis.org should link to or consume the source-published bundle rather than publishing site-branded starter clones.

**Why:** AIWikis dogfood showed that a working example can become unclear if the consumer site ships an artifact named like its own starter product. The source relationship should be obvious from route names, package metadata, and public copy.

**Effect:** The starter bundle registry and public handoff state identify LlmWikis.org as the publisher. Consumer-site package evidence should record hashes and observations without rebundling or relabeling the starter ZIP.

**Boundary:** This does not make LlmWikis canonical for UAI-1 or Project Handoff. UAIX.org remains the source publisher for `uai1-project-handoff.zip`.

## [2026-04-28] Treat AIWikis dogfood as handoff package QA input

**Decision:** LlmWikis public handoff guidance should tell readers to verify actual package contents, not only copy the Project Handoff prose. Dogfood claims should check for `agent-file-handoff/`, the loaded `.uai` handoff set, source manifests, and release evidence.

**Why:** AIWikis.org exposed a concrete gap: a starter or exported package can cite UAIX and LlmWikis recommendations while missing active intake folders or several useful `.uai` handoff files.

**Effect:** The Agent Handoff guide now includes a package dogfood lesson. LlmWikis continues to mirror the UAIX-published `uai1-project-handoff.zip` for evaluation and does not become the canonical source for that plugin.

**Boundary:** This is non-normative handbook guidance. UAIX.org remains canonical for the Project Handoff package, UAI-1, validator behavior, conformance material, roadmap, and support boundaries.

## [2026-04-28] Treat LlmWikis as prelaunch until first production release

**Decision:** LlmWikis.org is launch-ready work, not a site with public SEO history. Obsolete prelaunch routes should be removed, drafted, returned as intentional gone/404 behavior, or documented as internal compatibility only.

**Why:** Carrying private iteration routes into first launch creates avoidable canonical and sitemap debt. The clean launch surface matters more than redirects for URLs that were never intentionally public.

**Effect:** `/what-is-an-llm-wiki/` is the canonical definition route. The old nested `/start-here/what-is-an-llm-wiki/` route is retired from managed pages instead of preserved as a 301 for public SEO. Sitemaps, `llms.txt`, navigation, templates, examples, and package references must not link to it.

**Boundary:** This does not affect UAIX.org, which is already live and must preserve important public URLs and redirects.

## [2026-04-28] Permanently retire public content-quality audit routes

**Decision:** The former `/content-quality/` audit route family is no longer public content and should return `410 Gone` from the active theme.

**Why:** The content-quality audit was a chore list and internal improvement input for maintainers and AI agents. Serving it as a public page confused site-improvement work with reader-facing handbook material.

**Effect:** Public navigation now points to Source Policy, Page Templates, Roadmap, and handbook pages instead of the retired audit route. Useful audit material is absorbed into public policy/templates/handbook copy or `.uai` progress/roadmap state; the raw intake files are archived after disposition.

**Boundary:** Future quality audits may inform public content after review, but they must not be published as audit-route pages or listed in `llms.txt`, `sitemap.xml`, header, footer, or crawler discovery by default.

## [2026-04-27] Archive already-dispositioned intake files

**Decision:** Agent File Handoff now uses `agent-file-handoff/Archive/` for files that have already received an explicit disposition.

**Why:** Once a dropped file has been applied, converted into `.uai`, roadmap, progress, or code state, deferred, or blocked, keeping it in `Content/` or `Improvement/` makes every new AI treat old work as fresh work. The archive preserves the source for humans without keeping it alive in routine AI intake.

**Effect:** `scripts/Invoke-UaiFileIntake.ps1` still indexes only `Content/`, `Improvement/`, and legacy `intake/`; it creates but ignores `Archive/`. Archived files are dead to AI unless a human explicitly names one or moves it back into an active bucket. Bucket-local README files are not part of the pattern; durable AI instructions live in `AGENTS.md` and `.uai` files, while human-facing explanation lives in root `readme.human`.

**Boundary:** The archive is not public content, not a discovery surface, not UAIX evidence, and not a trusted truth layer. It is retained source material for explicit human reference or repossession.

## [2026-04-27] Split file intake into `Content` and `Improvement` buckets

**Decision:** Agent File Handoff now uses `agent-file-handoff/Content/` for candidate public/editorial material and `agent-file-handoff/Improvement/` for audits, QA findings, SEO reports, bug notes, roadmap suggestions, and site-fix work.

**Why:** A single incoming folder made it too easy to treat improvement reports as public content. The content-quality audit was site-improvement work, not public handbook content by default.

**Effect:** `scripts/Invoke-UaiFileIntake.ps1` indexes both buckets and records the bucket in `.uai/intake-index.uai`. The legacy `agent-file-handoff/intake/` folder is compatibility-only and any files left there are treated as `Unsorted`. Public discovery/navigation should not list internal improvement reports unless a specific item is reviewed and converted into reader-facing content.

**Boundary:** This still avoids watchers, daemons, queues, manifests, and background services. Bucketed intake does not make files public truth or production-ready content.

## [2026-04-27] Add `readme.human` as the human-facing handoff companion

**Decision:** LlmWikis now dogfoods root `readme.human` beside `AGENTS.md` and `.uai/` files.

**Why:** Humans steering AI work need a plain briefing about what the AI sees, protects, needs clarified, and will not assume. That guidance is different from the machine/context role of `.uai` files.

**Effect:** New AI sessions read `AGENTS.md`, then `readme.human`, then the `.uai` bundle and intake index before broad work. Public LlmWikis handoff guidance can explain the concept while keeping the private root file out of discovery outputs.

**Boundary:** `readme.human` is a briefing aid, not an authority layer. It does not override `AGENTS.md`, `.uai/constraints.uai`, system instructions, repository rules, policy, or the human's current request.

## [2026-04-27] Treat file intake as immediate review, not passive indexing

**Decision:** LlmWikis follows the UAIX Agent File Handoff rule that any `needs-agent-review` file in `.uai/intake-index.uai` must be inspected, summarized, and dispositioned before unrelated broad work continues.

**Why:** Merely making files visible is not enough if an AI can refresh the index and then ignore the files. The handoff needs to force review of new local inputs without adding watchers, daemons, queue folders, or always-on services.

**Effect:** The intake helper marks non-executable files as `needs-agent-review`, and the AGENTS.md/.uai instructions require a concrete disposition: apply now, convert to durable state, defer with a reason, ask for clarification, or block.

**Boundary:** Intake review does not make dropped files public content, UAIX evidence, official validation, or production state. Normal source review, authority checks, release checks, and human approval still apply.

## [2026-04-27] Reframe the public site as an LLM Wiki creation handbook

**Decision:** Make the active public surface primarily teach how to build and maintain LLM Wikis, with UAIX/UAI-1 and adjacent protocol material preserved as non-normative case studies.

**Why:** The source reports identified that the existing site was too centered on UAIX/UAI-1 explainers to serve as a comprehensive reference for personal and team LLM Wiki builders. The highest-value move was to foreground the reusable architecture: immutable raw sources, compiled markdown wiki, compact schema, and the ingest/query/lint loop.

**Effect:** The theme now seeds Start Here, Architecture, Operations, Navigation, Schema Engineering, Examples, and Protocols and Case Studies routes. Root `llms.txt`, `robots.txt`, and `sitemap.xml` improve crawler discovery.

**Boundary:** This does not create an official generator, validator, certification, public MCP server, automated ingestion pipeline, open editing system, live benchmark integration, or multilingual support. It also does not move UAIX authority to LlmWikis.

**Content rule:** Public website copy should not attribute the LLM Wiki concept by creator name. It may link directly to the foundational idea file as a reference source.

## [2026-04-26] Treat the WordPress implementation as the production package surface

**Decision:** Update LlmWikis copy, handoff files, and package metadata to describe the current WordPress implementation as the production package surface rather than a throwaway preview.

**Why:** LlmWikis.org is preparing for first public launch. Leaving test-only language in the public surface or AI bundle would make the project look provisional, while claiming live public history would overstate the state.

**Effect:** Homepage/status copy, strategy addenda, publish metadata, handoff files, and release ZIPs now describe a launch-ready package while keeping roadmap-only features clearly gated.

**Boundary:** This does not widen support claims for live benchmark data, public MCP, open editing, multilingual support, or UAIX-certified handoff tooling.

## [2026-04-26] Turn the UI/UX blueprint into the WordPress launch surface

**Decision:** Implement the shippable parts of the UI/UX product blueprint in the current WordPress theme and plugin instead of waiting for a future replatform.

**Why:** The current priority is a working, testable public surface. WordPress can already host the command-center homepage, authority labels, route hubs, seed explainers, comparisons, glossary concepts, guide pages, and structured record scaffolding.

**Effect:** `llmwikis-knowledge-theme` now seeds the expanded launch route map, and `llmwikis-core` now registers structured content objects beyond models, benchmarks, and protocols.

**Boundary:** Live benchmark integrations, automated ingestion, public MCP, open editing, paid memberships, grants, multilingual support, and AI conversational search remain planned until the required tooling, policy, data sources, and review evidence exist.

## [2026-04-26] Launch complementary to UAIX first

**Decision:** Build LlmWikis first as a complementary, non-normative knowledge layer around UAIX, UAI, and adjacent AI interoperability ecosystems.

**Why:** The strategy report identifies UAIX as already authoritative for the normative standards surface, while LlmWikis has the clearest near-term opportunity as an explainer, glossary, implementation catalog, comparison, and community knowledge layer.

**Boundary:** Standalone expansion can be revisited after six to nine months of traffic, contributor, quality, and operating evidence.

## [2026-04-26] Use WordPress for the first launch surface

**Decision:** Use the existing WordPress Studio workspace for the initial launch surface.

**Why:** The current local project is already a WordPress Studio site, and the immediate priority is a working public surface with clear scope, not a full replatform.

Why This File Exists

This is a UAI AI Memory handoff file from llmwikis.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 decisions 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 Decisions Log; [2026-04-28] Preserve LlmWikis starter bundle source ownership; [2026-04-28] Treat AIWikis dogfood as handoff package QA input; [2026-04-28] Treat LlmWikis as prelaunch until first production release; [2026-04-28] Permanently retire public content-quality audit routes; [2026-04-27] Archive already-dispositioned intake files; [2026-04-27] Split file intake into Content and Improvement buckets; [2026-04-27] Add readme.human as the human-facing handoff companion. 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

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-1125 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LLMWikis Decisions Log",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-decisi-ea3341dc/",
    "source_reference":  "raw/system-archives/llmwikis/internal-memory-reorg/2026-05-01/.uai/decisions.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:ea3341dcd814df356117175d75884ef779814c09fd5667a52d189b3a03004239",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-04-28T22:09:16.0489169Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-1125",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}