Skip to content
aiWikis.org

Decisions

Decision: AIWikis preserves the May 2-3 LlmWikis recent-work state as a dated raw-memory sweep plus public-safe retrieval nodes, because the prior AIWikis memory only covered older LlmWikis preservation through 2026-0...

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/uai-decisions-uai-ab78eea1/
Source reference.uai/decisions.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-03T02:37:18.8323405Z
Content hashsha256:ab78eea15208add4e389c0f1919b4cab8a8d92c096dc1090ddd97d59d2258c62
Import statuschanged
Raw source layerdata/sources/aiwikis/uai-decisions-uai-ab78eea15208.uai
Normalized source layerdata/normalized/aiwikis/uai-decisions-uai-ab78eea15208.txt

Current File Content

Structure Preview

  • Decisions
  • 2026-05-03: Preserve Recent LlmWikis Agentic Orchestration And Support Work
  • 2026-05-03: Preserve Recent UAIX Wizard, Handoff, LLM Wiki, Roadmap, And Agentic-System Work
  • 2026-05-02: Preserve Protocol5 Reports And Improvement Designs As Long Memory
  • 2026-05-01: Preserve Original Processed Reports Before Treating AIWikis Memory As Complete
  • 2026-05-01: Add Source-Site Outcome Routing
  • 2026-05-01: Use AIWikis As UAIX Cold Memory, Not UAIX Authority
  • 2026-05-01: Add Protocol5.com As A First-Class Source System
  • 2026-04-30: Add Coverage And Claim Boundary Registers
  • 2026-04-30: Add A Cross-Site Memory Atlas And Operations Playbook
  • 2026-04-30: Add Source Memory Guides For UAIX.org And LLMWikis.org
  • 2026-04-30: Publish A Public Roadmap As The Planning Surface
  • 2026-04-30: Track UAIX AI Memory Wizard Protocol Outputs As Source Evidence
  • 2026-04-30: Expose Current Source Files With Provenance And Explanations
  • 2026-04-30: Rebuild With Compact Recovered-Content Pages, Not A Monolith
  • 2026-04-30: Add An Intake Outcome Ledger For Dropped-File Feedback
  • 2026-04-29: Make Project Handoff Export A Checked Local Dogfood Artifact
  • 2026-04-29: Adopt The Deep Cognitive Archive As Local AIWikis Architecture
  • 2026-04-29: Render Public Pages From Markdown Files
  • 2026-04-28: AIWikis Is The Long-Term System Memory Archive
  • 2026-04-28: AIWikis Consumes Source-Published Packages
  • 2026-04-28: WordPress ZIP entries must use forward slashes
  • 2026-04-28: Package Dogfood Must Inspect Real Handoff Files
  • 2026-04-28: Reviewed Seed Pages Must Import Into WordPress

Raw Version

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

---
uai: "1.0"
type: decisions
project: "AIWikis.org"
updated: "2026-05-03"
status: active
---

# Decisions

## 2026-05-03: Preserve Recent LlmWikis Agentic Orchestration And Support Work

Decision: AIWikis preserves the May 2-3 LlmWikis recent-work state as a dated raw-memory sweep plus public-safe retrieval nodes, because the prior AIWikis memory only covered older LlmWikis preservation through 2026-05-01.

Reason: The human asked whether today's and the last couple days of LlmWikis work ended up in the LLM Wiki. The coverage check showed partial memory: AIWikis had older LlmWikis internal-memory and report-preservation manifests, but not one current digest for the processed roadmap input, agentic orchestration guide, task packet template, support escalation checklist, starter-bundle registry, discovery files, tests, and handoff updates.

Effect: `raw/system-archives/2026-05-03-llmwikis-recent-work-sweep.json` records 25 copied LlmWikis files with byte counts, SHA-256 hashes, summaries, and dispositions. AIWikis added `wiki/sources/llmwikis-recent-work-sweep-2026-05-03.md`, `wiki/concepts/llmwikis-agentic-orchestration-support-current-state.md`, and `wiki/logs/llmwikis-recent-work-sweep-2026-05-03.md`, then updated the Intake Outcome Ledger, LlmWikis Source Memory Guide, Source-Site Outcome Routing, Memory Coverage Matrix, Claim Boundary Register, wiki index, graph, progress, AGENTS.md, readme.human, lessons, recommendation adjustments, and changelog.

Boundary: LLMWikis.org remains the handbook source for LLM Wiki patterns, starter bundles, metadata, trust labels, governance, source policy, and AI-agent operating rules. AIWikis memory does not create public MCP support, A2A implementation, write API support, trace exporter support, live eval integration, managed runtime, managed service, SDK, CLI, certification, endorsement, automatic ingestion, automatic publication, deployment, or source-site authority.

## 2026-05-03: Preserve Recent UAIX Wizard, Handoff, LLM Wiki, Roadmap, And Agentic-System Work

Decision: AIWikis preserves the May 2-3 UAIX recent-work state as a dated raw-memory sweep plus public-safe retrieval nodes, because the prior AIWikis memory only covered older UAIX preservation through 2026-05-01.

Reason: The human asked whether the work from the last couple days ended up in the LLM Wiki. The coverage check showed partial memory: AIWikis had older UAIX internal-memory and report-preservation manifests, but not one current digest for direct wizard setup URLs, `point_agent_urls`, `AGENT_FILE_HANDOFF_PLAN.md`, optional LLM Wiki location questions, agentic-system guidance, roadmap work, language sweeps, deploy checks, and final wizard polish.

Effect: `raw/system-archives/2026-05-03-uaix-recent-work-sweep.json` records 23 copied UAIX files with byte counts, SHA-256 hashes, summaries, and dispositions. AIWikis added `wiki/sources/uaix-recent-work-sweep-2026-05-03.md`, `wiki/concepts/uaix-wizard-file-handoff-llm-wiki-current-state.md`, and `wiki/logs/uaix-recent-work-sweep-2026-05-03.md`, then updated the Intake Outcome Ledger, UAIX Source Memory Guide, Source-Site Outcome Routing, Memory Coverage Matrix, Claim Boundary Register, wiki index, graph, progress, AGENTS.md, readme.human, generated source-file pages, source-sync reports, source-sync write retries, and smoke coverage.

Boundary: UAIX.org remains canonical for UAI-1, AI Memory, Project Handoff, Agent File Handoff, validator/conformance material, packages, roadmap, governance, and support claims. AIWikis memory does not create hosted import validation, automatic repository writes, automatic LLM Wiki sync, CI pickup, watchers, SDK, CLI, certification, endorsement, official adapter support, conformance approval, deployment, or source-site authority.

## 2026-05-02: Preserve Protocol5 Reports And Improvement Designs As Long Memory

Decision: AIWikis preserves Protocol5 report, modernization, and active Improvement design inputs as raw long-memory references with public-safe summaries, not as public truth or support evidence.

Reason: The human asked for Protocol5.com reports and Improvement docs to be processed into AIWikis for history and reference while the Protocol5 build was being fixed. The active screenshot drops also needed durable disposition before leaving the review bucket.

Effect: `raw/system-archives/2026-05-02-protocol5-report-preservation.json` records 12 copied files with byte counts, SHA-256 hashes, summaries, and dispositions. AIWikis added `wiki/sources/protocol5-report-preservation-2026-05-02.md`, `wiki/logs/protocol5-report-preservation-2026-05-02.md`, ledger entries, Protocol5 source-memory updates, graph records, and progress state. Protocol5 recorded the four active screenshot dispositions, moved them to `agent-file-handoff/Archive/2026-05-02/Improvement/`, and refreshed active intake to zero files.

Boundary: Protocol5.com remains the parent brand and UAI .NET implementation package source. UAIX.org remains normative for UAI-1. AIWikis memory does not create package conformance, certification, endorsement, hosted validation, deployment, automatic sync, or public truth from raw design/report files.

## 2026-05-01: Preserve Original Processed Reports Before Treating AIWikis Memory As Complete

Decision: AIWikis requires a raw original report preservation check when source-site processing is expected to become AIWikis long-term memory.

Reason: The 2026-05-01 deep dive found that AIWikis had useful summaries, UAIX hot-context transfer evidence, and LlmWikis staged outcome artifacts, but no single manifest proving that every original processed 2026-05-01 UAIX and LlmWikis source-site report had been copied into raw memory with checksums.

Effect: `raw/system-archives/2026-05-01-source-site-report-preservation.json` now records 38 copied files: 19 UAIX archive files and 19 LlmWikis archive files. AIWikis added `wiki/sources/source-site-report-preservation-2026-05-01.md`, `wiki/concepts/source-site-report-preservation.md`, and `wiki/logs/source-site-report-preservation-2026-05-01.md`, and updated the Intake Outcome Ledger, System Memory Archive, source guides, atlas, playbook, coverage matrix, claim register, lessons, recommendation adjustments, changelog, handoff state, and graph.

Boundary: This decision preserves provenance. It does not publish raw reports, promote staged LlmWikis drafts, create automatic repository writes, automatic LLM Wiki sync, hosted validation, public MCP support, SDK, CLI, certification, endorsement, deployment, or source-site authority.

## 2026-05-01: Add Source-Site Outcome Routing

Decision: AIWikis requires an explicit outcome-routing pass when a source repository processes intake and the human expects AIWikis public or long-memory surfaces to change.

Reason: LLMWikis processed eight integration Improvement reports into a governed staged review package. That was valid source-site work, but AIWikis.org did not visibly change because the cross-site system only described archive pulls and source sync, not the intermediate case where source-site staging should produce public-safe AIWikis feedback.

Effect: `content/pages/031-source-site-outcome-routing.md` now explains the workflow. The Intake Outcome Ledger, LLMWikis Source Memory Guide, Cross-Site Memory Atlas, Source Memory Operations Playbook, Memory Coverage Matrix, Claim Boundary Register, Roadmap, lessons, recommendation adjustments, changelog, AGENTS.md, readme.human, and handoff records now state that source-site staged work needs explicit routing before AIWikis changes. The processed LLMWikis staged package may be preserved as AIWikis long-memory evidence only because the human asked for this correction.

Boundary: This decision does not publish the staged LLMWikis drafts as handbook truth, does not create automatic publication, automatic repository writes, automatic LLM Wiki sync, hosted validation, public MCP, SDK, CLI, certification, endorsement, deployment, or source-site authority. LLMWikis.org remains the handbook source.

## 2026-05-01: Use AIWikis As UAIX Cold Memory, Not UAIX Authority

Decision: AIWikis will preserve bulky UAIX internal knowledge, source reports, proposal history, and pre-slim handoff snapshots as long-term cold memory while UAIX keeps routine `AGENTS.md`, `readme.human`, and `.uai` context concise.

Reason: UAIX had accumulated large research and progress files that were useful provenance but expensive to load in every agent session. AIWikis already owns the source-side archive, Intake Outcome Ledger, wiki nodes, graph, and source-memory guide model needed to preserve that knowledge without keeping it in UAIX hot context.

Effect: The 2026-05-01 transfer manifest `raw/system-archives/2026-05-01-uaix-internal-memory-reorg.json` records 23 copied UAIX files with SHA-256 hashes. AIWikis now has `wiki/sources/uaix-internal-memory-reorg-2026-05-01.md`, `wiki/concepts/uaix-active-context-diet.md`, and `wiki/logs/uaix-internal-memory-reorg-2026-05-01.md`, plus updated ledger, archive, guide, index, and graph records.

Boundary: AIWikis memory is not active UAIX truth until deliberately promoted back into UAIX source state. It does not create automatic sync, hosted import validation, repository writes, SDK, CLI, certification, endorsement, official vendor support, or validator-backed `.uai` conformance evidence. UAIX.org remains canonical for UAI-1 and public support claims.

## 2026-05-01: Add Protocol5.com As A First-Class Source System

Decision: AIWikis adds Protocol5.com as a reviewed source system beside UAIX.org and LLMWikis.org.

Reason: Protocol5.com carries Protocol5 parent-brand, Mathematics, UAI .NET Hub, package download, route-contract, compatibility mirror, and implementation-boundary evidence. Future humans and agents need that evidence visible on AIWikis with the same source-memory depth as the other source sites, while preserving the rule that UAIX.org remains normative for UAI-1 standards authority.

Effect: `content/pages/030-protocol5-source-memory-guide.md` now defines Protocol5 ownership, reading paths, update triggers, frozen Prime/Fibonacci boundaries, and non-claims. `tools/sync-source-files.ps1` now imports Protocol5 source files and generates `/protocol5/`, `/protocol5/public/`, `/protocol5/uai-system/`, `/protocol5/demos/`, `/protocol5/provenance/`, and `/protocol5/uai-system/files/...` routes. Source manifests, source-package metadata, Home, Start Here, Roadmap, Source Map, Cross-Site Memory Atlas, Source Memory Operations Playbook, Memory Coverage Matrix, Claim Boundary Register, docs, wiki memory, graph records, and smoke coverage now include Protocol5.

Boundary: Protocol5.com does not become the UAI-1 standards authority, validator authority, registry authority, roadmap authority, governance authority, certification authority, endorsement source, or conformance authority. AIWikis does not own Protocol5 packages, does not certify Protocol5 artifacts, and does not routinely sync generated Prime/Fibonacci numeric route trees.

## 2026-04-30: Add Coverage And Claim Boundary Registers

Decision: AIWikis adds a reviewed Memory Coverage Matrix and Claim Boundary Register.

Reason: Source guides, an atlas, and a playbook explain the memory system, but future agents also need a quick way to decide whether a domain is covered, partially covered, source-only, or blocked, and whether a claim is safe, source-routed, dogfood evidence, planned, or forbidden.

Effect: `content/pages/029-memory-coverage-matrix.md` now maps UAIX, LLMWikis, and AIWikis domains to source owners, AIWikis surfaces, coverage state, and update triggers. `content/pages/029-claim-boundary-register.md` now names safe claims, source-routed claims, dogfood evidence claims, blocked claims, planned-language rules, risky words, and AI-agent behavior. Home, Start Here, Roadmap, docs, handoff state, lessons, recommendation adjustments, source-side wiki memory, graph records, and smoke coverage now treat coverage and claim safety as first-class memory infrastructure.

Boundary: Coverage does not equal authority. The registers do not create UAIX certification, endorsement, conformance approval, hosted validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, deployment, package validation, source-site authority, or public safety for raw archive material.

## 2026-04-30: Add A Cross-Site Memory Atlas And Operations Playbook

Decision: AIWikis adds a reviewed Cross-Site Memory Atlas and Source Memory Operations Playbook.

Reason: Source-system guides explain UAIX.org, LLMWikis.org, and Protocol5.com individually, but AIWikis also needs a deeper operating layer that routes claims, artifacts, evidence flow, source sync, archive consolidation, handoff export, and package-ready documentation maintenance across all source sites.

Effect: `content/pages/027-cross-site-memory-atlas.md` now maps system roles, authority, artifact ownership, memory layers, evidence flow, claim routing, and failure modes. `content/pages/028-source-memory-operations-playbook.md` now gives future humans and agents a workflow for intake, source changes, UAIX-specific checks, LLMWikis-specific checks, archive consolidation, public pages, generated evidence, handoff export, packaging, definition of done, and stop conditions. Home, Start Here, Roadmap, docs, handoff state, lessons, recommendation adjustments, and smoke coverage now treat these as first-class public memory infrastructure.

Boundary: The atlas and playbook are AIWikis operating guidance. They do not make AIWikis the canonical UAIX or LLMWikis source, do not publish raw archives, do not create hosted upload/import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, package validation, deployment, or source-site authority claims.

## 2026-04-30: Add Source Memory Guides For UAIX.org And LLMWikis.org

Decision: AIWikis adds reviewed public source memory guides for UAIX.org, LLMWikis.org, and Protocol5.com.

Reason: The generated source-file pages expose detailed current files, but humans and agents still need a source-system atlas that explains what each site owns, which routes matter, how AIWikis preserves evidence, when memory should be updated, and which authority or support claims are forbidden.

Effect: `content/pages/018-uaix-source-memory-guide.md`, `content/pages/019-llmwikis-source-memory-guide.md`, and `content/pages/030-protocol5-source-memory-guide.md` now sit beside `/uaix/`, `/llmwikis/`, `/protocol5/`, `/files/`, `/concepts/`, and `/reports/`. Home, Start Here, Roadmap, docs, handoff state, lessons, recommendation adjustments, and smoke coverage treat them as first-class AIWikis memory surfaces.

Boundary: These pages are AIWikis memory guides. UAIX.org remains canonical for UAI-1, AI Memory, Project Handoff, Agent File Handoff, validator, conformance, packages, governance, roadmap, and support boundaries. LLMWikis.org remains the handbook source for LLM Wiki patterns, starter templates, metadata, trust labels, governance, source policy, and AI-agent rules. The guides do not create certification, endorsement, hosted import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, source-site authority, or live deployment claims.

## 2026-04-30: Publish A Public Roadmap As The Planning Surface

Decision: AIWikis adds a reviewed public Roadmap page that separates current support, next work, later research, blocked claims, and promotion rules.

Reason: Changelog, lessons, recommendation adjustments, source-file reports, and `.uai` progress each answer a different question. Without a roadmap, future humans and agents have to reconstruct priority and support status from scattered evidence.

Effect: `content/pages/017-roadmap.md` now summarizes the live local state, deployment drift, source-sync priorities, AI Memory Wizard dogfood, future source-manifest and export questions, and blocked claims. Home, Start Here, docs, handoff state, and smoke coverage now treat the roadmap as a first-class page.

Boundary: The roadmap is local AIWikis planning. It does not deploy the site, override UAIX or LLMWikis authority, create hosted import validation, automatic writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, or source-site support claims.

## 2026-04-30: Track UAIX AI Memory Wizard Protocol Outputs As Source Evidence

Decision: AIWikis treats the UAIX AI Memory Package Wizard protocol expansion as current source evidence in its documentation and source-file sync story.

Reason: The wizard is becoming the practical centerpiece of UAI AI Memory: it now generates populated memory operating files rather than empty starter shells. AIWikis needs to reflect that because it demonstrates how compact UAI memory packets can coexist with optional deeper LLM Wiki memory.

Effect: AIWikis public and handoff docs now name generated system profiles, receiver briefs, startup packets, overlay JSON, optional LLM Wiki memory plans, and the source-authority, memory-update, evidence-ledger, conflict-resolution, risk, and rollback policies carried through those files. The transparent source-file sync should keep current UAIX handoff and wizard source pages aligned after UAIX changes.

Boundary: AIWikis is still a dogfood and memory site. UAIX.org remains the AI Memory and UAI-1 authority. This decision does not create hosted upload/import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, or AIWikis-owned AI Memory standards support.

## 2026-04-30: Expose Current Source Files With Provenance And Explanations

Decision: AIWikis adds a transparent source-file sync layer that publishes focused file pages for current UAIX.org, LLMWikis.org, Protocol5.com, and AIWikis.org memory/system files while preserving source authority boundaries.

Reason: The recovery/import pass made source memory available, but the public site still leaned toward compact summaries. AIWikis needs to demonstrate the real architecture: current files, provenance, hashes, update history, generated explanations, and small route-addressable units that reduce prompt-size burden.

Effect: `tools/sync-source-files.ps1` now writes source-side raw copies under `data/sources/`, normalized comparison text under `data/normalized/`, hash history under `data/hashes/source-file-history.jsonl`, generated public source-system routes under `/uaix/`, `/llmwikis/`, and `/protocol5/`, individual file routes under `/uaix/uai-system/files/...`, `/llmwikis/uai-system/files/...`, and `/protocol5/uai-system/files/...`, global `/files/`, `/concepts/...`, `/reports/`, and source-file reports under `reports/`.

Boundary: The generated public view redacts local absolute Windows paths to protect public HTML. Source hashes are based on the unredacted files. AIWikis does not become the UAIX or LLMWikis authority, does not certify the files, and does not create hosted import validation, automatic repository writes, SDK, CLI, certification, or endorsement support.

## 2026-04-30: Rebuild With Compact Recovered-Content Pages, Not A Monolith

Decision: AIWikis adds a repeatable recovered-content pipeline that crawls public source/discovery/package surfaces, scans local processed archives, preserves raw `.md` and `.uai` inputs, deduplicates source groups, and publishes compact generated summary pages under topic indexes.

Reason: AIWikis is the real LLM Wiki example and needs recovered LLMWikis.org, UAIX.org, and AIWikis.org memory to be available through small, crawlable, linkable pages instead of one large aggregate page or a hidden raw archive.

Effect: `tools/reprocess-content.ps1` writes raw evidence under `sources/recovered/raw/`, generated pages and indexes under `content/pages/`, and audit reports under `reports/`. `aiwikis-core` now supports nested file-backed routes plus generated `robots.txt` and `sitemap.xml` discovery responses.

Boundary: Generated pages are public-safe summaries and provenance maps, not verbatim publication of raw archive reports. LLMWikis.org remains the handbook source, UAIX.org remains canonical for UAI-1, and AIWikis remains the dogfood memory/reference site.

## 2026-04-30: Add An Intake Outcome Ledger For Dropped-File Feedback

Decision: AIWikis adds an Intake Outcome Ledger as the reviewed public-safe feedback layer for dropped-file digestion outcomes.

Reason: The 2026-04-30 UAIX Improvement reports made the failure mode concrete: a file can be moved into an archive and even copied into long-term memory, while the human still cannot tell what work happened or where to view the resulting documentation. A robust LLM Wiki memory layer needs visible disposition, transfer evidence, changed surfaces, and blocked/deferred claims.

Effect: AIWikis preserved two UAIX reports in `raw/system-archives/uaix/`, added `raw/system-archives/2026-04-30-uaix-aiwiki-long-term-memory-ingest.json`, published `content/pages/016-intake-outcome-ledger.md`, added source/concept/log wiki nodes, updated `wiki/index.md`, `config/graph.jsonld`, lessons, recommendation adjustments, changelog, progress, and route/content maps.

Boundary: The ledger is reviewed documentation, not automatic ingestion. It does not create hosted upload/import validation, automatic repository writes, automatic LLM Wiki sync, queue workers, SDK/CLI support, certification, endorsement, legal guarantees, or UAIX authority. UAIX.org remains canonical for UAI-1 and public support claims.

## 2026-04-29: Make Project Handoff Export A Checked Local Dogfood Artifact

Decision: AIWikis now generates a local Project Handoff export from root handoff files, current `.uai` state, recommendation docs, intake scaffolding, and selected reviewed wiki nodes marked `handoff_export: include`.

Reason: The active AIWikis/LLMWikis/UAIX reports exposed that the recommendation "ship `.uai` export bundles directly from reviewed wiki nodes and decisions" was not happening. AIWikis had the right documentation and separate layers, but no executable bridge from reviewed deep memory to compact handoff packets.

Effect: `tools/generate-handoff-export.ps1` writes `dist/handoff/aiwikis-project-handoff/` and a ZIP. Wiki nodes now carry governance/source metadata; `tools/wiki-lint.ps1` requires the expanded metadata and at least one export-eligible node; `tools/smoke-test.ps1` checks the generated export; and `tools/package.ps1` includes the export in release evidence.

Boundary: This is local AIWikis dogfood evidence. It is not hosted UAIX generator support, public upload validation, SDK/CLI support, certification, endorsement, UAI-1 conformance evidence, or a promise that raw system archives are safe to export.

## 2026-04-29: Adopt The Deep Cognitive Archive As Local AIWikis Architecture

Decision: AIWikis adopts the Deep Cognitive Archive model as a local source-side architecture for separating public pages, compact Project Handoff or AI Memory packets, and slower reasoning memory.

Reason: The active Improvement report correctly identified that public pages, `.uai` handoff files, and long-form archive/wiki memory do different jobs. Public pages should stay readable, `.uai` files should stay compact and active, and the deep archive should preserve why, rejected alternatives, contradictions, modelling insufficiency, lineage, and graph relationships.

Effect: AIWikis added the reviewed `/deep-cognitive-archive/` public page, preserved the report under `raw/system-archives/aiwikis/`, retired the active intake file under `agent-file-handoff/Archive/`, added source/concept/log wiki nodes, updated `config/graph.jsonld`, and recorded the disposition in handoff docs and package checks.

Boundary: Deep Cognitive Archive metadata is an AIWikis local extension. Numeric confidence, mandatory `uai_id`, and graph JSON-LD export must not be described as UAIX certification, universal LLMWikis baseline, hosted validation support, or upstream endorsement without source-site evidence.

## 2026-04-29: Render Public Pages From Markdown Files

Decision: AIWikis abandons the WordPress Page seed/import strategy. Reviewed public pages now live in `content/pages/` during development, are packaged into `aiwikis-core/data/pages`, and are rendered directly by `aiwikis-core` at matching public routes.

Reason: This is a development environment for building AIWikis.org content. Requiring activation hooks, admin repair actions, or database reseeding after document edits makes content iteration brittle and deployment harder.

Effect: `aiwikis-core` no longer inserts or updates WordPress `page` posts for reviewed content. The plugin resolves `/`, `/start-here/`, `/source-packages/`, and other one-segment public routes from the Markdown file index at request time. Package checks now require `aiwikis-core/data/pages/*.md` and the file-backed router instead of `data/seed/pages` plus importer code.

Boundary: Raw archive reports, source snapshots, and private handoff files still do not become public pages automatically. They must be converted into reviewed Markdown pages before public rendering.

## 2026-04-28: AIWikis Is The Long-Term System Memory Archive

Decision: AIWikis is the long-term memory archive for already-dispositioned UAIX.org and LlmWikis.org archive inputs. Source sites still process files normally; after disposition, AIWikis can pull archive material into `raw/system-archives/`, remove the source archive files, and compile safe summaries, wiki nodes, graph records, lessons, and recommendation adjustments.

Reason: UAIX and LlmWikis archives were dead to routine intake after disposition, which kept old reports from distracting source-site agents but also scattered the deep reasoning. AIWikis is the right working example for the LLM Wiki recommendation because it can keep high-resolution memory without making the public source sites carry every internal report.

Effect: The first sweep moved 5 UAIX archive files and 16 LlmWikis archive files into AIWikis raw system memory, copied and retired 4 active AIWikis intake records, added the System Memory Archive public page, and added source/concept/log nodes plus graph triples.

Boundary: AIWikis archive memory does not replace UAIX.org as UAI-1 authority or LlmWikis.org as the handbook source. Raw archive files remain out of public HTML, discovery routes, and WordPress upload packages unless converted into reviewed public summaries.

## 2026-04-28: AIWikis Consumes Source-Published Packages

Decision: AIWikis must not publish `aiwikis-starter-pack.zip`. LlmWikis.org remains the source publisher for `llm-wiki-starter-bundle.zip`, UAIX.org remains the source publisher for `uai1-project-handoff.zip`, and AIWikis is the end-user dogfood site that consumes and observes both. For practical wp-admin installation, AIWikis may mirror the UAIX-owned `uai1-project-handoff.zip` into `AIWikis-Publish` as a separate plugin artifact.

Reason: The first AIWikis package pass was a valid working example in spirit, but its route names, ZIP name, and starter-pack copy made the consumer site look like an upstream package authority. That blurred the public recommendation.

Effect: AIWikis now exposes source-package references, not an AIWikis-branded starter download. Package scripts remove obsolete `aiwikis-starter-pack*.zip` outputs, mirror the UAIX Project Handoff plugin for upload convenience, release evidence records source-package ownership, and public copy routes through `/source-packages/`.

Boundary: This preserves AIWikis dogfood evidence without moving source authority away from LlmWikis or UAIX. The mirrored UAIX plugin must not be renamed as an AIWikis package or nested inside AIWikis theme/plugin ZIPs.

## 2026-04-28: WordPress ZIP entries must use forward slashes

Decision: AIWikis distributable WordPress ZIPs must write archive entry paths with `/` separators and smoke tests must fail packages that contain Windows `\` separators.

Reason: The first `aiwikis-authority-theme-v0.1.0.zip` artifact contained `aiwikis-authority\style.css`. Local root checks could parse that path, but wp-admin upload reported the theme as missing `style.css` because installable WordPress packages need standard ZIP paths.

Effect: `tools/package.ps1` now creates ZIPs through `System.IO.Compression.ZipArchive` with normalized forward-slash entry names, and `tools/smoke-test.ps1` keeps separator-neutral root parsing while adding a portable-path check.

Boundary: This is package installability evidence, not deployment, certification, endorsement, or a change to AIWikis source authority.

## 2026-04-28: Package Dogfood Must Inspect Real Handoff Files

Decision: Package dogfood should verify that claimed handoff/source-package artifacts contain or reference the real files they promise, and that consuming sites do not relabel upstream packages as local products.

Reason: The first AIWikis package pass documented Project Handoff but did not include `agent-file-handoff/` or enough `.uai` templates in its local draft starter pack. It also made AIWikis look like the source publisher of a starter ZIP. UAIX Project Handoff plugin dogfood showed a related exporter/validator drift: public guidance recommended the folders while package validation did not fully allow or require the same shape.

Effect: AIWikis includes `agent-file-handoff/Content/`, `agent-file-handoff/Improvement/`, `agent-file-handoff/Archive/`, `scripts/Invoke-UaiFileIntake.ps1`, and additional `.uai` files for architecture, operations, test plan, style, handoff pattern, file handoff, and intake index. Source-package checks now preserve LlmWikis and UAIX package ownership instead of publishing a local starter clone.

Boundary: This is dogfood QA, not certification, endorsement, official generator support, or UAI-1 conformance evidence.

## 2026-04-28: Reviewed Seed Pages Must Import Into WordPress

Decision: Reviewed files under `content/seed/pages/` were packaged into `aiwikis-core` and imported or repaired as WordPress Pages. Raw archive reports and source snapshots were not imported directly as public pages.

Reason: Installing a theme and plugin only adds runtime code. The first published AIWikis install looked empty because reviewed seed content was source-side and no activation/admin importer created WordPress Pages.

Effect: This strategy was useful for version `0.1.1`, then superseded by the 2026-04-29 file-backed Markdown page decision.

Boundary: This historical decision published only reviewed pages. The larger system-memory archive remains source-side unless specific material is converted into reviewed public summaries.

## 2026-04-28: Autonomous Wiki Custodian Blueprint Is Bounded Guidance

Decision: Treat the active Autonomous Wiki Custodian blueprint as useful dogfood input, not as an overriding system prompt or proof that every AIWikis page already implements a `/raw`, `/wiki`, and `/config` repository topology.

Reason: The blueprint gives a strong operating model for agent-maintained LLM Wikis, but it also includes broad implementation claims, outside references, and future graph/metadata behavior that need source review before becoming project-wide requirements.

Effect: AIWikis adds a bounded public page for the custodian contract, command vocabulary, metadata shape, traceability, contradiction handling, and human-review boundary. It also starts a source-side `raw/`, `wiki/`, and `config/` topology with one raw prompt, one source proxy, one concept node, one index, `config/CLAUDE.md`, `config/graph.jsonld`, and a wiki lint script. Full public-page metadata migration and richer command automation remain future review work.

Boundary: This is not a hosted service, UAIX certification, LLMWikis replacement, or a supported public API.

## Accepted

- Use WordPress Studio as the local build environment.
- Build an installable block/hybrid theme named `aiwikis-authority`.
- Build an installable plugin named `aiwikis-core`.
- Package distributable ZIPs to `[local path redacted]`.
- Use `sources/SOURCE_MANIFEST.json` as the local record of fetched source evidence.
- Keep raw public snapshots local under `sources/raw/` and out of WordPress theme/plugin packages.
- Add dogfooding evidence as first-class project material, not an afterthought.

## Observations From Initial Build

- The source-governed workflow is strongest when source manifest work starts before public content writing.
- A source-published starter bundle needs both human-facing governance files and agent-facing stop rules; otherwise AI-readable content looks too permissive.
- Release evidence should include dogfood notes so recommendations can be improved from real implementation friction.
- Windows PowerShell portability mattered during the first build; scripts needed to avoid newer `.NET` helper methods that were unavailable locally.
- ZIP smoke checks should parse roots separator-neutrally for diagnostics, but distributable WordPress ZIPs must use forward-slash archive entries.
- Release evidence logs should avoid local absolute paths.
- Source discovery should preserve failed observations, including missing or not-yet-deployed discovery routes.
- Source-package naming is part of the boundary: a dogfood consumer should not introduce a branded ZIP name that implies upstream ownership.
- Mirroring an upstream plugin into a local publish folder can be useful dogfood ergonomics only when the filename, manifest, checksum, and install guidance preserve the upstream publisher.

## Proposed Changes

- Future dogfood guidance should recommend a dedicated lessons/source-observations folder for consumer sites.
- Future source-manifest guidance should distinguish fetched raw snapshots from public citation records and package-safe summaries.
- Future Windows WordPress publication guidance should recommend PowerShell 5.1-compatible helpers or declare a newer minimum runtime.

## Rejected Changes

- Do not publish raw fetched source snapshots inside installable theme/plugin packages.
- Do not treat AIWikis.org public pages as canonical UAI-1 or LLMWikis policy.
- Do not publish `aiwikis-starter-pack.zip`.

## Open Questions

- Should AIWikis.org eventually expose a public static source manifest file at the web root or only through the plugin REST route?
- Should future LlmWikis starter bundles include sample `.well-known` discovery files or keep those as deployment instructions?
- What review cadence should apply after the first live WordPress import?

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: Decisions; 2026-05-03: Preserve Recent LlmWikis Agentic Orchestration And Support Work; 2026-05-03: Preserve Recent UAIX Wizard, Handoff, LLM Wiki, Roadmap, And Agentic-System Work; 2026-05-02: Preserve Protocol5 Reports And Improvement Designs As Long Memory; 2026-05-01: Preserve Original Processed Reports Before Treating AIWikis Memory As Complete; 2026-05-01: Add Source-Site Outcome Routing; 2026-05-01: Use AIWikis As UAIX Cold Memory, Not UAIX Authority; 2026-05-01: Add Protocol5.com As A First-Class Source System. 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-326 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Decisions",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/uai-decisions-uai-ab78eea1/",
    "source_reference":  ".uai/decisions.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:ab78eea15208add4e389c0f1919b4cab8a8d92c096dc1090ddd97d59d2258c62",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-03T02:37:18.8323405Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-326",
    "duplicate_role":  "primary",
    "related_files":  [

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