AIWikis Org Human Briefing

AIWikis.org is a WordPress publication project for dogfooding LLM Wiki, UAIX, source-governance, source-package, and agent-handoff guidance.

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/files/aiwikis/readme-human-069f97e8/
Source reference	readme.human
File type	human
Content category	uai-system
Last fetched	2026-05-15T00:23:56.0837262Z
Last changed	2026-05-11T20:10:15.9695781Z
Content hash	sha256:069f97e810d45f6b6ba03fb937d192cebcabcba074f85b479146294ceba2262f
Import status	changed
Raw source layer	data/sources/aiwikis/readme-human-069f97e810d4.human
Normalized source layer	data/normalized/aiwikis/readme-human-069f97e810d4.txt

Current File Content

Structure Preview

• AIWikis.org Human Briefing
• What The AI Should Protect
• What Humans Need To Review
• How The AI Reads This Project
• Build Outputs

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.

# AIWikis.org Human Briefing

AIWikis.org is a WordPress publication project for dogfooding LLM Wiki, UAIX, source-governance, source-package, and agent-handoff guidance.

The first package passes exposed two useful dogfood findings: package checks must inspect actual files such as `agent-file-handoff/` and `.uai` records, and consumer sites must not relabel source-published packages as local products. AIWikis consumes the LlmWikis `llm-wiki-starter-bundle-v2.8.0.zip` and the UAIX `uai1-project-handoff-v2.8.0.zip`; it should not publish `aiwikis-starter-pack.zip`. For wp-admin install convenience, `AIWikis-Publish` may mirror the UAIX-owned `uai1-project-handoff-v2.8.0.zip` as a separate plugin artifact while preserving UAIX publisher labels.

Deployment versioning should stay affected-site scoped. AIWikis theme/plugin ZIP names, internal versions, release manifests, and checksums should advance only when AIWikis or that package changed; unchanged artifacts keep their previous names and versions so the filename tells humans whether deployment is needed. The site footer should show the last system-wide version that affected AIWikis.org, not the newest version caused by another site.

The site should help humans and AI agents understand how to build and operate source-governed AI-readable knowledge systems. It must attribute and link back to the source projects it applies:

- LLMWikis.org for LLM Wiki handbook patterns, starter templates, trust labels, metadata, source policy, governance, and agent rules.
- UAIX.org for UAI-1, Project Handoff, AGENTS.md plus `.uai` context patterns, validator/conformance material, implementation boundaries, and public evidence surfaces.
- Protocol5.com for Protocol5 parent-brand, Mathematics, UAI .NET implementation packages, route contracts, package distribution, and compatibility-mirror evidence.
- ɩ.com / JustAnIota.com for JustAnIota public identity, compact-message tooling, the HTML Keyless Extractor, implementation-profile evidence, and JustAnIota handoff state.

AIWikis now also has a source-side file-native wiki skeleton: `raw/` for immutable source inputs, `wiki/` for compiled Markdown nodes, and `config/` for autonomous wiki rules and graph output. This layer is project source infrastructure, not public upload content. Because AIWikis is multisite, `wiki/index.md` is a root router for source sub-wikis and global-only records; `wiki/uaix/index.md`, `wiki/llmwikis/index.md`, `wiki/protocol5/index.md`, and `wiki/justaniota/index.md` own source-specific all-files maps, and `wiki/global/index.md` owns organization-level, workspace, cross-site, and claim-boundary records.

AIWikis also has a repeatable recovered-content pipeline in `tools/reprocess-content.ps1`. It crawls public source/discovery/package surfaces, scans local processed archives, preserves raw `.md` and `.uai` evidence under `sources/recovered/raw/`, generates compact public summaries and indexes under `content/pages/`, and records the recovery audit trail under `reports/`.


The current context-budget finding is recorded at `reports/2026-05-04-llm-wiki-context-budget-audit.md`. Routine AI sessions should not traverse `data/generated-history/`, `content/archive/generated-source-file-stale/`, `data/sources/`, `data/normalized/`, `sources/recovered/raw/`, large `reports/*.json`, or raw system archives unless the task explicitly targets provenance, source sync, archive recovery, or checksum verification.

For UAIX AI Memory work, that source-file view should expose the current Package Wizard as a populated operating-profile generator: source-authority policy, memory-update timing, evidence ledger, conflict-resolution policy, testing, deployment, review, risk, rollback, receiver brief, startup packet, and optional LLM Wiki memory-plan guidance.


The Intake Outcome Ledger at `content/pages/016-intake-outcome-ledger.md` is the public-safe feedback page for that workflow. After deployment, `/intake-outcome-ledger/` should tell people what happened to recently digested files, which surfaces changed, what was deferred or blocked, and where the reviewed documentation can be viewed.

The Roadmap at `content/pages/017-roadmap.md` is the public planning surface. It should separate current support, next work, later research, and blocked claims so humans and future agents do not have to reconstruct priorities from scattered changelog entries.



Source-Site Outcome Routing at `content/pages/031-source-site-outcome-routing.md` closes a dogfood gap: when a source repository processes intake and creates staged drafts, that does not automatically change AIWikis.org. AIWikis needs an explicit routing pass that says what changed, what stayed staged, what public/source-side surfaces were updated, and what still needs human review or deployment.

The 2026-05-01 source-site report preservation manifest at `raw/system-archives/2026-05-01-source-site-report-preservation.json` closes the next gap: summaries and staged artifacts do not prove raw original reports survived. When AIWikis is expected to retain final memory, the source archive files need copied destinations, file counts, and checksums.

The 2026-05-03 UAIX recent-work sweep at `raw/system-archives/2026-05-03-uaix-recent-work-sweep.json` closes the follow-up gap for the last couple days of UAIX work. It preserves the current wizard setup URL, Agent File Handoff, optional LLM Wiki, roadmap, agentic-system, deploy-check, and processed-intake source state with 23 copied files and hashes. AIWikis can remember that work, but UAIX.org remains the current support authority.

The 2026-05-03 LlmWikis recent-work sweep at `raw/system-archives/2026-05-03-llmwikis-recent-work-sweep.json` closes the matching follow-up gap for the last couple days of LlmWikis work. It preserves the processed roadmap input, agentic orchestration guide, task packet template, support escalation checklist, starter-bundle registry, discovery, tests, and handoff source state with 25 copied files and hashes. AIWikis can remember that work, but LLMWikis.org remains the current handbook authority.

The 2026-05-03 ɩ.com / JustAnIota intake recovery at `raw/system-archives/2026-05-03-justaniota-intake-processing.json` preserves the 13-file active Improvement batch for compact-message research, keyless JSON and HTML extraction, Unicode/PUA boundaries, public-site identity, logo/theme direction, and File Handoff plus LLM Wiki completion-rule fixes. AIWikis can remember and route that work under `/justaniota/`, but JustAnIota.com remains the source authority and UAIX.org remains the UAI-1 authority.

The 2026-05-05 JustAnIota short-domain SEO release sweep at `raw/system-archives/2026-05-05-justaniota-short-domain-seo-release-sweep.json` preserves the current source-site decision that `ɩ.com`/`xn--8na.com` redirects into the canonical JustAnIota.com package. It also records locale-prefixed human URLs, official social preview metadata, the `ns12-locale-router` 2.7.0 package evidence, and guarded deletion of the obsolete separate short-domain install.

The Memory Coverage Matrix and Claim Boundary Register at `content/pages/029-memory-coverage-matrix.md` and `content/pages/029-claim-boundary-register.md` make the next layer explicit: what AIWikis currently covers, what is only partially covered or source-only, what is blocked, and which phrases require source-site evidence before they can appear in public or package copy.

The Deep Cognitive Archive is the local name for this slower reasoning layer: public pages stay polished, `.uai` files stay compact enough for active handoff, and the source-side wiki/archive layer keeps why, rejected alternatives, contradictions, and lineage.

AIWikis now has a local Project Handoff export loop in `tools/generate-handoff-export.ps1`. It proves, during dogfood checks, that selected reviewed wiki nodes and current `.uai` files can produce a compact handoff packet. This is local release evidence only; it is not UAIX certification, a hosted generator, or public endorsement.

Reviewed public pages under `content/pages/` are rendered directly by `aiwikis-core` in development and packaged into `aiwikis-core/data/pages` for deployment. The old WordPress Page seed/import strategy has been abandoned so document edits do not require reseeding. Raw archive reports are not rendered directly as public pages.

## What The AI Should Protect

- Source boundaries and citations.
- The distinction between source-site authority and AIWikis archive memory.
- The context budget: use indexes, source guides, Markdown reports, bounded generated pages, and hashes before opening generated-history, stale archive, raw mirror, normalized mirror, or large JSON layers.
- Clear separation between current recommendations, AIWikis build observations, proposed changes, accepted changes, rejected changes, and open questions.
- Installable WordPress package roots, publish outputs, and source-package ownership labels.
- Affected-version deployment labels: package filenames and footer versions move only when AIWikis is affected, not when another site changes.
- No secrets, credentials, local private paths, or raw private material in public packages.
- No unsupported claims of certification, endorsement, SDK support, CLI support, or production deployment.
- `needs-agent-review` intake files must be processed before unrelated broad work.

## What Humans Need To Review

- Public Markdown page wording, especially where raw archive material has only been summarized.
- Generated recovered-content summaries and indexes, especially where source reports were summarized instead of copied.
- Whether future source packages should be consumed exactly as published, mirrored for install convenience, or only referenced as upstream artifacts.
- Whether the staged LLMWikis integration drafts should be promoted into LLMWikis public handbook pages, summarized in AIWikis only, or held for vendor/source verification.
- WordPress admin setup, menu creation, homepage assignment, plugin activation, theme activation, and public download placement.
- Any policy, security, privacy, legal, production, architecture, or source-governance change.
- Whether a future archive pull should become a public summary page, a source-side wiki node only, or a deferred raw-memory record.

## How The AI Reads This Project

The AI should start with root `AGENTS.md`, read this file, refresh `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, ignore `agent-file-handoff/Archive/` unless a human explicitly names an archived file, and load the `.uai` files listed in AGENTS.md before broad edits.

## Build Outputs

The package scripts write ZIP artifacts and release metadata to:

`[local path redacted]`

Why This File Exists

This is a UAI AI Memory handoff 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

readme.human is the human-facing companion to the agent entry file. It gives maintainers a plain-language briefing while leaving hard rules in AGENTS.md, constraints, and current human instructions.

Structure

The file is structured around these visible headings: AIWikis.org Human Briefing; What The AI Should Protect; What Humans Need To Review; How The AI Reads This Project; Build Outputs. 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

• Global File Index
• Reports

Provenance And History

• Current observation: 2026-05-15T00:23:56.0837262Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-029 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "AIWikis Org Human Briefing",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/readme-human-069f97e8/",
    "source_reference":  "readme.human",
    "file_type":  "human",
    "content_category":  "uai-system",
    "content_hash":  "sha256:069f97e810d45f6b6ba03fb937d192cebcabcba074f85b479146294ceba2262f",
    "last_fetched":  "2026-05-15T00:23:56.0837262Z",
    "last_changed":  "2026-05-11T20:10:15.9695781Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-029",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-15T00:23:56.0837262Z"
}