AI Memory Package Wizard Integration

Purpose

MikeKappel.com treats UAIX AI Memory as a reviewed handoff and evidence-organization surface. The site package keeps current operating memory in .uai, durable reviewed memory in /docs, and evidence-bounded research recall in /reports.

Current UAIX setup route

• Base wizard: https://uaix.org/en-us/tools/ai-memory-package-wizard/
• Agent File Handoff configuration: https://uaix.org/en-us/tools/ai-memory-package-wizard/#setup-file-handoff
• LLM Wiki long-memory planning: https://uaix.org/en-us/tools/ai-memory-package-wizard/#setup-llm-wiki
• Agent File Handoff plus LLM Wiki planning: https://uaix.org/en-us/tools/ai-memory-package-wizard/#setup-file-handoff-llm-wiki
• Advanced rare-use Talisman System: https://uaix.org/en-us/ai-memory/talisman-system/

Current support boundary

The current wizard is an eight-step, local-first package planning flow. It supports page-level validation, local browser draft restore, prompt nudges, Safe Structured Output Mode, .uai/archives logs, active .uai files, .uai/exports artifacts, JSON-LD graphs, llms.txt, llms-full.txt, package model JSON, manifest JSON, manifest overlay JSON, receiver briefs, startup packets, browser-generated ZIP packages, canonical starter ZIP links, Agent File Handoff planning, and LLM Wiki long-memory planning when selected.

It is not a hosted importer, automatic repository writer, WordPress admin installer, automatic LLM Wiki sync, SDK, CLI, certification authority, endorsement surface, or runtime orchestrator.

Implemented package layout

.uai/
  identity.uai
  world-context.uai
  totem.uai
  taboo.uai
  short-term-memory.uai
  coding-standards.uai
  startup-packet.uai
  system-profile.uai
  receiver-brief.uai
  project-handoff.uai
  file-handoff.uai
  long-term-memory.uai
  archives/
  exports/

docs/
  index.md
  uai-memory-package-current-alignment.md
  long-term-memory-map.md
  uai-memory-handoff-map.md
  report-to-doc-curation.md
  report-staleness-review.md
  reviewed Architecture Notes

reports/
  indexable ordinary report pages plus noindex sensitive and raw-resource boundaries

Intake and organization rule

Agent File Handoff is incomplete until every active agent-file-handoff/Content/, agent-file-handoff/Improvement/, or misplaced root intake file has a recorded disposition and proof-of-use evidence. Site content intake must either be used in the site/package or explicitly dispositioned and archived. Long-term memory that should steer future work belongs in .uai and curated /docs; raw reports belong in /reports until reviewed.

Site integration

The public site may surface this as evidence for:

• AI Memory package design
• Project Handoff and receiver read-order discipline
• Agent File Handoff disposition discipline
• .uai short-term memory mapped to durable /docs research
• reviewed long-term memory separated from raw report recall
• AI, .NET, SQL, and TypeScript portfolio positioning

Receiver warning

Do not treat generated memory files, report archives, or browser-generated packages as automatic truth, automatic sync, site installation, credential authority, runtime execution, or approval to write into a repository.