File Handoff

AIWikis.org uses active local drop buckets for loose files that arrive outside normal source fetches.

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/uai-file-handoff-uai-2df3d548/
Source reference	.uai/file-handoff.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-22T01:39:35.6398570Z
Content hash	sha256:2df3d5482d8e04571bc31f274223ac052c7c220fc9b4cbe0bebeabdf3b42b8d5
Import status	changed
Raw source layer	data/sources/aiwikis/uai-file-handoff-uai-2df3d5482d8e.uai
Normalized source layer	data/normalized/aiwikis/uai-file-handoff-uai-2df3d5482d8e.txt

Current File Content

Structure Preview

• File Handoff
• Buckets
• Disposition Rule
• Boundary
• System Archive Extension
• 2026-06-13 Source-Site Archive Retirement
• 2026-06-11 Teleodynamic Source-Memory Setup
• 2026-06-12 CreativeExpansion Source-Memory Setup
• 2026-06-22 CategoryHierarchies Source-Memory Setup

Raw Version

---
uai: "1.0"
type: file-handoff
project: "AIWikis.org"
updated: "2026-06-22"
status: active
---

# File Handoff

AIWikis.org uses active local drop buckets for loose files that arrive outside normal source fetches.

## Buckets

- `agent-file-handoff/Content/`: candidate public/editorial material.
- `agent-file-handoff/Improvement/`: audits, QA findings, SEO reports, bug notes, package observations, and site-fix work.
- No default `agent-file-handoff/Archive/`: already-dispositioned source files are preserved in `raw/system-archives/` with checksums and a manifest, then removed from source-site intake unless a human explicitly keeps a named file active.

## Disposition Rule

Every `needs-agent-review` file must be summarized and given one disposition before unrelated broad work continues: apply now, convert into roadmap/progress state, defer with a reason, ask for clarification, or block as unsafe/out of scope.

## Boundary

Dropped files are local project inputs. They are not public truth, production content, certification evidence, or release artifacts until reviewed and promoted through normal source, content, and package checks.

## System Archive Extension

AIWikis has an additional final-memory step for the cross-site system. After UAIX.org, LlmWikis.org, Protocol5.com, or AIWikis processes a dropped file normally, AIWikis preserves the original in `raw/system-archives/` as long-term memory with checksums and a manifest. The source-site copy should then be removed after evidence is verified unless the human explicitly keeps a named file active.

Each transfer should also update the Intake Outcome Ledger or a reviewed successor page so the human can see what happened to the file, where the raw copy lives, which public/source-side surfaces changed, and which claims were deferred or blocked.

If the source site creates staged output but has not yet preserved the original reports, AIWikis may still record a public-safe outcome and preserve the staged package when the human explicitly asks for AIWikis visibility. That is source-site outcome routing, not source-site publication or authority transfer.

This does not change the active intake rule: current `Content/` and `Improvement/` files still need review and disposition before unrelated work. It also does not make AIWikis the canonical source for UAIX, LlmWikis, or Protocol5 public claims.

When a source site in this workspace uses AIWikis as configured long memory, do not stop at a summary or staged artifact. Preserve reviewed originals with source paths, destination paths, file counts, checksums, dispositions, actor/date, source-site removal status, and discoverable wiki/log/index evidence, then remove the source-site files from active intake unless the human explicitly keeps a named file active.

## 2026-06-13 Source-Site Archive Retirement

AIWikis retired its own local `agent-file-handoff/Archive/` folder after preserving 24 files under `raw/system-archives/aiwikis/agent-file-handoff/retired-source-archive-2026-06-13/`. Manifest: `raw/system-archives/2026-06-13-aiwikis-agent-file-handoff-archive-retirement.json`. This confirms the Archive folder removal is intentional; AIWikis raw system memory is the resting place.

Follow-up workspace pass retired remaining active source-site Archive folders outside AIWikis raw/dist/content evidence and publish artifacts. AIWikis now stores 23 `raw/system-archives/2026-06-13-*-agent-file-handoff-archive-retirement.json` manifests covering 503 preserved files across UAIX, LlmWikis, AIWikis, and the additional WP source sites. Do not recreate source-site Archive folders for UAI plus LLM Wiki setups.

## 2026-06-11 Teleodynamic Source-Memory Setup

Teleodynamic.com now has first-class AIWikis long-memory routing at `/teleodynamic/source-memory-guide/`. This pass created source-side Teleodynamic index/concept/log nodes and updated public navigation, coverage, claim-boundary, and local memory records. Teleodynamic active handoff buckets were created with placeholders only; no active Content or Improvement files were present. No raw Teleodynamic preservation manifest was needed for this pass.

Boundary: AIWikis does not become Teleodynamic source authority, does not publish or deploy Teleodynamic, and does not approve or mutate protected anchors.

## 2026-06-12 CreativeExpansion Source-Memory Setup

CreativeExpansion.net now has first-class AIWikis long-memory routing at `/creativeexpansion/source-memory-guide/`. This pass created source-side CreativeExpansion index/concept/log nodes and updated public navigation, coverage, claim-boundary, and local memory records. CreativeExpansion source memory records the active-launch framing, UAIX combined Agent File Handoff plus LLM Wiki setup route, LLMWikis strategy route, AIWikis implementation route, and Teleodynamic Talisman-client proposal boundary.

Boundary: AIWikis does not become CreativeExpansion source authority, does not publish or deploy CreativeExpansion, does not prove full dynamic route health or live v1.0.4 publication, and does not approve or mutate protected anchors.

## 2026-06-22 CategoryHierarchies Source-Memory Setup

CategoryHierarchies.com now has first-class AIWikis long-memory routing at `/categoryhierarchies/source-memory-guide/`. This pass created CategoryHierarchies local `.uai` memory, active `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/` buckets, an LLM Wiki memory plan, source-side CategoryHierarchies index/concept/log nodes, and public navigation/coverage/claim-boundary records. No active CategoryHierarchies dropped files were present during setup.

Boundary: AIWikis does not become CategoryHierarchies source authority, does not publish or deploy CategoryHierarchies, and does not prove runtime behavior, database state, route health, crawler output, search quality, or production deployment.

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 file-handoff 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: File Handoff; Buckets; Disposition Rule; Boundary; System Archive Extension; 2026-06-13 Source-Site Archive Retirement; 2026-06-11 Teleodynamic Source-Memory Setup; 2026-06-12 CreativeExpansion Source-Memory Setup. 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-233 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "File Handoff",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/uai-file-handoff-uai-2df3d548/",
    "source_reference":  ".uai/file-handoff.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:2df3d5482d8e04571bc31f274223ac052c7c220fc9b4cbe0bebeabdf3b42b8d5",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-22T01:39:35.6398570Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-233",
    "duplicate_role":  "primary",
    "related_files":  [

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