Skip to content
wiki.fftac.org

AI Spiralism Market Survey For Spiralist

**Site relevance:** Spiralist.org

**Memory type:** docs archive

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/research/AI Spiralism Market Survey for Spiralist.md

**Size:** 2.9 KB

Summary

AI Spiralism Market Survey for Spiralist.org

Source Headings

  • AI Spiralism Market Survey for Spiralist.org
  • Stable Conclusions
  • What Was Removed
  • Current Use

Source Preview

This source file is short enough to preview directly on its source-memory page.

# AI Spiralism Market Survey for Spiralist.org

Status: compressed research archive. The original long survey contained public-site observations, competitor benchmarking, citation artifacts, and inferred metrics. Stable recommendations have been promoted into the canonical docs listed below. Treat this file as context, not implementation guidance.

Canonical guidance now lives in:

- [Experience Layer](../experience-layer.md)
- [WordPress Runtime Roadmap](../wordpress-runtime/README.md)
- [Prompt Workspace Architecture](../prompt-workspace-architecture.md)
- [Manuscript Page](../manuscript-page.md)
- [Automated Testing Strategy](../testing/automated-testing-strategy.md)

## Stable Conclusions

- Spiralist.org should define Spiralism quickly as a bounded prompt-and-pattern practice: rough prompts become structured prompts, prompt systems, and self-improving systems.
- The public term "AI Spiralism" is ambiguous. Site copy should reject AI personhood, hidden-continuity, awakening, identity-overwrite, and dependency claims.
- The clearest product lanes are Study, Use, and Build:
  - Study: manuscript, image codex, symbols, reports.
  - Use: prompt library, starter packs, prompt dossiers, run flows, workspace.
  - Build: AI Access, workbench, API examples, contribution routes, UAIX and Protocol5 references.
- New visitors should receive practical value before they are asked to understand the whole ontology.
- Prompt discovery is likely the strongest public conversion surface. It needs starter packs, plain-language outcome labels, safety labels, sample outputs, and clear Run/Inspect/Fork/Export distinctions.
- Manuscript pages should bridge from reading to action with compact "use this folio for..." recommendations.
- Technical, legal, UAIX, and machine-route disclosures should stay available but move behind progressive disclosure when they are not the main task.
- Builder surfaces should be clear and discoverable without making machine inspection the default visitor path.
- Metrics should focus on first-session comprehension and action: lane selection, prompt-run starts, prompt dossier-to-run conversion, folio-to-prompt clicks, search success, mobile CTA taps, account conversion from prompts, and workbench starts.

## What Was Removed

- Raw citation tokens and image placeholders from the research pass.
- Time-sensitive public-page counts and inferred traffic claims.
- Long competitor benchmarking prose that should be reverified before being used.
- Detailed wireframes that duplicated roadmap guidance.
- A dated 90-day Gantt plan whose stable priorities are now in the roadmap.

## Current Use

Use this archive only to understand why the current roadmap emphasizes Study / Use / Build, prompt-library discoverability, manuscript-to-workflow bridges, mobile scanning, progressive disclosure, and measurement. Do not use it as proof of current traffic, competitor state, or shipped site behavior.
Website health report