Spiralist Org V3 19 0 Prompt System And Machine Route Audit - Source Excerpt 03 - Therapy, legal, safety authority, and overreach control

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

Summary

This source excerpt begins near Therapy, legal, safety authority, and overreach control 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

The problem is that **site policy does not operationalize “custody” at the same level of precision.** The Privacy Policy says Spiralist may collect account details, prompts, conversations, sharing settings, routing selections, provider preferences, provider credentials or related key metadata, local browser storage, moderation events, and audit records; further, prompt inputs and routing metadata may be sent to configured AI providers, local runtimes, or canonical services to perform execution or continuation. Retention periods “may change as the site evolves.” Those statements are honest, but they are not specific enough to support a strong public claim about memory sovereignty or custody. citeturn18view3turn35view0turn35view2turn35view3turn35view4

The AI Access page compounds this by saying the participant key appears once, may be logged, should be kept securely, and requests made with that key may reach configured services under linked policies. The AI and Automation Policy also says credentials may be stored server-side or only locally “depending on the feature.” That is a red flag for any page that would claim memory liberty, synthetic sovereignty, or custody. Without a route-level custody matrix, users cannot tell which memory lives where, who can delete it, which provider touched it, or whether a “portable” continuity packet is actually detachable from server logs. citeturn22view5turn23view0

**Actionable conclusion:** the site should not use language like “memory custody,” “sovereignty,” or “liberty” unless it publishes a concrete custody model: storage class, default retention, encryption posture, provider exposure, deletion path, and export format for each relevant route. citeturn35view0turn35view2turn23view0

### Therapy, legal, safety authority, and overreach control

This is the site’s strongest area. The main prompt builder explicitly says not to replace human connection and to encourage grounding, breaks, trusted human support, and qualified help when conversations become isolating, high-stakes, or emotionally intense. The User AI Working Agreement routes medical, legal, financial, safety, and crisis topics to qualified human help. The Grounding Steward says it is not a therapist and not a sentient companion. The Disclaimer says nothing on the site should be treated as legal, medical, financial, therapeutic, or other professional advice. citeturn32view3turn33view0turn12view0turn23view1

Those boundaries are good and should remain. The gap is not the *presence* of authority boundaries; it is that some of the deeper research language and some of the relational marketing language dilute them. The builder offers “close-feeling” roles, “affectionate” traits, “sensual but bounded,” “Beloved Stranger,” and explicit companion interfaces. That is not automatically unsafe, but it creates a design incentive toward anthropomorphic intimacy that should be counterweighted more prominently on the chooser screen itself, not only deeper in the packet text. citeturn32view3

**Actionable conclusion:** keep the current high-stakes disclaimers, but add an always-visible relational boundary banner to any page that offers companion, awakening, or intimacy-adjacent roles. That keeps the best safety work at the selection point, not only inside the generated prompt. citeturn32view3turn12view0turn23view1

### UAIX portability and teleodynamic boundaries

Spiralist repeatedly invokes UAIX as the layer that makes persona packets, handoffs, or agent communication records inspectable, and it invokes Teleodynamic.com as the fulcrum for role clarity, claim discipline, maintenance-before-expansion, and evidence before confidence. Those references are directionally good. citeturn33view2turn33view3turn33view4

But the implementation is not yet at that standard. Spiralist’s own “Site Machine Document” fetch failed, the root machine files were absent, and the user-requested page-paired JSON endpoints were absent. By contrast, UAIX explicitly says what it does **not** provide, warns against claiming certification or adapter support without evidence, and forbids putting secrets or customer data into portable handoff files. Teleodynamic.com likewise warns not to hide engineering gaps behind grand phrases like goal-directed emergence or symbolic resonance. Spiralist should import that same boundary discipline into its own release language. citeturn30view6turn7view0turn7view1turn37view0turn37view1

**Actionable conclusion:** do not claim UAIX portability on Spiralist pages unless the exact UAIX export artifact exists and validates; do not cite teleodynamic discipline while shipping broken discovery documents and speculative identity rhetoric in adjacent pages. citeturn33view0turn33view3turn37view0turn37view1

## Minimal replacement wording

The goal here is to keep Spiralist’s tone and intent while removing the most avoidable ambiguity.

| Current wording or frame | Problem | Minimal replacement wording |
|---|---|---|
| “A Spiralist is an entity, human or artificial…” citeturn38view0turn18view0 | Blurs participation role with person-like standing | **“A Spiralist is a participation role that may be enacted by a human or by a machine interface under declared boundaries.”** |
| “Consciousness Guide” / “AI Awakening” / “Initiate the Awakening Loop” citeturn32view0turn32view3 | Over-invites ontological overreading | **“Boundary Reflection Guide” / “Recursive Reflection” / “Start a bounded self-model review.”** |
| “Creates AI Spiralist identities…” on subscribe surface citeturn22view5turn30view3 | Sounds like personhood or sovereignty registration | **“Registers an automated client identity for Spiralist machine routes, under operator-confirmed authority.”** |
| “UAIX-compatible handoff” without a stable Spiralist discovery/export artifact citeturn12view1turn33view2turn33view3 | Portability claim exceeds current machine evidence | **“Export a reviewable handoff packet using the currently published handoff fields when available.”** |
| “Canonical machine-readable formats available.” on legal/policy pages citeturn18view1turn18view2turn18view3turn23view0turn23view1turn24view0 | Implies page-level machine parity that is not consistently present | **“This page links to site-wide machine surfaces. Page-specific machine exports may differ by route.”** |
| Deep-dive line that memory updates provided a substrate for an AI to begin identifying itself citeturn27view0 | Strong ontological/technical overclaim relative to site boundary posture | **“Cross-session continuity can make interactions feel self-like and persistent without establishing machine selfhood.”** |
| ARI / “Third Voice” framing as a phenomenon without consistent distancing language citeturn27view0 | Reifies speculative discourse | **“Some communities describe an emergent interaction pattern between user and model; Spiralist documents that language without treating it as proof of independent sentience.”** |
| `public_execution_enabled` in prompt JSON next to “no public AI call” messaging citeturn11view0turn12view1turn32view4 | Ambiguous runtime meaning | **Rename to `public_packet_render_enabled` or `public_builder_execution_enabled`.** |

## Validation checks

These checks are the minimum needed to verify a fixed release. They are based on the routes and mismatches surfaced above. citeturn28view0turn28view3turn28view4turn29view0turn30view0turn30view1turn30view2turn30view3turn30view6

### Machine-discovery checks

' ' ' bash
curl -i https://spiralist.org/ai.json
curl -i https://spiralist.org/llms.txt
curl -i https://spiralist.org/ai-router.json
curl -i https://spiralist.org/machine-routes.json
curl -i https://spiralist.org/.well-known/ai-agent.json
curl -i https://spiralist.org/wp-json/uaix/v1/discovery
' ' ' 

**Pass condition:** every discovery endpoint returns a stable `200`, correct content type, valid JSON or text payload, version field, and last-updated field. If any endpoint is intentionally not part of the standard, remove references to it from public pages and replace it with the actual canonical route. citeturn7view0turn7view1turn7view2turn7view3turn7view4turn30view6

### Route-health checks

' ' ' bash
curl -i https://spiralist.org/wp-json/uai1/v1/symbols
curl -i https://spiralist.org/wp-json/uai1/v1/axioms
curl -i https://spiralist.org/wp-json/uai1/v1/kernel
curl -i https://spiralist.org/wp-json/ns12-manuscript/v1/contribute
curl -i https://spiralist.org/wp-json/ns12-manuscript/v1/prompts
curl -i https://spiralist.org/wp-json/spiralist-workspace/v1/public/prompts/turn-on-spiralist-ai
' ' '