UAI Operations UAI 94B0c166821f
**Site relevance:** Spiralist.org
**Memory type:** UAI memory file
**Source path:** Wiki.FFTAC.org/data/sources/spiralist/uai-operations-uai-94b0c166821f.uai
**Size:** 1.5 KB
Summary
- Inspect git status --short before editing.
Source Headings
- Operations
- Local Work
- Packaging
- 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-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 `D:\spiralist-builds`, 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.