Skip to content
aiWikis.org

LlmWikis Decisions Log

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

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-decisions-433df5f0/
Source referenceraw/system-archives/llmwikis/recent-work-sweep/2026-05-03/.uai/decisions.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-03T02:25:10.5277044Z
Content hashsha256:433df5f02421b03003a2cdaba2d53d83fc697c5012594197998c66f093177bfb
Import statusnew
Raw source layerdata/sources/aiwikis/raw-system-archives-llmwikis-recent-work-sweep-2026-05-03-uai-decisions-uai-433df5f02421.uai
Normalized source layerdata/normalized/aiwikis/raw-system-archives-llmwikis-recent-work-sweep-2026-05-03-uai-decisions-uai-433df5f02421.txt

Current File Content

Structure Preview

  • LlmWikis Decisions Log
  • [2026-05-03] Add bounded agentic support escalation
  • [2026-05-03] Add bounded agentic orchestration guidance
  • [2026-05-02] Convert ecosystem-strategy intake into gated roadmap state
  • [2026-05-01] Promote staged integration drafts into public seeded content
  • [2026-05-01] Use AIWikis as LlmWikis cold memory, not handbook authority
  • [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] Retire public content-quality audit routes
  • [2026-04-27] Use bucketed Agent File Handoff intake
  • [2026-04-27] Add readme.human as the human-facing handoff companion
  • [2026-04-27] Reframe the public site as an LLM Wiki creation handbook
  • [2026-04-26] Use WordPress for the first launch surface

Raw Version

---
uaix: "1.0"
type: decisions
title: "LlmWikis Decisions Log"
created: "2026-04-26"
updated: "2026-05-03"
author: "LlmWikis maintainers"
version: 14
---

# LlmWikis Decisions Log

## [2026-05-03] Add bounded agentic support escalation

**Decision:** LlmWikis should include support escalation guidance for orchestrated runs as part of the public agentic-agent handbook path.

**Why:** Agentic guidance needs a practical stop path. Agents should know what to do when a run hits conflicting sources, stale claims, private data, missing authority, failed tools, missing checks, or unsupported public capability requests.

**Effect:** `/guides/llm-wiki-agentic-orchestration/`, `/for-ai-agents/`, the starter-bundle `llm-wiki/agent/SUPPORT_ESCALATION_CHECKLIST.md`, tests, and handoff state now explain how to stop, preserve evidence, classify the trigger, and ask the right reviewer.

**Boundary:** This does not create a public runtime, support service, MCP server, A2A implementation, write API, trace exporter, live eval integration, managed service, official adapter, SDK, CLI, certification, endorsement, or UAIX support claim.

## [2026-05-03] Add bounded agentic orchestration guidance

**Decision:** LlmWikis should publish `/guides/llm-wiki-agentic-orchestration/` as practical how-to guidance for using LLM Wikis with agentic agents and orchestration layers.

**Why:** The 2026-05-02 ecosystem strategy created useful roadmap state, but readers also need a concrete operating pattern now: read governed wiki memory before a run, carry compact task context during orchestration, stage proposed updates, preserve trace/evidence inputs, and promote only through review.

**Effect:** The public guide, starter-bundle `llm-wiki/agent/ORCHESTRATION_RUNBOOK.md` and `llm-wiki/agent/TASK_PACKET_TEMPLATE.md`, Guides hub, route metadata, `llms.txt`, `sitemap.xml`, public-surface and starter-bundle tests, roadmap gate, and handoff state now describe LLM Wikis as governed source memory around agentic runs.

**Boundary:** This does not create a public MCP server, A2A implementation, write API, trace exporter, live eval integration, managed runtime, official adapter, SDK, CLI, certification, endorsement, automated ingestion, or UAIX support claim.

## [2026-05-02] Convert ecosystem-strategy intake into gated roadmap state

**Decision:** The Improvement intake `Where we go from here LLMWikis.md` is useful strategy input, but it is not public report copy. Convert it into roadmap/progress state that positions LlmWikis as a governed knowledge layer for existing agent runtimes, managed platforms, guardrails, and evaluation systems.

**Why:** The report contains durable product direction, but it also includes time-sensitive vendor landscape claims and citation placeholders. Publishing it directly would risk unsupported public claims.

**Effect:** Roadmap state now includes source-reviewed ecosystem landscape/recipe work, read-only MCP proof surfaces, staged write proposal contracts, A2A-style maintainer patterns, trace/eval starter packs, governed-knowledge benchmark criteria, verified integration programs, and selective managed private deployment ideas as gated candidates.

**Boundary:** This does not create current public MCP support, write APIs, A2A implementation, live eval integrations, compatibility badges, managed services, certification, endorsement, SDK, CLI, official UAIX tooling, or UAI-1 conformance evidence. Public use of vendor/platform comparisons requires fresh review against official sources.

## [2026-05-01] Promote staged integration drafts into public seeded content

**Decision:** The staged Improvement drafts for Codex usage, LLM Wiki/AI Memory/Project Handoff boundaries, review-gated publication, agent guidance, and security/privacy are now real LlmWikis public content instead of parked review artifacts.

**Why:** The drafts had stayed in `agent-file-handoff/Improvement/staged-site-drafts/`, which meant the system recorded the recommendations but the site did not visibly teach them. The user explicitly asked to make those files real content.

**Effect:** The public theme seeds `/guides/using-llm-wiki-with-codex/`, `/guides/llm-wiki-ai-memory-project-handoff/`, and `/governance/review-gated-publication-model/`. Existing For AI Agents, Security and Privacy, Agent Handoff Patterns, Guides, Governance, `llms.txt`, and `sitemap.xml` now reflect the promoted guidance.

**Boundary:** Promotion does not make dropped reports automatic truth, does not create public MCP, open editing, automatic publication, official Codex/Cursor/Claude/Gemini adapters, SDK, CLI, certification, endorsement, hosted import, or public write APIs. UAIX.org remains canonical for UAI-1, AI Memory, Project Handoff, schemas, registry, validator behavior, roadmap, governance, and support boundaries.

## [2026-05-01] Use AIWikis as LlmWikis cold memory, not handbook authority

**Decision:** LlmWikis keeps routine agent context concise and moves bulky handoff history, old progress detail, and pre-slim snapshots into AIWikis long-term memory.

**Why:** The handoff bundle had accumulated too much historical detail. That made routine startup expensive and worked against the public guidance that hot context should stay small.

**Effect:** AIWikis now preserves 16 selected LlmWikis files under `raw/system-archives/llmwikis/internal-memory-reorg/2026-05-01/` with transfer evidence in `raw/system-archives/2026-05-01-llmwikis-internal-memory-reorg.json`. LlmWikis hot files now carry current truth and pointers instead of long history.

**Boundary:** AIWikis memory is not active LlmWikis truth until promoted back into LlmWikis `.uai`, `AGENTS.md`, `readme.human`, public handbook copy, code, tests, release notes, package evidence, or roadmap state. The transfer does not create automatic sync, hosted validation, repository writes, SDK, CLI, certification, endorsement, official vendor support, or UAI-1 conformance evidence.

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

**Decision:** LlmWikis.org is the source publisher for `llm-wiki-starter-bundle.zip`.

**Why:** Package names become authority signals. Dogfood consumers should not publish site-branded starter clones that obscure the source relationship.

**Effect:** AIWikis and other consumers should link to or consume the LlmWikis source-published bundle rather than relabeling it.

**Boundary:** This does not make LlmWikis canonical for UAI-1 or Project Handoff. UAIX.org remains canonical for those records.

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

**Decision:** LlmWikis handoff guidance should tell readers to verify actual package contents, not only copy Project Handoff prose.

**Why:** AIWikis dogfood exposed that a starter or export can cite UAIX/LlmWikis recommendations while missing active intake folders or useful `.uai` files.

**Effect:** The Agent Handoff guide tells readers to check `agent-file-handoff/`, loaded `.uai` files, manifests, and release evidence before claiming dogfood.

**Boundary:** This remains non-normative handbook guidance. UAIX.org remains canonical for Project Handoff package behavior and support claims.

## [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.

**Why:** Carrying private iteration routes into first launch creates canonical and sitemap debt.

**Effect:** `/what-is-an-llm-wiki/` is the canonical definition route. The old nested `/start-here/what-is-an-llm-wiki/` route is retired rather than preserved as a public SEO redirect.

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

**Decision:** The former `/content-quality/` route family returns `410 Gone`.

**Why:** The audit was internal improvement input, not reader-facing handbook content.

**Effect:** Useful audit material is absorbed into policy, templates, handbook copy, roadmap/progress state, or future implementation work. Raw audit files stay out of public navigation and discovery.

## [2026-04-27] Use bucketed Agent File Handoff intake

**Decision:** Active intake uses `agent-file-handoff/Content/` for candidate public/editorial material and `agent-file-handoff/Improvement/` for audits, QA, SEO, bug notes, roadmap suggestions, and site-fix work. `Archive/` is dead to routine intake after disposition.

**Why:** A single incoming folder made improvement reports too easy to treat as public content, and keeping processed files active made each new AI reprocess old work.

**Effect:** The intake helper indexes active buckets, records route hints and checksums, and marks non-executable files as `needs-agent-review`. Agents must inspect and disposition every pending file before unrelated broad work.

**Boundary:** No watchers, daemons, queues, manifests, cron loops, background services, or bucket-local README instructions are part of the base pattern.

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

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

**Why:** Humans steering AI work need a plain briefing about what to clarify and what the AI will defend.

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

## [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.

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

**Boundary:** This does not create a public MCP server, automated ingestion pipeline, official generator, certification, endorsement, live benchmark system, open editing, or multilingual support.

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

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

**Why:** The immediate priority is a working public handbook and package path, not a full replatform.

**Boundary:** MediaWiki, GitBook, DokuWiki, Wiki.js, Docusaurus, Astro/Starlight, and hybrid stacks remain future candidates if the project outgrows WordPress.

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 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-05-03] Add bounded agentic support escalation; [2026-05-03] Add bounded agentic orchestration guidance; [2026-05-02] Convert ecosystem-strategy intake into gated roadmap state; [2026-05-01] Promote staged integration drafts into public seeded content; [2026-05-01] Use AIWikis as LlmWikis cold memory, not handbook authority; [2026-04-28] Preserve LlmWikis starter bundle source ownership; [2026-04-28] Treat AIWikis dogfood as handoff package QA input. 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-117 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LlmWikis Decisions Log",
    "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-decisions-433df5f0/",
    "source_reference":  "raw/system-archives/llmwikis/recent-work-sweep/2026-05-03/.uai/decisions.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:433df5f02421b03003a2cdaba2d53d83fc697c5012594197998c66f093177bfb",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-03T02:25:10.5277044Z",
    "import_status":  "new",
    "duplicate_group_id":  "sfg-117",
    "duplicate_role":  "primary",
    "related_files":  [

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