Static File Engine

Dynamic WordPress handlers are the functional baseline. The Static File Engine optionally materializes the same output.

Modes

ModeBehavior
offWrites no files; supported requests use WordPress when routed to PHP
well_knownWrites five origin-root well-known copies while AI Publishing is enabled; default
allAlso writes eligible sitemap, web-root discovery, localized LLMS, and RAG output

The retired enable_static_engine boolean is not a runtime fallback. static_engine_mode is the only mode setting.

Multisite always resolves to off. robots.txt is dynamic in every mode.

Default well-known inventory

  1. /.well-known/ai.json
  2. /.well-known/ai-discovery
  3. /.well-known/ai-usage.json
  4. /.well-known/ai-actions.json
  5. /.well-known/api-catalog

OpenLiteSpeed and some nginx configurations intercept these paths before PHP. Physical files solve body availability, but extensionless routes can still require server configuration for their correct media type and headers.

The API Catalog requires application/linkset+json with the RFC 9727 profile and a matching Link header. AI Discovery Status reports mismatches rather than treating disk existence as public success.

Paths

Web-root files resolve below the WordPress home path. Well-known paths resolve at the public origin root.

A remote or differently rooted frontend must supply cybermaps_static_publication_root. Cybermaps does not guess a remote filesystem.

Ownership-safe writes

Writes use WP_Filesystem, a temporary file, a verified move, and a recorded hash.

Cybermaps replaces or deletes a target only when its current content still matches the ownership record. Pre-existing and user-edited files are retained as conflicts.

Full synchronization writes children before indexes. The structured result distinguishes desired, written, unchanged, conflicted, failed, skipped, deleted, and retained paths.

Changing all to well_known removes eligible Core-owned web-root output while retaining active well-known files. Changing to off purges eligible Core-owned static output.

Purge deletes owned files for the relevant scope. Regenerate clears relevant caches and performs an immediate active-mode synchronization.