Workspace Current State

This page gives a compact public runtime state for the AIWikis package used by wiki.fftac.org.

Required Runtime State

Check	Required State
AIWikis Core health	The REST health endpoint returns HTTP 200.
Packaged Markdown	The health response confirms content pages are available.
Search index	The public search-index endpoint returns HTTP 200 with route records.
File-backed routes	Reviewed Markdown pages render as public routes, not hidden 404 responses.

The production package should expose both canonical AIWikis REST routes and the wiki.fftac.org compatibility route family used by deployment checks.

How To Read This Page

Use this page after a package upload or recovery deployment to decide whether the public site is serving the file-backed AIWikis content layer. A green homepage is not enough by itself. The package must also expose the Markdown-backed routes, the REST health payload, and the search index that AI agents and maintenance checks use to discover public memory safely.

The phrase "content pages are available" means the active plugin can see the packaged Markdown files under its data/pages/ directory and can count them through the health endpoint. If the count is zero, WordPress may still render a shell page, but the LLM Wiki memory layer is not actually available.

The HTTP 200 requirement matters because a hidden 404 can render a body that looks useful while still telling crawlers, monitors, and deployment checks that the route is missing. Public memory pages, source indexes, crawl maps, and transfer logs should return HTTP 200 when they are intentionally published.

Runtime Routes

Route	Expected Result
/wp-json/aiwikis/v1/health	HTTP 200 JSON with plugin health, active theme, content page counts, and public route inventory.
/wp-json/aiwikis/v1/search-index	HTTP 200 JSON with public route records for search and agent retrieval.
/wp-json/wiki-fftac/v1/search-index	HTTP 200 compatibility alias for wiki.fftac.org deployment checks.
/memory/sources/	HTTP 200 public memory-source index.
/memory/crawl-map/	HTTP 200 public crawl-map route.
/transfer-log/	HTTP 200 transfer evidence route.

Source Boundary

This page is deployment-readiness evidence, not proof that production was uploaded in the current work session. Source packages remain local until deliberately uploaded from the deployable UPLOAD-THEME, UPLOAD-PLUGIN, MU-PLUGIN-DEPLOY, WP-CONTENT-DEPLOY, or ROOT-FILES folders.

Failure Interpretation

If /wp-json/aiwikis/v1/health works but /wp-json/wiki-fftac/v1/search-index fails, the live plugin is missing the compatibility REST namespace expected by wiki.fftac.org checks. If /workspace-current-state/ renders but lacks this text, the public Markdown package is older than the current deployment contract. If the health endpoint reports too few content pages, rebuild the workspace package and upload the AIWikis Core plugin ZIP from UPLOAD-PLUGIN, not a legacy root ZIP.

Do not repair those failures by uploading raw archives, source-tree folders, or files from LEGACY-DO-NOT-UPLOAD. The correct path is to rebuild the package, run deployment readiness, run the SEO sweep, then upload only the approved deployment artifacts.