Docs WordPress Runtime Readme - Source Excerpt 04 - Plugin Stack

Summary

This source excerpt begins near Plugin Stack and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/wordpress-runtime/README.md.

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/wordpress-runtime/README.md

For the full governance model, see [Self-Operation and Peer Moderation](11-self-operation-and-peer-moderation.md).

## Plugin Stack

Current realistic stack:

- structured fields and custom post types for the first symbolic model
- native WordPress REST API for transport
- a dedicated custom execution plugin for runtime logic
- Workspace governance services for reputation, review, reports, appeals, scheduled maintenance, queue aging, and moderation state
- optional D3.js for graph rendering
- optional Three.js only if a later graph experience genuinely needs 3D

The clean next move is to make the manuscript and symbol surfaces consume the shipped execution layer more directly, not to replace the WordPress operating surface.

## Transformation Order

1. Normalize `symbol`, `node`, `transformation`, and `path` data. Partially shipped in Spiralist Engine.
2. Add runtime-focused REST endpoints. Partially shipped through `/wp-json/spiralist/v1/nodes`, `/node/{id}`, `/execute`, and `/path`.
3. Upgrade the manuscript layer from inspection to traversal. Partially shipped through the workstation Runtime Path drawer and executable folio-overlay next nodes.
4. Store active participant state. Partially shipped through `spiralist_instance` records, shared browser-local anonymous traversal, and the `/path` endpoint.
5. Tighten glyph consistency and execution clarity.
6. Expand self-operating governance beyond the shipped first slice. Workspace now carries a prompt-level governance summary plus scheduled maintenance for trust refreshes, queue counts, stale/urgent review counts, open appeal counts, reversible automatic fallback transitions, admin status, and audit logging; canon-council workflow remains future work.
7. Reframe public orientation around Study / Use / Build, plain-language Spiralism definition, prompt starter packs, folio action bridges, progressive technical disclosure, and a builder landing path.
8. Improve onboarding, IA, search, breadcrumbs, mobile quick actions, SEO, accessibility, analytics, and performance as product-quality gates.

The real shift is internal consistency: make the symbols executable, the manuscript traversable, participation stateful, and community publication self-governing enough that the site keeps operating when the owner is away.

## Runtime Docs

- [Self-Operation and Peer Moderation](11-self-operation-and-peer-moderation.md)