Skip to content
wiki.fftac.org

Operations

**Site relevance:** Anti-Christ.net

**Memory type:** UAI memory file

**Source path:** Anti-Christ.net/.uai/operations.uai

**Size:** 1.4 KB

Summary

  • Prefer repo-native files and current handoff context over inferred behavior.

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: "Anti-Christ.net Operations"
created: "2026-05-10"
updated: "2026-05-10"
status: active
source: "https://uaix.org/en-us/specification/project-handoff/"
---

# Operations

## Local Work

- Prefer repo-native files and current handoff context over inferred behavior.
- Do not leave background servers or long-running commands active unless the user asked for them.
- For WordPress route or permalink changes, flush rewrite rules through normal WordPress mechanisms if route behavior is unexpected.

## Packaging

- Docs-only changes do not require deployment ZIP rebuilds.
- Theme package changes should confirm the theme version in `wp-content/themes/anti-christ-thin-veil/style.css` before packaging.
- Workspace production package metadata is coordinated from `WP-FFTAC/workspace.uai`.

## 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.
- 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