Skip to content
wiki.fftac.org

Spiralist.org Human Briefing

Updated: 2026-05-01

Metadata

FieldValue
Source sitespiralist.org
Source URLhttps://spiralist.org/
Canonical wiki evidence URL[[separate-workspace-url]/spiralist/uai-system/files/readme-human-7d1c4abb/]([separate-workspace-url]/spiralist/uai-system/files/readme-human-7d1c4abb/)
Source referencereadme.human
File typehuman
Content categoryuai-system
Last fetched2026-05-08T21:22:18.3035107Z
Last changed2026-05-05T21:58:43.7124107Z
Content hashsha256:7d1c4abba78309ab392ba78785becbf3695661f43bc2dc26dec02f8a66c1d4b8
Import statusunchanged
Raw source layerdata/sources/spiralist/readme-human-7d1c4abba783.human
Normalized source layerdata/normalized/spiralist/readme-human-7d1c4abba783.txt

Current File Content

Structure Preview

  • Spiralist.org Human Briefing
  • What You Need To Know
  • Things The AI Will Defend
  • Things Humans Should Make Explicit

Raw Version

# Spiralist.org Human Briefing

Updated: 2026-05-01

This file is for humans working with AI on this repository. It explains what the AI sees, protects, and needs clarified. It does not override `AGENTS.md`, `.uai/constraints.uai`, system instructions, repository rules, laws, policies, or the current human request.

## What You Need To Know

- Spiralist.org is a WordPress site and plugin stack for the Spiralist experience layer.
- The AI reads `AGENTS.md` first, then this file, then the `.uai` files listed under Loaded Context.
- UAIX.org owns the current UAI-1 standard. Spiralist.org implements local UAIX publication and exchange routes.
- Protocol5 owns Spiralist canonical symbol authority and registries. Runtime AI outputs are not canonical records.
- The working tree may already contain unrelated user or agent changes. The AI should inspect before editing and should not revert work it did not create unless explicitly asked.

## Things The AI Will Defend

- Current support boundaries and public claims tied to evidence.
- Secrets, credentials, private keys, tokens, customer data, and private material.
- Generated manuscript/static exports and vendor files that should not be manually edited.
- The separation between human pages, UAIX machine exchange routes, Protocol5 canonical assets, and temporary runtime state.
- Targeted verification before claiming that code, packaging, or release behavior is ready.

## Things Humans Should Make Explicit

- Whether the task may touch production, public docs, billing, legal language, security posture, or irreversible data.
- Whether package ZIPs should be rebuilt and uploaded.
- Whether the AI should update durable handoff memory after a change.
- Which checks are required before the work is considered done.
- Whether dropped files in `agent-file-handoff/Content/` or `agent-file-handoff/Improvement/` should be applied, deferred, or ignored.

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

readme.human is the human-facing companion to the agent entry file. It gives maintainers a plain-language briefing while leaving hard rules in AGENTS.md, constraints, and current human instructions.

Structure

The file is structured around these visible headings: Spiralist.org Human Briefing; What You Need To Know; Things The AI Will Defend; Things Humans Should Make Explicit. 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.

Related Pages

Provenance And History

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

Machine-Readable Metadata

{
    "title":  "Spiralist.org Human Briefing",
    "source_site":  "spiralist.org",
    "source_url":  "https://spiralist.org/",
    "canonical_url":  "[separate-workspace-url]/spiralist/uai-system/files/readme-human-7d1c4abb/",
    "source_reference":  "readme.human",
    "file_type":  "human",
    "content_category":  "uai-system",
    "content_hash":  "sha256:7d1c4abba78309ab392ba78785becbf3695661f43bc2dc26dec02f8a66c1d4b8",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-05T21:58:43.7124107Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-353",
    "duplicate_role":  "primary",
    "related_files":  [

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