UAI Memory Package Current Alignment

Purpose

This Architecture Note records the current MikeKappel.com .uai memory package alignment with the UAIX AI Memory Package Wizard. It keeps current working memory, durable long-term memory, and raw report recall in separate lanes.

Current UAIX wizard interpretation

The current UAIX wizard is an eight-step local-first package planning flow. It can generate or verify launch-baseline files, typed Project Handoff files, Agent File Handoff guidance, LLM Wiki long-memory planning, JSON-LD graph output, llms.txt, llms-full.txt, package model JSON, manifest JSON, manifest overlay JSON, file deck records, receiver briefs, startup packets, and browser-generated ZIP packages.

The wizard does not create hosted imports, automatic repository writes, WordPress admin installation, automatic LLM Wiki sync, certification, endorsement, SDK behavior, CLI behavior, or runtime orchestration.

Launch-baseline set

• .uai/identity.uai
• .uai/world-context.uai
• .uai/totem.uai
• .uai/taboo.uai
• .uai/short-term-memory.uai
• .uai/coding-standards.uai

Active memory organization

• .uai/archives/ keeps raw session evidence and prior memory snapshots.
• .uai/ keeps active human-readable and receiver-agent memory.
• .uai/exports/ keeps machine-readable summaries, package-model JSON, file-deck JSON, graph, and LLM summaries.
• .uai/long-term-memory.uai points to curated /docs notes rather than raw research reports.
• wiki/ remains reserved for deliberate LLM Wiki compatibility work and is not the default memory path.

Reports and docs organization

• /docs/ is curated durable memory and reviewer-facing Architecture Notes.
• /reports/ is evidence-bounded research and recall material. Ordinary canonical HTML reports are index-follow, user-confirmed sensitive reports are search-only/noindex, and raw Markdown/JSON resources remain noindex.
• Agent File Handoff archives are disposition evidence. They do not steer asserted public copy until the material is reviewed and either curated into /docs or retained as an evidence-bounded /reports item.
• Report-derived facts become public evidence only after review, rewrite, and mapping to a compact .uai pointer.

Public-site boundaries

• WordPress remains the server-rendered production runtime.
• JavaScript remains progressive enhancement.
• Public pages must not invent biography, employment history, production status, credentials, metrics, or deployment facts.
• Public static research indexes remain default-visible only.
• PHP-guarded private helper data remains outside public assets/data JSON.

Review boundary

.uai/totem.uai and .uai/taboo.uai remain generated-needs-review; they are included in the launch-baseline read order but are not promoted without exact approval wording from Mike.

Current no-regression memory

• .uai/navigation-compact-menus.uai preserves the recurring desktop grouped-menu z-index guard.
• .uai/public-facing-language-guard.uai preserves the route-specific public-copy guard and active-doc summary guard.
• ops/uaix-core-artifact-catalog-hotfix/ remains a CLI-only operational kit and does not self-apply through the theme.

Historical v9.0.8 residual QA note

The historical v9.0.8 pass preserved the v8.8.56 Research Dashboard, breadcrumb, and source-level separator fixes and rechecked breadcrumb URL normalization. Current package identity is governed by E:/Source/WP/workspace.uai. Real browser QA still requires a version-proven WordPress runtime or deployed site.