Skip to content
aiWikis.org

Spiralist.org Active File Handoff

On AGENTS.md load, check active buckets before broad work. Classify files sitting directly under agent-file-handoff/ into Content/ or Improvement/ before disposition. Disposition each active file as apply now, c...

Metadata

FieldValue
Source sitespiralist.org
Source URLhttps://spiralist.org/
Canonical AIWikis URLhttps://aiwikis.org/spiralist/uai-system/files/uai-file-handoff-uai-ae797a11/
Source reference.uai/file-handoff.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-08T21:22:18.3035107Z
Last changed2026-05-08T21:18:50.8356221Z
Content hashsha256:ae797a116b3662b2f2c84da61cc3fbccdb8aa0abb74386d3f5474b51b7ca7280
Import statusunchanged
Raw source layerdata/sources/spiralist/uai-file-handoff-uai-ae797a116b36.uai
Normalized source layerdata/normalized/spiralist/uai-file-handoff-uai-ae797a116b36.txt

Current File Content

Structure Preview

  • File Handoff
  • Active Buckets
  • Intake Rule
  • Complete Outcome Rule
  • Boundary

Raw Version

---
uai: "1.0"
type: file-handoff
title: "Spiralist.org Active File Handoff"
created: "2026-05-01"
updated: "2026-05-08"
status: active
source: "https://uaix.org/en-us/specification/project-handoff/"
---

# File Handoff

## Active Buckets

- `agent-file-handoff/Content/`: candidate content, source material, or documents that may affect site content.
- `agent-file-handoff/Improvement/`: improvement requests, bug notes, screenshots, exported chats, or implementation hints.
- `agent-file-handoff/Archive/`: processed files moved out of active intake.

## Intake Rule

On AGENTS.md load, check active buckets before broad work. Classify files sitting directly under `agent-file-handoff/` into `Content/` or `Improvement/` before disposition. Disposition each active file as apply now, convert into roadmap/progress state, archive as duplicate, defer with a reason, ask for clarification, or block as unsafe/out of scope.

## Complete Outcome Rule

Because this workspace routes reviewed long memory to AIWikis.org, a processed active file is complete only after durable state records:

- reviewed summary, risk, current-task relationship, and disposition;
- actual site or system work, or durable no-change/defer/duplicate/clarification/blocker reason;
- hot-memory update or explicit no-change reason;
- AIWikis long-memory/archive preservation with source path, destination path, file count, checksum, disposition, actor/date, and discoverable evidence when configured;
- targeted checks run or skipped with reason;
- Archive destination.

Move processed source files to `agent-file-handoff/Archive/` after the complete outcome unless the human explicitly keeps a named file active. Memory routing alone is not completion, and reviewed files must not remain in `Content/` or `Improvement/` merely because they were summarized or copied.

## Boundary

Dropped files are local project-state inputs only. Public content, production writes, support claims, and release claims still need normal review and targeted verification.

Why This File Exists

This is a UAI AI Memory handoff file from spiralist.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; Active Buckets; Intake Rule; Complete Outcome Rule; Boundary. 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-08T21:22:18.3035107Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-517 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Spiralist.org Active File Handoff",
    "source_site":  "spiralist.org",
    "source_url":  "https://spiralist.org/",
    "canonical_url":  "https://aiwikis.org/spiralist/uai-system/files/uai-file-handoff-uai-ae797a11/",
    "source_reference":  ".uai/file-handoff.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:ae797a116b3662b2f2c84da61cc3fbccdb8aa0abb74386d3f5474b51b7ca7280",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-08T21:18:50.8356221Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-517",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-08T21:22:18.3035107Z"
}