Workspace Current State
Runtime readiness page for the wiki.fftac.org AIWikis package, content-page availability, and HTTP route expectations.
Metadata
| Field | Value |
|---|---|
| Source site | aiwikis.org |
| Source URL | https://aiwikis.org/ |
| Canonical AIWikis URL | https://aiwikis.org/aiwikis/files/content-pages-973-workspace-current-state-md-955f0b1a/ |
| Source reference | content/pages/973-workspace-current-state.md |
| File type | md |
| Content category | public-content |
| Last fetched | 2026-06-22T01:56:21.9510185Z |
| Last changed | 2026-05-25T08:09:02.1622344Z |
| Content hash | sha256:955f0b1ab289853068b52920bb054b60c2db8eca78e1e0d7cae9bae86377a04b |
| Import status | unchanged |
| Raw source layer | data/sources/aiwikis/content-pages-973-workspace-current-state-md-955f0b1ab289.md |
| Normalized source layer | data/normalized/aiwikis/content-pages-973-workspace-current-state-md-955f0b1ab289.txt |
Current File Content
Structure Preview
- Workspace Current State
- Required Runtime State
- How To Read This Page
- Runtime Routes
- Source Boundary
- Failure Interpretation
Raw Version
---
title: "Workspace Current State"
description: "Runtime readiness page for the wiki.fftac.org AIWikis package, content-page availability, and HTTP route expectations."
seo_title: "Workspace Current State"
meta_description: "Runtime readiness status for wiki.fftac.org, including AIWikis Core content-page availability, search-index route expectations, and HTTP 200 checks."
slug: "org/workspace-current-state"
route_aliases:
- "workspace-current-state"
status: "Reviewed"
trust_level: "reviewed"
source_status: "deployment checklist runtime state page"
content_type: "reference"
page_type: "reference"
primary_category: "operations"
schema_type: "TechArticle"
canonical_url: "https://aiwikis.org/org/workspace-current-state/"
canonical: "https://aiwikis.org/org/workspace-current-state/"
noindex: false
sitemap_include: true
tags:
- "deployment"
- "runtime-state"
- "wiki-fftac"
- "content-pages"
owner: "AIWikis maintainers"
last_reviewed: "2026-05-15"
typed_relations:
part_of:
- "/source-map/"
depends_on:
- "/wp-json/aiwikis/v1/health"
- "/wp-json/aiwikis/v1/search-index"
supersedes: []
contradicts: []
source_for: []
---
# 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.
Why This File Exists
This is a public content source file from aiwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.
Role
This file is a focused source unit. Its path, headings, and metadata give an agent a retrieval handle that is smaller than loading the entire site or repository.
Structure
The file is structured around these visible headings: Workspace Current State; Required Runtime State; How To Read This Page; Runtime Routes; Source Boundary; Failure Interpretation. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.
Prompt-Size And Retrieval Benefit
Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.
How To Use It
- Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
- LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
- Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
- Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.
Update Requirements
When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.
Related Pages
- Source overview
- Site file index
- Site report index
- UAI system index
- Source provenance
- Site directory
- Organization reports
Provenance And History
- Current observation:
2026-06-22T01:56:21.9510185Z - Source origin:
current-source-workspace - Retrieval method:
local-source-workspace - Duplicate group:
sfg-714(primary) - Historical hash records are stored in
data/hashes/source-file-history.jsonl.
Machine-Readable Metadata
{
"title": "Workspace Current State",
"source_site": "aiwikis.org",
"source_url": "https://aiwikis.org/",
"canonical_url": "https://aiwikis.org/aiwikis/files/content-pages-973-workspace-current-state-md-955f0b1a/",
"source_reference": "content/pages/973-workspace-current-state.md",
"file_type": "md",
"content_category": "public-content",
"content_hash": "sha256:955f0b1ab289853068b52920bb054b60c2db8eca78e1e0d7cae9bae86377a04b",
"last_fetched": "2026-06-22T01:56:21.9510185Z",
"last_changed": "2026-05-25T08:09:02.1622344Z",
"import_status": "unchanged",
"duplicate_group_id": "sfg-714",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-06-22T01:56:21.9510185Z"
} Next Useful Routes
- Start Here A task-first reading path for AIWikis.org, separating newcomer learning, source-memory lookup, maintainer workflow, and AI-agent retrieval.
- Topic Index A tag-oriented index for LLM Wiki, AI memory, UAI, source governance, crawling, and retrieval topics.
- Source Map AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
- AIWikis.org AIWikis.org source-system overview for transparent AIWikis memory demonstration.
- AIWikis.org Files Site-scoped current-source file index for AIWikis.org.
- AIWikis.org UAI System Files Real current AIWikis file-backed content, source-side wiki, raw archive, graph, handoff, and public-route evidence files.