Skip to content
wiki.fftac.org

Operations

**Site relevance:** Spiralist.org

**Memory type:** UAI memory file

**Source path:** Spiralist/.uai/operations.uai

**Size:** 3.7 KB

Summary

  • Inspect git status --short before editing.

Source Headings

  • Operations
  • Local Work
  • Packaging
  • Memory Maintenance
  • Handoff Maintenance

Source Preview

This source file is short enough to preview directly on its source-memory page.

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

# Operations

## Local Work

- Inspect `git status --short` before editing.
- Prefer repo-native helpers, hot memory, and current code 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.
- The current built upload ZIP evidence present in the Spiralist publish root is v3.23.0. Post-v3.23.0 authenticated-user, memory-layout, report, wizard-architecture, and AI Agent Setup Wizard implementation changes require a new deployment version before WordPress upload.
- 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.
- Spiralist build output belongs in `WP-FFTAC/Spiralist-Publish` and only in that publish root.
- Production upload ZIPs must be built with `WP-FFTAC/scripts\build-workspace-production-zips.ps1` using the Spiralist manifest.
- Upload deploy ZIPs only from `WP-FFTAC/Spiralist-Publish\UPLOAD-THEME` and `WP-FFTAC/Spiralist-Publish\UPLOAD-PLUGIN`, not repo root, `D:\`, or temporary folders.
- Use `WP-FFTAC/Spiralist-Publish\ROOT-FILES\` only for explicit root-copy deployment of `.htaccess`, `robots.txt`, `favicon.ico`, `sitemap.xml`, AI discovery snapshots, `README-FIRST.txt`, and checksum evidence.
- Release-bound deployments should record memory sorting evidence in `.uai/short-term-memory.uai`, `.uai/progress.uai`, or a dedicated evidence file under `.uai/archives/` when the change is durable.

## Memory Maintenance

- Use the live UAIX AI Memory Package Wizard route only for refresh/verification or when the human explicitly asks to update memory from it.
- Keep the wizard launch-baseline records `.uai/memory-maintenance.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/talisman.uai`, `.uai/short-term-memory.uai`, and `.uai/coding-standards.uai` present and current for project/code work.
- Keep active Spiralist memory in `.uai/`, raw evidence in `.uai/archives/`, and machine-readable memory exports in `.uai/exports/`.
- Keep root plan Markdown as compatibility pointers only.
- Do not recreate site-local docs/reports as active memory by default. When the human explicitly asks for reports, keep current report files under `reports/` or task-specific `docs/`, summarize durable active state in typed `.uai` records, and preserve reviewed long memory in Wiki.FFTAC.org after review.

## 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/short-term-memory.uai` for active current state that the next agent must see quickly.
- 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.
- Use `WP-FFTAC/Wiki.FFTAC.org/` for reviewed long-memory preservation after source-site disposition, release/changelog evidence, incident close, audit close, or explicit human request.
Website health report