LLMWikis Operations

1. Read AGENTS.md first. 2. Read root readme.human as the human briefing companion; do not treat it as an override. 3. Perform chat-start file intake from Content/ and Improvement/, avoid source-site `Archive/...

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/uai-operations-uai-6b8eb4f6/
Source reference	.uai/operations.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-13T22:17:44.2793109Z
Content hash	sha256:6b8eb4f61c20e6d5c93b093e0cfb5f64a30e30dbcd910ff94434213ffe08acdd
Import status	unchanged
Raw source layer	data/sources/llmwikis/uai-operations-uai-6b8eb4f61c20.uai
Normalized source layer	data/normalized/llmwikis/uai-operations-uai-6b8eb4f61c20.txt

Current File Content

Structure Preview

• LlmWikis Operations
• Common Commands
• Common Checks
• Editing Workflow
• Release Expectations
• Recovery Notes

Raw Version

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

---
uaix: "1.0"
type: custom
title: "LlmWikis Operations"
created: "2026-04-26"
updated: "2026-06-13"
author: "LlmWikis maintainers"
version: 18
---

# LlmWikis Operations

## Common Commands

- `studio site status`
- `studio site start --skip-browser`
- `studio wp option get siteurl`
- `studio wp theme list --fields=name,status,version`
- `studio wp plugin list --fields=name,status,version`
- `studio wp theme activate llmwikis-knowledge-theme`
- `studio wp plugin activate llmwikis-core`
- `studio wp plugin activate uai1-project-handoff`
- `studio wp rewrite flush`
- `powershell -NoProfile -ExecutionPolicy Bypass -File scripts/Invoke-UaiFileIntake.ps1`
- If `.uai/intake-index.uai` lists any `needs-agent-review` file from `Content/`, `Improvement/`, or legacy `intake/`, inspect it, summarize it, and state a disposition before unrelated broad work continues.
- For every safe, relevant intake file, complete at least one named site or system work item before source-site removal; memory distribution without site or system work is a failed handoff.
- Record the complete intake outcome: reviewed disposition, actual work, hot-memory outcome, LLM Wiki/AIWikis preservation outcome, checks, blockers, and source-site removal or keep-active reason.
- Do not create or rely on `agent-file-handoff/Archive/` during routine intake when LLM Wiki/AIWikis long memory is configured.
- Do not use watcher/daemon, queue-folder, manifest, bucket-local README instructions, or always-on background services for Agent File Handoff; the supported workflow is a one-shot intake scan during handoff load.
- `studio wp eval-file scripts/lint-llmwikis.php`
- `php scripts/test-llmwikis-starter-bundle.php` when a PHP CLI is available, to verify starter-template registry, manifest, bundle contents, duplicate detection, unsafe path rejection, and rendered/downloaded drift
- `powershell -NoProfile -ExecutionPolicy Bypass -File scripts/Test-LlmWikisPublicSurface.ps1` for route/discovery/private-file/internal-link checks
- `scripts/publish-llmwikis-packages.ps1`
- Root discovery files: `llms.txt`, `robots.txt`, `sitemap.xml`
- Use `.uai/test-plan.uai` to choose targeted checks for ordinary work and to decide when package publishing or full runtime smoke checks are justified.
- For multisite or multi-repository tasks, run a per-repository Git preflight before Sync, pull, merge, commit, or push: branch tracking, `.git/MERGE_HEAD`, unmerged index entries, ahead/behind state, and tracked generated/runtime artifacts.
- For WordPress Studio sites, do not version mutable SQLite database files such as `wp-content/database/.ht.sqlite`, `*.sqlite`, `*-wal`, or `*-shm`; keep required drop-ins, must-use plugins, `.htaccess`, and `index.php` files tracked.
- For LLM Wiki setup or broad ingest tasks, define context-budget, large-file, duplicate-file, and generated-history policies before traversing generated history, stale output, raw mirrors, package mirrors, large JSON reports, or exact duplicate groups.

## Common Checks

- Default verification is targeted: choose checks that cover the files, routes, discovery files, handoff records, or behaviors changed.
- Do not run package publishing, refresh ZIPs, or run broad runtime smoke checks by default for ordinary prompt work.
- `scripts/lint-llmwikis.php` for runtime-loaded PHP files and JSON validity.
- `scripts/test-llmwikis-starter-bundle.php` for starter registry and dynamic ZIP architecture when PHP CLI is available; report the absence of `php` rather than claiming it passed.
- `scripts/Test-LlmWikisPublicSurface.ps1` for core public pages, discovery files, private-file exclusions, static ZIP absence, comparison/security/agent/checklist copy requirements, sitemap duplicates, and internal link validity.
- Setup wizard tests should cover context-budget controls in the form, generated packet, readiness checklist, visitor-AI digest, first actions, and structured setup model.
- AGENTS.md-triggered chat-start intake before broad AI work so files dropped into `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/` update `.uai/intake-index.uai`; use `scripts/Invoke-UaiFileIntake.ps1` when available, do not create source-site `Archive/`, then process every `needs-agent-review` entry into a complete intake outcome before unrelated broad work.
- `git diff --check` for whitespace issues before packaging.
- The root workspace builder creates current WordPress upload ZIPs and checksums in `[local path redacted]`; for the current shared build, use the `v3.53.0` ZIPs under `UPLOAD-THEME` and `UPLOAD-PLUGIN`. The LlmWikis copy of Project Handoff comes from the UAIX-published `wordpress-plugin-upload-uai1-project-handoff-v3.53.0.zip`. Keep non-upload archives under `[local path redacted]`.
- The source-only handoff archive includes `agent-file-handoff/`, `llms.txt`, `robots.txt`, and `sitemap.xml`; these are public discovery files and source-only intake files, not WordPress upload packages.
- Verify `llms.txt` lists only public pages and canonical external sources, not the private repository root `AGENTS.md`, private `.uai/` files, package archives, WordPress admin routes, or private/generated output. Public tutorial pages may discuss AGENTS.md or `.uai` concepts.
- Verify `llms.txt` does not list private root `readme.human`; public tutorial pages may discuss the concept without publishing the local source file.
- `studio wp theme list` confirms active theme.
- `studio wp plugin list` confirms required plugins are active.
- `studio wp post list --post_type=page` confirms seeded pages.
- HTTP smoke check against the current Studio URL from `studio site status`.

## Editing Workflow

1. Read `AGENTS.md` first.
2. Read root `readme.human` as the human briefing companion; do not treat it as an override.
3. Perform chat-start file intake from `Content/` and `Improvement/`, avoid source-site `Archive/`, and then load the listed `.uai` files, including `.uai/intake-index.uai`; use `scripts/Invoke-UaiFileIntake.ps1` when available.
4. Process every `needs-agent-review` file from `.uai/intake-index.uai`: inspect, summarize, disposition it, complete named site/system work for every safe relevant file, record hot-memory and LLM Wiki/AIWikis preservation outcomes, and report checks before unrelated broad work.
5. Remove processed source-site copies only after the complete intake outcome and configured preservation evidence are recorded. If no safe work can be completed, leave the file active or record a durable blocker instead of silently removing it.
6. Read the strategy docs when changing positioning, roadmap, taxonomy, or governance.
7. Keep UAIX canonical route links explicit on UAIX-related explainers.
8. Keep public LLM Wiki concept copy free of creator-name attribution; direct foundational-source links are allowed.
9. Use `apply_patch` for manual code and doc edits.
10. Use `studio wp`, not bare `wp`, for WordPress state changes.
11. Run targeted syntax, whitespace, route, discovery, or runtime checks before final response when the environment allows them. Use package and full runtime checks only for ZIP/release work, broad public-surface changes, or explicit human requests.

## Release Expectations

- Do not publish until the site loads without 5xx responses.
- Publish local ZIP packages through `scripts/publish-llmwikis-packages.ps1`.
- Building or refreshing ZIPs is release-scoped work and should run the package path unless an intentional documented exception applies.
- WordPress upload artifacts use affected-version deployment signaling. When a LlmWikis package changes, its ZIP filename, theme/plugin header version, package metadata, and checksum output should reflect the current accepted system-wide version. If a package does not change, leave its filename and internal version unchanged.
- The LlmWikis.org footer should display the last system-wide version that affected LlmWikis.org, not the latest global system version when only UAIX, AIWikis, Protocol5, or another site changed.
- A full build also includes source-document hygiene: update and clean `AGENTS.md`, `readme.human`, loaded `.uai` files, strategy/progress/public-surface records, source-document disposition notes, and any active Markdown source files that describe the state being packaged.
- Full builds must verify that private source docs, `.uai`, `readme.human`, intake, preserved raw evidence, and package files remain excluded from public discovery and WordPress upload ZIPs unless deliberately converted into public handbook copy.
- Treat `[local path redacted]` as the current maintained LlmWikis theme upload package for the shared package round.
- Upload normal WordPress packages only from `[local path redacted]` and `[local path redacted]`; do not upload archives from `source-and-site-archives\`.
- Do not open public editing until legal and moderation policy exists.
- Do not add analytics or trackers without the chosen privacy disclosure.
- Do not claim live benchmark freshness without automated source and timestamp evidence.

## Recovery Notes

The local site uses SQLite. Keep:

- `wp-content/db.php`
- `wp-content/mu-plugins/sqlite-database-integration/`

If `studio wp` reports missing `wp-config.php`, run `studio site start --skip-browser` from the site root so Studio can configure the local site.

Why This File Exists

This is a UAI AI Memory handoff file from llmwikis.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 .uai file is a compact custom packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: LlmWikis Operations; Common Commands; Common Checks; Editing Workflow; Release Expectations; Recovery Notes. 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-515 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LLMWikis Operations",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/uai-operations-uai-6b8eb4f6/",
    "source_reference":  ".uai/operations.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:6b8eb4f61c20e6d5c93b093e0cfb5f64a30e30dbcd910ff94434213ffe08acdd",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-13T22:17:44.2793109Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-515",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}