Source-Site Outcome Routing

Source-site processing and AIWikis publication are different steps.

When LLMWikis.org, UAIX.org, Protocol5.com, or ɩ.com / JustAnIota.com processes an Improvement file, the first correct result may be a staged inventory, draft, roadmap item, implementation slice, 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.

The 2026-05-03 JustAnIota recovery exposed the route-ownership version of the same gap. AIWikis had preserved the 13-file JustAnIota intake batch, but the home page and generated route split still needed to show ɩ.com / JustAnIota.com as its own source system instead of leaving JustAnIota evidence inside generic archive memory.

The added source-system rule is:

If AIWikis preserves a source site's intake or current-source evidence, that evidence needs a named source guide, route family, coverage row, and claim boundary. It should not disappear under generic AIWikis memory.

The 2026-05-08 Symbiokinetic repair exposed the stale-index version of the same gap. Symbiokinetic.com had real source-site work and a local database seed, but its .uai/intake-index.uai still reflected the empty setup state and the four original Content reports remained active.

The added completion rule is:

After source-site work uses active Content or Improvement files, refresh the intake index, record dispositions, preserve accepted originals in AIWikis long memory when configured, run focused checks, and move originals to Archive before calling the handoff complete.

The later 2026-05-08 cross-site report audit exposed the exact-copy version of the same gap. Several recent source-site archive reports had public-safe summaries or source-site archive locations, but not exact raw AIWikis copies.

The added verification rule is:

Before saying recent reports made it to long-term memory, compare source-site archive/report hashes against AIWikis/raw/system-archives/, copy any missing originals, write a manifest, and add public-safe summary nodes.

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-03 ɩ.com / JustAnIota intake recovery is now treated as the newest source-system routing correction:

• ɩ.com is the visible brand and JustAnIota.com is the canonical host for compact-message tooling, public-site identity, implementation examples, and JustAnIota handoff state.
• AIWikis preserved 13 active JustAnIota Improvement originals in raw/system-archives/2026-05-03-justaniota-intake-processing.json, but that evidence must be discoverable through /justaniota/, /justaniota/source-memory-guide/, and /concepts/justaniota/.
• UAIX.org remains canonical for UAI-1 standards, validators, conformance, governance, and roadmap claims.
• The new memory does not make AIWikis the JustAnIota source authority and does not make JustAnIota a UAI-1 standards, validator, registry, certification, endorsement, or conformance authority.

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.

The 2026-05-08 Symbiokinetic content intake repair is now treated as the newest stale-index correction:

• Symbiokinetic.com remains the source for the public Symbiokinetic AI and AI Symbiokinetics knowledgebase.
• AIWikis preserved four active Content originals in raw/system-archives/2026-05-08-symbiokinetic-content-intake-preservation.json.
• The local source-site seed was verified through Studio WP-CLI: Symbiokinetic, AI Symbiokinetics Knowledgebase, seed version 1.1.0, and 63 published page/post/resource records.
• The correction does not prove production deployment, does not make AIWikis the Symbiokinetic.com authority, and does not claim academic settlement for Symbiokinetic AI or AI Symbiokinetics.

The 2026-05-08 recent report memory completion is now treated as the newest exact-copy correction:

• AIWikis compared recent source-site reports from 2026-05-07 through 2026-05-08 against raw-memory hashes.
• The correction does not prove production deployment, source authority transfer, certification, endorsement, or support commitments.

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.