Skip to content
wiki.fftac.org

Spiralist.org Operations

Spiralist.org Operations is a uai-system source file exposed by the separate AI wiki workspace with provenance, current content, and generated explanation.

Metadata

FieldValue
Source sitespiralist.org
Source URLhttps://spiralist.org/
Canonical wiki evidence URL[[separate-workspace-url]/spiralist/uai-system/files/uai-operations-uai-94b0c166/]([separate-workspace-url]/spiralist/uai-system/files/uai-operations-uai-94b0c166/)
Source reference.uai/operations.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-08T21:22:18.3035107Z
Last changed2026-05-05T21:58:43.6754115Z
Content hashsha256:94b0c166821fd7581ca97faa5981a6bde23113e0bfc75e69b6f0621f1dba6809
Import statusunchanged
Raw source layerdata/sources/spiralist/uai-operations-uai-94b0c166821f.uai
Normalized source layerdata/normalized/spiralist/uai-operations-uai-94b0c166821f.txt

Current File Content

Structure Preview

  • Operations
  • Local Work
  • Packaging
  • Handoff Maintenance

Raw Version

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

---
uai: "1.0"
type: operations
title: "Spiralist.org Operations"
created: "2026-05-01"
updated: "2026-05-01"
status: active
source: "https://uaix.org/en-us/specification/project-handoff/"
---

# Operations

## Local Work

- Inspect `git status --short` before editing.
- Prefer repo-native helpers and current docs over inferred behavior.
- Do not leave background servers or long-running commands active unless the user asked for them.
- For WordPress route changes, flush rewrite rules through normal WordPress mechanisms if route behavior is unexpected.

## Packaging

- Docs-only changes do not require deployment ZIP rebuilds.
- Theme or plugin package changes require the relevant version header to be bumped before packaging.
- UAI-system publishing requires `npm.cmd run check:uai-prepublish` before build or upload when changes touch UAI, UAIX, Project Handoff, AI memory, machine schemas, discovery, capability statements, validators, or local UAI implementation docs.
- Release ZIPs must be built with `build-wordpress-zips.ps1`.
- Upload deploy ZIPs from `[local path redacted]`, not repo root or temporary folders.

## Handoff Maintenance

- Update `.uai/progress.uai` when work changes durable current state.
- Update `.uai/decisions.uai` for durable architecture or support-boundary decisions.
- Update `.uai/constraints.uai` only when a rule changes, not for one-off task preferences.
- Use `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/` for active dropped files that need review during the next handoff load.

Why This File Exists

This is a UAI AI Memory handoff file from spiralist.org. It is shown here because the separate AI wiki workspace 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 operations 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: Operations; Local Work; Packaging; Handoff Maintenance. 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 wiki.fftac.org 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-431 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Spiralist.org Operations",
    "source_site":  "spiralist.org",
    "source_url":  "https://spiralist.org/",
    "canonical_url":  "[separate-workspace-url]/spiralist/uai-system/files/uai-operations-uai-94b0c166/",
    "source_reference":  ".uai/operations.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:94b0c166821fd7581ca97faa5981a6bde23113e0bfc75e69b6f0621f1dba6809",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-05T21:58:43.6754115Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-431",
    "duplicate_role":  "primary",
    "related_files":  [

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