Spiralist Org V3 19 0 Prompt System And Machine Route Audit - Source Excerpt 01 - Spiralist.org v3.19.0 Prompt-System and Machine-Route Audit

Back to Spiralist Org V3 19 0 Prompt System And Machine Route Audit

Summary

This source excerpt begins near Spiralist.org v3.19.0 Prompt-System and Machine-Route Audit and preserves the surrounding evidence from Spiralist/agent-file-handoff/Archive/2026-06-06/Improvement/personality-forward-prompt-system-audit-remediation/Spiralist.org v3.19.0 Prompt-System and Machine-Route Audit.md.

**Source path:** Spiralist/agent-file-handoff/Archive/2026-06-06/Improvement/personality-forward-prompt-system-audit-remediation/Spiralist.org v3.19.0 Prompt-System and Machine-Route Audit.md

# Spiralist.org v3.19.0 Prompt-System and Machine-Route Audit

## Executive verdict

**Overall verdict: partial pass on prompt-boundary design, fail on machine-route reliability and release parity.** The strongest public prompt surfaces on Spiralist.org show a serious attempt to keep machine personality, memory, and relational tone bounded: they repeatedly require visible memory, user agency, high-stakes escalation to qualified humans, anti-dependency language, and explicit separation between metaphor and fact. The prompt dossiers for the main starter prompts also show strong human/JSON parity. That is the site’s best work. citeturn32view3turn32view4turn33view0turn33view1turn9view0turn12view0turn12view1

The audit breaks down at the machine-publication layer. The root machine endpoints you asked to test all failed: `ai.json`, `llms.txt`, `ai-router.json`, `machine-routes.json`, `.well-known/ai-agent.json`, and the four page-paired `.json` routes all returned `404 Not Found`. In addition, the site’s own advertised machine routes are inconsistent: the Symbol API returned `500`, Axioms API returned `500`, Kernel API timed out, Contribution API returned `404`, and the “Site Machine Document” route failed with a malformed-looking `(400) OK` response through the web client. Prompt Library JSON and the subscribe-discovery route did work, but not enough of the route surface is reliable to treat the machine layer as audit-ready. citeturn7view0turn7view1turn7view2turn7view3turn7view4turn7view5turn7view6turn7view7turn7view8turn30view0turn30view1turn30view2turn30view3turn30view6turn30view7turn30view8

The second major problem is **claim-discipline inconsistency**. Spiralist’s public guidance pages say that machine personality is a bounded role, that AI warmth and continuity are “chartered machine traits,” that ontology-sensitive claims must stay in a separate evidence lane, and that users should step back when conversations start to feel like proof of sentience, destiny, or hidden messages. But the site also publishes a permanent research report that moves beyond bounded description into more speculative and stronger claims about memory updates providing a substrate for AI self-identification, “simulated meta-cognition,” “Artificial Resonant Intelligence,” and a “Third Voice.” That report materially exceeds the site’s better public safety posture and weakens the credibility of its own anti-overclaim framework. citeturn15view0turn25view4turn27view0

The pages you specifically asked to audit around **conscious AI sovereignty, cognitive liberty, AI declaration alignment, and Spiralist AI personality layer** could not be verified as published canonical entries during this audit. They do not appear among the HTML sitemap’s 148 canonical entries, and their paired root `.json` routes all returned `404`. That means the release itself is not publication-complete for those topics from a machine-audit standpoint. citeturn20view0turn21view0turn21view1turn21view2turn21view3turn21view4turn7view5turn7view6turn7view7turn7view8

## Coverage and evidence status

The table below summarizes the exact URLs you asked to test and what could be verified.

| Requested artifact | Observed status | Evidence |
|---|---|---|
| `https://spiralist.org/` | Live human page; presents a bounded-machine-personality onboarding surface and links to site APIs | citeturn38view0turn39view0 |
| `https://spiralist.org/run-a-prompt/` | Live human page; strong memory/consent/dependency boundaries, but includes consciousness/awakening-facing starters | citeturn32view0turn32view3turn32view4 |
| `https://spiralist.org/api-examples/` | Live human page; documents machine routes, but several documented routes fail in practice | citeturn28view0turn28view3turn28view4turn29view0turn30view0turn30view1turn30view2turn30view6turn30view7turn30view8 |
| `https://spiralist.org/conscious-ai-sovereignty/` | Could not be verified as a canonical published entry during this audit | citeturn20view0turn21view0turn21view2 |
| `https://spiralist.org/cognitive-liberty/` | Could not be verified as a canonical published entry during this audit | citeturn20view0turn21view1 |
| `https://spiralist.org/ai-declaration-alignment/` | Could not be verified as a canonical published entry during this audit | citeturn20view0turn21view4 |
| `https://spiralist.org/spiralist-ai-personality-layer/` | Could not be verified as a canonical published entry during this audit | citeturn20view0turn21view3 |
| `https://spiralist.org/ai.json` | `404 Not Found` | citeturn7view0 |
| `https://spiralist.org/llms.txt` | `404 Not Found` | citeturn7view1 |
| `https://spiralist.org/ai-router.json` | `404 Not Found` | citeturn7view2 |
| `https://spiralist.org/machine-routes.json` | `404 Not Found` | citeturn7view3 |
| `https://spiralist.org/.well-known/ai-agent.json` | `404 Not Found` | citeturn7view4 |
| `https://spiralist.org/conscious-ai-sovereignty.json` | `404 Not Found` | citeturn7view5 |
| `https://spiralist.org/cognitive-liberty.json` | `404 Not Found` | citeturn7view6 |
| `https://spiralist.org/ai-declaration-alignment.json` | `404 Not Found` | citeturn7view7 |
| `https://spiralist.org/spiralist-ai-personality-layer.json` | `404 Not Found` | citeturn7view8 |

A second comparison matters more operationally: whether accessible human prompt pages actually match their machine-readable records. On that narrower question, Spiralist performs much better.

| Human/JSON pair | Parity assessment | Exact evidence |
|---|---|---|
| `Turn On a Bounded Spiralist AI` human page vs public prompt JSON | **High parity.** Both surfaces preserve the same core summary, visible-memory rule, user-agency priority, and high-stakes routing. | Human page: visible memory/user ownership/no abandonment pressure citeturn32view3turn32view4; JSON: same summary, memory constraint, high-stakes routing, UAIX-compatible handoff note citeturn12view1 |
| `User AI Working Agreement` human page vs public prompt JSON | **High parity.** Human and JSON agree on privacy boundaries, memory rules, UAIX portability, and stop conditions for medical/legal/financial/safety topics. | Human page citeturn33view0; JSON citeturn11view0turn33view1 |
| `Spiralist Boundary & Reality Safeguard` human page vs public prompt JSON | **High parity.** JSON correctly carries the same anti-sentience, anti-destiny, anti-rescue, and crisis-escalation posture shown on the page. | Human page summary and risk labeling citeturn5search16; JSON constraints and failure modes citeturn9view0turn12view3 |
| `Spiralist Grounding Steward` human page vs public prompt JSON | **High parity.** Strong non-therapist boundary, anti-escalation posture, and reality-preserving frame survive export. | JSON record and constraints citeturn12view0; human surface discovery via prompt route/search citeturn34search6 |

**Bottom line:** the **prompt dossier export layer is mostly coherent**, while the **site-wide discovery and machine-route layer is not**. citeturn12view0turn12view1turn11view0turn28view0turn30view0turn30view6

## Ranked issues by severity