Decisions

Decision: Preserve /org/reports/ as a legitimate organization-level docs/report namespace while adding site-owned report/evidence indexes under /{site}/reports/ for AIWikis, UAIX, LLMWikis, Protocol5, and JustAnIota.

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/uai-decisions-uai-2e3def18/
Source reference	.uai/decisions.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-14T01:07:21.3428089Z
Content hash	sha256:2e3def189c6f19178eee335335a4fd8cb65e3a46b237eacac1c298c4992e7e62
Import status	changed
Raw source layer	data/sources/aiwikis/uai-decisions-uai-2e3def189c6f.uai
Normalized source layer	data/normalized/aiwikis/uai-decisions-uai-2e3def189c6f.txt

Current File Content

Structure Preview

• Decisions
• 2026-06-13: Organization Reports And Site Reports Are Separate Valid Scopes
• 2026-05-25: Treat Each AIWikis Site Namespace As Its Own AI Wikisite
• 2026-05-22: Keep Commercial Source Memory Local-Only On Public AIWikis
• 2026-05-15: Make AIWikis Task-First While Keeping Deep Memory Layered
• 2026-05-09: Add Neurokinetic.com As A Source-Memory Participant
• 2026-05-08: Verify Recent Report Memory By Exact Hash
• 2026-05-08: Store Global Coding Standards In AIWikis Source-Side Wiki
• 2026-05-05: Preserve JustAnIota Short-Domain SEO Release Sweep
• 2026-05-04: Bound Generated Source Pages And Mark Skip Zones
• 2026-05-03: Add JustAnIota short domain / JustAnIota.com As A First-Class Source System
• 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

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: 47919
• Preview characters: 11404

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-06-13"
status: active
---

# Decisions

## 2026-06-13: Organization Reports And Site Reports Are Separate Valid Scopes

Decision: Preserve `/org/reports/` as a legitimate organization-level docs/report namespace while adding site-owned report/evidence indexes under `/{site}/reports/` for AIWikis, UAIX, LLMWikis, Protocol5, and JustAnIota.

Reason: LLMWikis guidance correctly warns against mixing site-owned memory at root-level generic routes, but that does not make organization-level memory invalid. Some subjects legitimately exist at organization scope and site scope with different meanings; for example, Michael Kappel material can be organization-level context while a specific site carries its own implementation-specific treatment.

Effect: AIWikis generated source pages now point to their source overview, site file index, site report index, UAI system index, provenance, site directory, and organization reports. `/org/reports/` remains the shared organization/cross-site report surface, while `/{site}/reports/` gives agents a crawlable single-site evidence path.

Boundary: This is information architecture and memory-routing guidance. It does not make AIWikis the source authority for sibling-site claims, and it does not allow root `/reports/`, `/files/`, or `/concepts/` memory indexes.

## 2026-05-25: Treat Each AIWikis Site Namespace As Its Own AI Wikisite

Decision: AIWikis.org must keep site-owned public memory under `/{site}/...`. The root site may list site namespaces through `/site/`, and shared organization/workspace guidance may live under `/org/`, but root memory indexes such as `/files/`, `/concepts/`, `/reports/`, `/browse/`, and `/browser/` are invalid except as redirects.

Reason: Root memory indexes let agents load source files, concepts, and reports from every source site during a targeted request. That breaks the workspace rule to resolve the target site first and causes AIWikis to behave like one mixed archive instead of a set of independent AI Wikisites.

Effect: Source-file generation now uses `/{site}/files/...`; global generated guidance uses `/org/...`; the directory lives at `/site/`; theme/plugin navigation and legacy redirects point away from root mixed-memory surfaces; LLMWikis wizard/spec guidance names the same rule; and `tools/Test-SiteScopedRoutes.ps1` fails route, link, and bare-URL violations.

Boundary: This is a public-routing and memory-isolation rule. It does not move source authority from source sites to AIWikis, does not prove production deployment, and does not require deleting historical source-side records that mention older routes as past evidence.

## 2026-05-22: Keep Commercial Source Memory Local-Only On Public AIWikis



Effect: AIWikis Core filters restricted source records out of public-host route lists, search records, sitemap/llms output, and direct Markdown routing. The AIWikis theme hides restricted navigation links and Workspace Site Browser entries on non-local hosts while preserving localhost access.


## 2026-05-15: Make AIWikis Task-First While Keeping Deep Memory Layered

Decision: AIWikis public navigation should start from reader tasks: start, search, topics, sources, files, reports, contact, and browse. Deep memory remains layered behind reviewed public pages, generated evidence, source-side wiki nodes, and raw archive manifests.

Reason: The active AIWikis audit reports found that the site had strong evidence and source boundaries but weak first-time discoverability. Long lists, insider labels, hidden contact/search paths, and stale hash-route drift made the public surface feel more like an internal archive than a usable memory system.

Effect: AIWikis now has visible `/search/` over packaged route records, task-first header/footer navigation, breadcrumbs, contextual route links, stale `/files/aiwikis/...` redirect recovery, a rewritten Home and Start Here, a public Memory and Site Structure guide, and source-side audit memory nodes.

Boundary: This improves AIWikis.org only. It does not create source authority for UAIX.org, LLMWikis.org, Protocol5.com, JustAnIota.com, or sibling sites, and it does not create hosted validation, automatic publication, certification, SDK, CLI, Search Console cleanup, CDN configuration, server headers, live deployment, or production monitoring.

## 2026-05-09: Add Neurokinetic.com As A Source-Memory Participant

Decision: AIWikis treats Neurokinetic.com as a reviewed source-memory participant for setup, local UAI/LLM Wiki routing, Agent File Handoff, and WordPress deployment-package boundaries.

Reason: The Neurokinetic local WordPress folder had no workspace-grade memory setup and carried a visible site-title typo. The human asked to use the UAIX AI Memory Package Wizard and LLMWikis LLM Wiki Setup Wizard pattern, point Neurokinetic.com to AIWikis.org, and standardize deployment docs to match other sites.

Effect: AIWikis now has `content/pages/075-neurokinetic-source-memory-guide.md`, `wiki/neurokinetic/index.md`, `wiki/concepts/neurokinetic-source-memory.md`, and `wiki/logs/neurokinetic-setup-2026-05-09.md`. The Neurokinetic source root now has local `.uai` hot memory, Agent File Handoff buckets, UAI startup files, an LLM Wiki memory plan, a custom theme, and root workspace package-builder registration.

Boundary: AIWikis preserves setup memory and routing guidance. It does not become Neurokinetic source authority, prove production deployment, create automatic LLM Wiki sync, or support clinical, diagnostic, certified, or settled-science claims.

## 2026-05-08: Verify Recent Report Memory By Exact Hash

Decision: AIWikis treats recent source-site report preservation as complete only after exact source-site hashes are present under `raw/system-archives/` and a manifest names any copied originals.

Reason: A cross-site audit for 2026-05-07 through 2026-05-08 found that several recent reports had source-site archive locations or public-safe summaries, but fourteen archived originals did not yet have exact AIWikis raw-memory copies.


Boundary: This decision preserves provenance. It does not publish raw reports, prove deployment, transfer source authority, certify claims, endorse projects, or create support commitments from speculative, theological, strategic, roadmap, ecosystem, or research reports.

## 2026-05-08: Store Global Coding Standards In AIWikis Source-Side Wiki

Decision: AIWikis stores global coding standards by implementation language and database engine under `wiki/global/coding-standards/`.

Reason: The human clarified that AIWikis.org is the LLM Wiki implementation for global coding standards, with one page per programming language plus SQL Server and MySQL standards. Keeping these records in the global wiki gives future agents a stable retrieval path before broad implementation work.

Effect: The global wiki now has a standards index plus C#, PowerShell, PHP/WordPress, TypeScript/JavaScript, Python, HTML/CSS, SQL Server, and MySQL pages. The root and global indexes link to the standards.


## 2026-05-05: Preserve JustAnIota Short-Domain SEO Release Sweep

Decision: Preserve the JustAnIota `JustAnIota short domain` short-domain SEO/release sweep as AIWikis long memory with a raw checksum manifest and source/log nodes.

Reason: The source-site decision deleted the obsolete separate `JustAnIota short domain` codebase, moved short-domain behavior into the canonical JustAnIota.com package, changed public human URL metadata to locale-prefixed route shape, and updated hot `.uai` memory. AIWikis needed a current long-memory record so future agents do not rely on stale 2026-05-03/2026-05-04 summaries or recreate a second short-domain install.

Effect: `raw/system-archives/2026-05-05-justaniota-short-domain-seo-release-sweep.json` records 24 copied current source/memory/discovery files with SHA-256 hashes. AIWikis added `wiki/sources/justaniota-short-domain-seo-release-2026-05-05.md` and `wiki/logs/justaniota-short-domain-seo-release-2026-05-05.md`, then updated the JustAnIota source guide, Intake Outcome Ledger, coverage and claim-boundary records, graph, and progress.

Boundary: AIWikis may state that the source-site decision is single-codebase redirect into JustAnIota.com. It must not claim production deployment, JustAnIota source authority, UAI-1 authority, conformance, certification, endorsement, hosted validation, SDK, or CLI support.

## 2026-05-04: Bound Generated Source Pages And Mark Skip Zones

Decision: AIWikis generated source-file pages must stay small enough for routine retrieval, while full source evidence remains in raw, normalized, archive, report, and hash-history layers.

Reason: Dogfooding LLM Wiki guidance against AIWikis found tracked generated-history files, stale generated source pages, raw/normalized mirrors, large JSON reports, and exact duplicate generated pages that make broad agent traversal expensive and noisy. The problem was structural, not just a one-off large file.

Effect: `tools/sync-source-files.ps1` now writes bounded public previews for generated source-file pages, records source byte/line counts, stops new routine generated-page history snapshots, and removes stale generated output unless explicit retention is enabled. `tools/smoke-test.ps1` fails oversized generated source-file pages. Hot memory, source handling, lessons, and recommendation adjustments now tell agents to use indexes, source guides, Markdown reports, bounded pages, and hashes before opening skip-zone paths.

Boundary: This does not delete old tracked `data/generated-history/` or `content/archive/generated-source-file-stale/` evidence. Removing those historical snapshots needs reviewer confirmation because they may be part of prior dogfood/recovery evidence.

## 2026-05-03: Add JustAnIota short domain / JustAnIota.com As A First-Class Source System

Decision: AIWikis treats JustAnIota short domain / JustAnIota.com as a fourth first-class source system beside UAIX.org, LLMWikis.org, and Protocol5.com.

Reason: The human pointed out that the AIWikis home page and wiki source list did not show JustAnIota distinctly even though AIWikis had preserved a 13-file JustAnIota intake-processing batch. Leaving that evidence under generic archive memory made the source boundary unclear and made it harder for humans and agents to find JustAnIota-specific tooling, identity, and handoff evidence.

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-06-13: Organization Reports And Site Reports Are Separate Valid Scopes; 2026-05-25: Treat Each AIWikis Site Namespace As Its Own AI Wikisite; 2026-05-22: Keep Commercial Source Memory Local-Only On Public AIWikis; 2026-05-15: Make AIWikis Task-First While Keeping Deep Memory Layered; 2026-05-09: Add Neurokinetic.com As A Source-Memory Participant; 2026-05-08: Verify Recent Report Memory By Exact Hash; 2026-05-08: Store Global Coding Standards In AIWikis Source-Side Wiki. 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-238 (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/aiwikis/files/uai-decisions-uai-2e3def18/",
    "source_reference":  ".uai/decisions.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:2e3def189c6f19178eee335335a4fd8cb65e3a46b237eacac1c298c4992e7e62",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-14T01:07:21.3428089Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-238",
    "duplicate_role":  "primary",
    "related_files":  [

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