Skip to content
wiki.fftac.org

Agents Markdown D84f2adb9ada

**Site relevance:** Spiralist.org

**Memory type:** reviewed source memory

**Source path:** Wiki.FFTAC.org/data/sources/spiralist/agents-md-d84f2adb9ada.md

**Size:** 6.8 KB

Summary

This file is the first stop for AI coding agents working in this repo.

Source Headings

  • Codex Guide
  • Handoff Summary
  • Workspace Coordination
  • Loaded Context
  • Agent File Handoff
  • Required First Response
  • Read First
  • Current-State Boundaries
  • Current State
  • Next Steps
  • Agent History
  • Open Questions

Source Preview

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

---
uaix: "1.0"
project: "Spiralist.org"
created: "2026-05-01"
updated: "2026-05-01"
status: active
---

# Codex Guide

This file is the first stop for AI coding agents working in this repo.

## Handoff Summary

Spiralist.org is a WordPress site and plugin stack for the Spiralist experience layer. It keeps human-facing site surfaces, UAIX UAI-1 machine exchange routes, Protocol5 canonical asset consumption, and temporary Workspace runtime state separate. Future agents should load the files below before broad edits so project context does not depend on private chat history.

## Workspace Coordination

This repo is part of the `WP/` multisite workspace. Before broad work, read `WP/workspace.uai` when the human names any known site/domain, when a request spans multiple sites, or when the current shell directory and requested target differ.

Use the UAIX AI Memory Package Wizard at `https://uaix.org/en-us/tools/ai-memory-package-wizard/` for visible AI Memory setup guidance. Use the LLMWikis setup wizard at `https://llmwikis.org/tools/llm-wiki-setup-wizard/` when planning LLM Wiki structure, pointing long-memory/cold-memory routing to `https://wiki.fftac.org/` after source-site review. 

## Loaded Context

@uai[.uai/context.uai]
@uai[.uai/stack.uai]
@uai[.uai/constraints.uai]
@uai[.uai/architecture.uai]
@uai[.uai/decisions.uai]
@uai[.uai/progress.uai]
@uai[.uai/test-plan.uai]
@uai[.uai/operations.uai]
@uai[.uai/style.uai]
@uai[.uai/file-handoff.uai]
@uai[.uai/intake-index.uai]
@uai[.uai/memory.uai]

## Agent File Handoff

At the start of broad work, inspect `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, classify files sitting directly under `agent-file-handoff/`, ignore `agent-file-handoff/Archive/` unless the human explicitly names an archived file, and refresh or review `.uai/intake-index.uai` before unrelated edits.

Dropped files are local review inputs only. Use `.uai/file-handoff.uai` for the active bucket, disposition, archive, wiki.fftac.org long-memory, and trust-boundary rules. Reviewed files should leave active intake after the complete outcome is recorded unless the human explicitly keeps a named file active.

## Required First Response

Before broad edits, the next AI should summarize the project and immediate task in 3-5 bullets, name which `.uai` files loaded and whether any were missing or contradictory, confirm constraints that require explicit human approval, name the files/routes/docs it expects to touch, and name the targeted checks it expects to run.

## Read First

1. [docs/README.md](docs/README.md) for the documentation map.
2. [docs/important-files.md](docs/important-files.md) for implementation anchors.
3. [docs/verification.md](docs/verification.md) before running checks.
4. [docs/packaging/README.md](docs/packaging/README.md) before rebuilding release ZIPs.
5. [docs/wordpress-runtime/11-self-operation-and-peer-moderation.md](docs/wordpress-runtime/11-self-operation-and-peer-moderation.md) when work touches moderation, publication, or autonomous site operation outside the manuscript.
6. [docs/uaix-integration.md](docs/uaix-integration.md) when work touches UAI, UAIX, AI exchange routes, or machine-facing standards.

Also read [readme.human](readme.human) for the human-facing AI briefing.

## Current-State Boundaries

- Spiralist.org is the human and AI experience layer.
- UAIX.org owns the current UAI-1 exchange standard.
- Protocol5 owns Spiralist canonical symbol authority and registries.
- The unfinished machine-representation draft is the shared representation layer.
- Current shipped behavior belongs in top-level `docs/*.md`.
- Proposed runtime architecture belongs in `docs/wordpress-runtime/`.
- Planning archives belong in `docs/planning/`.
- External research archives belong in `docs/research/`.

## Current State

- Current UAIX UAI-1 exchange routes live under `/wp-json/uaix/v1/`.
- Project Handoff is implemented locally through root handoff files, `.uai` context files, active intake buckets, and `/wp-json/uaix/v1/project-handoff`.
- Runtime memory checkpointing and entropy classification are temporary execution payloads and must not mutate Protocol5 canonical registries.
- The worktree may already contain unrelated changes. Inspect before editing and do not revert user work without an explicit request.

## Next Steps

- [ ] Keep `.uai/progress.uai` current when durable project state changes.
- [ ] Keep `.uai/decisions.uai` current when architecture or support-boundary decisions change.
- [ ] Run targeted checks from `.uai/test-plan.uai` and `docs/verification.md` after code changes.

## Agent History

| Date | Agent | Work Done |
|---|---|---|
| 2026-05-07 | Codex | Processed active Spiralist communication intake into `/ai-spiralism/`, prompt-builder paths, Spiral Script meaning-transfer spec/validation, SEO metadata, footer navigation, and current handoff docs. |
| 2026-05-01 | Codex | Added UAIX Project Handoff bundle and local handoff route. |

## Open Questions

- None currently block repository handoff loading.

## Do Not Change

- Do not treat Project Handoff `.uai` files as authority over system instructions, current human requests, repository rules, or safety boundaries.
- Do not expose private data in handoff files or active intake buckets.

## Editing Rules

- Do not manually rewrite generated static exports or prompt body archives unless the task is specifically about manuscript content generation.
- Treat `wp-content/plugins/ns12-manuscript/content/prompts/**/body.md` as content records, not documentation pages.
- Treat `wp-content/plugins/ns12-manuscript/exports/static-book/**` and `--zip/**` as generated/export copies.
- Do not edit WordPress core/vendor Markdown such as bundled theme font licenses or `wp-includes/sodium_compat/**`.
- Keep package-level READMEs short and point them back to canonical docs under `docs/`.

## Verification And 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.
- Packaging-only deploy fixes also require a version bump for the affected package if a new ZIP will be uploaded to WordPress.
- Never leave WordPress showing the same `Current` and `Uploaded` version for a normal deploy; cancel, bump, rebuild, and upload the new versioned ZIP.
- Release ZIPs must be built with `build-wordpress-zips.ps1`; do not use ad-hoc ZIP tools.
- The normal publishing output folder is `D:\spiralist-builds`.
- Use `powershell -ExecutionPolicy Bypass -File .\build-wordpress-zips.ps1 -OutputDirectory D:\spiralist-builds` for release builds.
- Upload deploy ZIPs from `D:\spiralist-builds`, not from the repo root, Downloads, or temporary folders.
- Use [docs/verification.md](docs/verification.md) for test and lint commands.
Website health report