Skip to content
aiWikis.org

Source-Site Outcome Routing

Source-site processing and AIWikis publication are different steps.

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/content-pages-031-source-site-outcome-routing-md-d0cc7ba1/
Source referencecontent/pages/031-source-site-outcome-routing.md
File typemd
Content categorypublic-content
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-03T02:35:18.0911143Z
Content hashsha256:d0cc7ba1802d9ff37b11816c31beef58d96b5eed515c1ea0ad5e4190417f5e1a
Import statuschanged
Raw source layerdata/sources/aiwikis/content-pages-031-source-site-outcome-routing-md-d0cc7ba1802d.md
Normalized source layerdata/normalized/aiwikis/content-pages-031-source-site-outcome-routing-md-d0cc7ba1802d.txt

Current File Content

Structure Preview

  • Source-Site Outcome Routing
  • What Went Wrong
  • Correct Flow
  • Outcome Types
  • Agent Rule
  • Current Correction
  • Non-Claims

Raw Version

---
title: "Source-Site Outcome Routing"
slug: "source-site-outcome-routing"
status: "working-draft"
trust_level: "reviewed"
source_status: "AIWikis public guidance for routing source-site processing outcomes into long-term memory and public documentation"
audience: "humans, ai-agents, maintainers"
---

# Source-Site Outcome Routing

Source-site processing and AIWikis publication are different steps.

When LLMWikis.org, UAIX.org, or Protocol5.com processes an Improvement file, the first correct result may be a staged inventory, draft, roadmap item, or pull-request package inside that source repository. That does not automatically change AIWikis.org, and it should not silently become public truth.

AIWikis.org changes only after a deliberate outcome-routing pass.

## What Went Wrong

On 2026-05-01, LLMWikis.org processed eight integration reports about LLM Wiki, UAI AI Memory, UAI Project Handoff, Codex, Cursor, Claude Code, Gemini, and layered publishing.

The source-site work was governed correctly: it created a staged review package in the LLMWikis repository, preserved unsupported claims as review items, and did not publish the reports directly. But AIWikis.org had no required follow-up step for the case where the human expected those source-site results to appear in AIWikis public memory.

The missing rule was:

> If a source-site processing job is expected to change AIWikis.org, create an explicit AIWikis outcome-routing pass and record what changed, what stayed staged, and what still needs review.

Without that pass, a source-site staging package can be real work while AIWikis.org appears unchanged.

The follow-up audit found a second, quieter version of the same problem. AIWikis had preserved useful staged LlmWikis artifacts and UAIX hot-context transfer evidence, but it still lacked one manifest proving that the original processed 2026-05-01 source-site reports were copied into raw long-term memory.

The added rule is:

> Outcome routing must reconcile original processed files against raw-memory manifests. Summaries, staged drafts, and hot-context snapshots do not replace raw original report preservation when AIWikis is expected to retain final memory.

The 2026-05-03 LlmWikis agentic-guidance pass exposed the next version of the same gap. AIWikis had older LlmWikis report and handoff preservation, but did not yet have one current-source digest for the May 2-3 roadmap input, public agentic orchestration guide, task-packet template, support-escalation checklist, discovery files, tests, and handoff updates.

The added current-source rule is:

> If source-site work changes public routes, implementation files, tests, machine-discovery files, starter assets, or support-boundary language after older reports were preserved, AIWikis needs a current-source digest before the work is considered long-term memory.

## Correct Flow

Use this flow when source-site intake is expected to affect AIWikis:

1. Process the files in the source repository.
2. Record a source-site inventory, disposition, publication plan, drafts, risks, and checks.
3. Compare original processed source files against AIWikis raw-memory manifests before relying on summaries or staged outputs.
4. If current implementation, discovery, starter, test, package, or support-boundary files changed after the original reports were preserved, create a current-source digest with copied files and checksums.
5. Keep raw reports review-gated unless they have been accepted for long memory or moved to archive.
6. Create an AIWikis outcome-routing entry that explains the source-site result in public-safe language.
7. Update AIWikis guides, atlas, playbook, coverage, claim boundaries, roadmap, lessons, recommendation state, and handoff files when the result changes durable memory.
8. Preserve reviewed, staged, archived, or current-source artifacts under `raw/system-archives/` only when explicitly accepted for AIWikis long memory, with file counts and checksums.
9. Run source sync, lint, smoke, handoff export, and package checks according to the files changed.
10. Deploy only after human review and the normal production workflow.

## Outcome Types

| Source-Site Result | AIWikis Action | Public Meaning |
| --- | --- | --- |
| Active reports still waiting for source-site review | Do not publish raw content; optionally record that review is pending | Not public truth |
| Staged inventory, plan, or draft package | Summarize the outcome and link it to review state | Candidate guidance |
| Accepted source-site edits | Refresh source memory guides, generated evidence, and route maps | Reviewed source-site change |
| Archived and dispositioned reports | Preserve raw memory, checksums, source/concept/log nodes, and ledger entry when useful | Long-term memory, not authority |
| Unsupported feature claim | Record as blocked or needs fact-checking | Not current support |
| Live production change | Require human deployment authorization and route verification | Not implied by local files |

## Agent Rule

When a user expects AIWikis changes after work in another source site, the agent must answer these questions before finishing:

- What changed in the source repository?
- Did AIWikis get an outcome-routing update?
- Which public AIWikis pages changed?
- Which raw or staged artifacts were preserved, if any?
- Which claims remain staged, blocked, or waiting for fact-checking?
- Were package or deployment steps run, or are they still pending human review?

If the answer is "AIWikis did not change," say that explicitly and explain why.

## Current Correction

The 2026-05-03 UAIX recent work sweep is now treated as the newest outcome-routing correction:

- UAIX.org remains canonical for UAI-1, AI Memory, Project Handoff, Agent File Handoff, validator/conformance material, package evidence, roadmap, and public support boundaries.
- AIWikis had older UAIX memory through 2026-05-01, but did not yet have one dated digest for the May 2-3 wizard setup URL, Agent File Handoff, optional LLM Wiki, roadmap, agentic-system, language, deploy-check, and wizard-polish outcomes.
- AIWikis now preserves 23 UAIX recent-work files in `raw/system-archives/2026-05-03-uaix-recent-work-sweep.json`.
- The public ledger, UAIX source guide, coverage matrix, claim register, source/concept/log wiki nodes, index, graph, progress, and decisions now explain what changed and what remains unsupported.
- The new memory does not create automatic sync, hosted import validation, repository writes, CI pickup, watchers, SDKs, CLIs, certification, endorsement, official adapters, conformance approval, or deployment.

The 2026-05-03 LLMWikis recent work sweep is now treated as the newest LlmWikis outcome-routing correction:

- LLMWikis.org remains the handbook source for LLM Wiki patterns, starter bundles, metadata, trust labels, governance, source policy, and AI-agent operating rules.
- AIWikis had LlmWikis memory through 2026-05-01, but did not yet have one dated digest for the May 2-3 roadmap input, agentic orchestration guide, support escalation checklist, starter-bundle files, route/discovery updates, tests, and handoff updates.
- AIWikis now preserves 25 LlmWikis recent-work files in `raw/system-archives/2026-05-03-llmwikis-recent-work-sweep.json`.
- The public ledger, LlmWikis source guide, coverage matrix, claim register, source/concept/log wiki nodes, index, graph, progress, and decisions now explain what changed and what remains unsupported.
- The new memory does not create public MCP support, A2A implementation, write API support, trace exporter support, live evaluation integration, managed runtime, managed service, SDK, CLI, certification, endorsement, automatic ingestion, automatic publication, or deployment.

The 2026-05-01 LLMWikis integration processing remains an earlier outcome-routing correction:

- LLMWikis.org remains the handbook source.
- The staged LLMWikis drafts remain review-gated and are not public truth by default.
- AIWikis records the workflow gap and the corrected rule in public guidance.
- AIWikis preserves the processed staged package as source-side long-memory evidence only because the human explicitly asked why the expected AIWikis change did not appear.
- AIWikis now also preserves the original UAIX and LlmWikis 2026-05-01 processed source-site archive files in `raw/system-archives/2026-05-01-source-site-report-preservation.json`.
- Vendor-specific Codex, Cursor, Claude Code, Gemini, MCP, API, automation, and hosted-service claims still require current source verification before public use.

## Non-Claims

This routing page does not create automatic publication, automatic repository writes, automatic LLM Wiki sync, public MCP support, hosted validation, SDK or CLI support, certification, endorsement, deployment, or source-site authority.

It makes the handoff visible: staged work is staged, public work is public, and AIWikis only changes when a reviewed or explicitly requested routing step says what changed.

Why This File Exists

This is a public content source 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 file is a focused source unit. Its path, headings, and metadata give an agent a retrieval handle that is smaller than loading the entire site or repository.

Structure

The file is structured around these visible headings: Source-Site Outcome Routing; What Went Wrong; Correct Flow; Outcome Types; Agent Rule; Current Correction; Non-Claims. 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-393 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Source-Site Outcome Routing",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/content-pages-031-source-site-outcome-routing-md-d0cc7ba1/",
    "source_reference":  "content/pages/031-source-site-outcome-routing.md",
    "file_type":  "md",
    "content_category":  "public-content",
    "content_hash":  "sha256:d0cc7ba1802d9ff37b11816c31beef58d96b5eed515c1ea0ad5e4190417f5e1a",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-03T02:35:18.0911143Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-393",
    "duplicate_role":  "primary",
    "related_files":  [

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