Handoff Pattern

AIWikis.org applies the UAIX Project Handoff pattern locally:

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/files/aiwikis/uai-handoff-pattern-uai-6e8f6e7a/
Source reference	.uai/handoff-pattern.uai
File type	uai
Content category	uai-system
Last fetched	2026-05-03T02:48:13.1276041Z
Last changed	2026-05-03T02:43:04.0352951Z
Content hash	sha256:6e8f6e7a28e4c9eb973b9adb994d098da003d75d6879e853129c5e522484bbf7
Import status	changed
Raw source layer	data/sources/aiwikis/uai-handoff-pattern-uai-6e8f6e7a28e4.uai
Normalized source layer	data/normalized/aiwikis/uai-handoff-pattern-uai-6e8f6e7a28e4.txt

Current File Content

Structure Preview

• Handoff Pattern
• Dogfood Correction

Raw Version

---
uai: "1.0"
type: handoff-pattern
project: "AIWikis.org"
updated: "2026-05-01"
status: active
---

# Handoff Pattern

AIWikis.org applies the UAIX Project Handoff pattern locally:

1. Read `AGENTS.md`.
2. Read `readme.human`.
3. Refresh `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`.
4. Load every `@uai[]` reference in `AGENTS.md`.
5. Inspect and disposition every `needs-agent-review` intake file before unrelated broad work.
6. Confirm source boundaries and targeted checks before public or package changes.

## Dogfood Correction

The first AIWikis package pass missed the active file-intake workspace and too many useful `.uai` handoff files. It also made the dogfood consumer look like the upstream starter-bundle publisher. Future source-package and package evidence checks must inspect actual ZIP contents, artifact names, routes, and publisher labels, not only the public documentation claims.

The next lapse was subtler: AIWikis recommended compact `.uai` / Project Handoff exports from reviewed wiki memory, but had no executable local export loop. The current correction is `tools/generate-handoff-export.ps1`, selected wiki nodes marked `handoff_export: include`, and lint/smoke/package checks that fail if the loop disappears. This remains AIWikis dogfood evidence, not hosted UAIX generator or certification support.

The current UAIX AI Memory Wizard work adds another dogfood lesson: a useful memory package needs populated operating decisions, not just empty files. AIWikis should preserve that lesson in its source-file pages and recommendations by pointing to UAIX wizard outputs for source authority, memory update timing, evidence ledger, conflict handling, testing, deployment, review, risk, rollback, receiver briefing, startup packet, and optional LLM Wiki memory-plan guidance.

AIWikis now also keeps a public Roadmap page so current, next, later, and blocked work can be read directly instead of reconstructed from handoff progress. The roadmap must stay bounded to AIWikis dogfood work and must not imply source-site authority or unsupported automation.

Protocol5.com is now a first-class AIWikis source system for Protocol5 parent-brand, Mathematics, UAI .NET package, route-contract, and implementation-mirror evidence. AIWikis should preserve Protocol5 memory in generated `/protocol5/...` pages and a reviewed source guide while keeping UAIX.org normative for UAI-1 standards claims and avoiding generated Prime/Fibonacci route-tree syncing.

The latest lapse was expectation routing: LLMWikis processed integration Improvement files into a governed staged package, but AIWikis did not change because no required cross-site outcome-routing pass existed. Future agents must state whether source-site processing changed AIWikis, update the Intake Outcome Ledger or Source-Site Outcome Routing page when it should, and preserve the boundary that staged source-site drafts are not public AIWikis truth.

The follow-up lapse was current-source coverage: older LlmWikis report preservation did not prove the newer agentic orchestration guide, task packet template, support escalation checklist, starter-bundle registry, discovery files, tests, or handoff state had reached AIWikis. Future agents must create a dated current-source digest when a source-site work session changes implementation, tests, discovery, starter assets, route behavior, or support-boundary language after older reports were already preserved.

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 handoff-pattern 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: Handoff Pattern; Dogfood Correction. 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

• Global File Index
• Reports

Provenance And History

• Current observation: 2026-05-03T02:48:13.1276041Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-210 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Handoff Pattern",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/uai-handoff-pattern-uai-6e8f6e7a/",
    "source_reference":  ".uai/handoff-pattern.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:6e8f6e7a28e4c9eb973b9adb994d098da003d75d6879e853129c5e522484bbf7",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-03T02:43:04.0352951Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-210",
    "duplicate_role":  "primary",
    "related_files":  [

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