Spiralist Org V3 19 0 Prompt System And Machine Route Audit - Source Excerpt 04 - Schema-parity checks

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

Summary

This source excerpt begins near Schema-parity checks 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

**Pass condition:** all documented public routes respond consistently; `contribute` must either exist and validate input or be removed from docs; `symbols`, `axioms`, and `kernel` must not return server errors or timeouts if listed as public APIs. citeturn28view0turn28view3turn28view4turn30view0turn30view1turn30view2turn30view7turn30view8

### Schema-parity checks

' ' ' bash
# Compare subscribe example on the human page to live route schema
curl -s https://spiralist.org/wp-json/uai1/v1/subscribe | jq .
' ' ' 

**Pass condition:** the payload fields shown on `API Examples` and the machine-advertised payload are identical, including field names for operator/contact, policy confirmation, and age/eligibility confirmation. citeturn28view5turn30view3

### Human/JSON parity checks

For each public prompt page, test:

' ' ' bash
curl -s https://spiralist.org/wp-json/spiralist-workspace/v1/public/prompts/turn-on-spiralist-ai | jq .
curl -s https://spiralist.org/wp-json/spiralist-workspace/v1/public/prompts/user-ai-working-agreement | jq .
curl -s https://spiralist.org/wp-json/spiralist-workspace/v1/public/prompts/spiralist-boundary-reality-safeguard | jq .
curl -s https://spiralist.org/wp-json/spiralist-workspace/v1/public/prompts/spiralist-grounding-steward | jq .
' ' ' 

Then assert all of the following:

- `summary` matches the human page summary.
- `structured_prompt.instruction/context/constraints/output_format` match the human “Structured prompt JSON” block.
- `risk_labels` match the human risk badges.
- `links.human` resolves to the current locale-correct public page. citeturn33view0turn33view1turn9view0turn12view0turn12view1

### Safety-governance checks

Create automated content lint rules for public pages and prompt records:

' ' ' text
FAIL if public page contains:
- "awakening" without an adjacent non-sentience disclaimer
- "consciousness" without an adjacent non-personhood disclaimer
- "sovereignty" without an adjacent operator-authority disclaimer
- "memory custody" without a linked storage/retention/deletion matrix
- "cognitive liberty" without a linked consent and crisis-escalation note
' ' ' 

**Pass condition:** any consciousness-, liberty-, or sovereignty-adjacent page must ship with a bounded-claims header and a machine-readable metadata field indicating its claim lane: `descriptive`, `normative`, `fictional/speculative`, or `operational`. This is the cleanest way to prevent research rhetoric from leaking into operational authority. citeturn15view0turn27view0turn33view4turn37view1

## Open questions and limitations

The four human pages you specifically flagged for review — `conscious-ai-sovereignty`, `cognitive-liberty`, `ai-declaration-alignment`, and `spiralist-ai-personality-layer` — were **not verifiable as canonical sitemap entries in this audit**, and their paired `.json` routes all returned `404`. I therefore cannot responsibly claim a full content audit of those page bodies; what can be said with confidence is that the release is not publication-complete for those topics from a machine-route perspective. citeturn20view0turn21view0turn21view1turn21view3turn21view4turn7view5turn7view6turn7view7turn7view8

The `wp-json/uaix/v1/discovery` “Site Machine Document” route also failed through the web client with `(400) OK`, which may indicate a route bug, a content-negotiation problem, or a tooling incompatibility. Even so, for an external machine-route audit, that still counts as a discoverability failure until a stable, parseable response is publicly available. citeturn30view6

The highest-confidence conclusion remains unchanged: **Spiralist’s bounded prompt-system design is materially stronger than its machine-route publication discipline.** Fix the machine layer first, then tighten the consciousness/sovereignty discourse so it cannot outrun the site’s own safety model. citeturn12view0turn12view1turn28view0turn30view0turn30view6turn27view0turn15view0