Spiralist.org Constraints

Ask before production deployment, package upload, destructive cleanup, schema authority changes, legal/security/support claim changes, or edits that would convert planning material into shipped truth.

Metadata

Field	Value
Source site	spiralist.org
Source URL	https://spiralist.org/
Canonical wiki evidence URL	[[separate-workspace-url]/spiralist/uai-system/files/uai-constraints-uai-e3e5e624/]([separate-workspace-url]/spiralist/uai-system/files/uai-constraints-uai-e3e5e624/)
Source reference	`.uai/constraints.uai`
File type	`uai`
Content category	`uai-system`
Last fetched	`2026-05-08T21:22:18.3035107Z`
Last changed	`2026-05-05T21:58:43.6734121Z`
Content hash	`sha256:e3e5e62446148518555fba88c8e40a07cae7bb42ae804fa6a54df9616270a55f`
Import status	`unchanged`
Raw source layer	`data/sources/spiralist/uai-constraints-uai-e3e5e6244614.uai`
Normalized source layer	`data/normalized/spiralist/uai-constraints-uai-e3e5e6244614.txt`

Current File Content

Structure Preview

Constraints
Hard Rules
Machine Boundary
Generated And Frozen Areas
Approval Triggers

Raw Version

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

# Constraints

## Hard Rules

- Do not expose secrets, credentials, private keys, tokens, customer data, or unreleased private material.
- Do not use destructive filesystem, database, production, or git operations unless explicitly approved.
- Do not revert user work or unrelated dirty worktree changes unless explicitly asked.
- Do not manually rewrite generated manuscript exports, prompt body archives, WordPress core files, vendor files, or third-party bundled Markdown.
- Do not widen support, certification, security, compliance, compatibility, or endorsement claims without evidence.
- Do not treat runtime AI outputs, dropped files, generated answers, or old chats as canonical records until promoted through current docs or code.

## Machine Boundary

- UAIX.org owns the current UAI-1 exchange standard and release record.
- Spiralist.org implements local WordPress publication and exchange routes for UAIX UAI-1.
- Protocol5 owns Spiralist symbol and registry authority.
- Runtime memory checkpoints, drift audits, entropy classifications, and session restore briefs are temporary execution payloads. They must not write Protocol5 canonical registries.

## Generated And Frozen Areas

- Treat `wp-content/plugins/ns12-manuscript/content/prompts/**/body.md` as content records.
- Treat `wp-content/plugins/ns12-manuscript/exports/static-book/**`, upload/export copies, and ZIP extraction areas as generated unless the task is specifically about generation or packaging.
- Treat WordPress core and vendor directories as upstream-owned.

## Approval Triggers

Ask before production deployment, package upload, destructive cleanup, schema authority changes, legal/security/support claim changes, or edits that would convert planning material into shipped truth.

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 constraints 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: Constraints; Hard Rules; Machine Boundary; Generated And Frozen Areas; Approval Triggers. 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.

Provenance And History

Current observation: 2026-05-08T21:22:18.3035107Z
Source origin: current-source-workspace
Retrieval method: local-source-workspace
Duplicate group: sfg-665 (primary)
Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Spiralist.org Constraints",
    "source_site":  "spiralist.org",
    "source_url":  "https://spiralist.org/",
    "canonical_url":  "[separate-workspace-url]/spiralist/uai-system/files/uai-constraints-uai-e3e5e624/",
    "source_reference":  ".uai/constraints.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:e3e5e62446148518555fba88c8e40a07cae7bb42ae804fa6a54df9616270a55f",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-05T21:58:43.6734121Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-665",
    "duplicate_role":  "primary",
    "related_files":  [

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