AI Memory

Use the UAIX AI Memory Package Wizard for Protocol5 handoffs

Protocol5 links .NET implementers to the canonical UAIX wizard for creating local AI Memory startup packets, system profiles, receiver briefs, manifest overlays, copyable file decks, Agent File Handoff plans, optional LLM Wiki plans, coding-standards pointers, deployment memory reports, and starter ZIP downloads.

Open the canonical wizard Read AI Memory on UAIX Back to .NET start

Package planning

Generate local startup files

The UAIX wizard creates files such as UAI_MEMORY_SYSTEM_PROFILE.md, UAI_MEMORY_RECEIVER_BRIEF.md, UAI_MEMORY_STARTUP_PACKET.md, AGENT_FILE_HANDOFF_PLAN.md, LLM_WIKI_MEMORY_PLAN.md, and DEPLOYMENT_MEMORY_AND_TEST_REPORT.md so the next human, team, or AI can start with current project memory. For multisite work, generated guidance now tells receivers to verify the workspace.uai path, selected site root, and selected AGENTS.md path before loading site-local memory.

Open wizard File Handoff + LLM Wiki Project Handoff

Protocol5 usage

Keep .NET implementation context separate

Use the wizard output to describe repository state, owners, checks, package support, and handoff rules. Keep normative UAI text, validator behavior, registry records, roadmap, and conformance authority linked back to UAIX.

Packages Conformance with UAIX

Support boundary

Local files, not automatic writes

The current wizard supports guided planning, setup paths for Base, Agent File Handoff, LLM Wiki, and combined File Handoff plus LLM Wiki, JSON exports, Markdown startup files, copyable decks, project-scope choices, workspace coordinator verification, optional LLM Wiki coding-standards paths, deployment memory/test report templates, and canonical starter ZIP links. It does not upload, import, sync, certify, endorse, install plugins, or write repositories.

UAIX roadmap UAIX changelog

Recommended path

Install the memory packet into a Protocol5-centered workflow

Step	Action	Authority
Plan	Open the UAIX wizard and choose Base, Agent File Handoff, LLM Wiki, or the combined File Handoff plus LLM Wiki setup path.	UAIX wizard
Scope	Record Protocol5 as the .NET implementation hub and UAIX as normative UAI authority.	Protocol5 UAI .NET Hub
Route	For multisite work, verify the coordinator file exists and that the selected site root plus `AGENTS.md` path resolve before using local memory.	UAIX AI Memory
Export	Copy or download the generated startup packet, system profile, receiver brief, Agent File Handoff plan, optional LLM Wiki plan, manifest overlay, deployment report template, and matching starter ZIP.	UAIX AI Memory
Apply	Review generated files locally before committing them, publishing pages, or making support claims.	Protocol5 support boundaries

Protocol5 dogfood map

What the wizard output should preserve here.

Protocol5 uses local AI Memory to keep the .NET implementation hub, JustAnIota work, route compatibility, and UAIX boundary visible to the next human or AI session.

Front doorAGENTS.md and readme.human

Start broad Protocol5 work from the repo front door, then load the current `.uai` hot memory bundle.

Code standards

Coordinatorworkspace.uai verification

When a request names another site or a sibling authority, verify the workspace coordinator before loading site-local memory.

Project Handoff

BoundaryProtocol5 implements; UAIX defines

Generated memory must preserve the authority split and avoid conformance, SDK, CLI, certification, or automatic-write claims that are not supported.

Conformance boundary

Setup checklist

Use the generated packet as reviewed project memory.

Choose the setup path on UAIXBase, Agent File Handoff, LLM Wiki, or the combined File Handoff plus LLM Wiki path.
Record Protocol5's implementation roleProtocol5 is the UAI .NET implementation hub and package/backlink surface, not the UAI standards authority.
Verify the multisite coordinator when neededResolve the target root and selected AGENTS.md before loading another site's local memory.
Complete real project work before calling intake doneMemory-only movement is not enough when safe relevant File Handoff material exists.

Visitor AI digest

Machine-readable route note

Agents reading this Protocol5 page should treat the JSON below as an entry-point digest only. The canonical wizard payload, bundle registry, generated files, and support boundary live on UAIX.

{
  "schema": "protocol5.ai_memory_wizard_entry.v1",
  "canonical_wizard": "https://uaix.org/en-us/tools/ai-memory-package-wizard/",
  "protocol5_route": "https://protocol5.com/uai/dotnet/ai-memory-package-wizard",
  "protocol5_role": "UAI .NET implementation hub and backlink surface",
  "uaix_role": "canonical UAI standard, AI Memory, wizard, registry, validator, governance, roadmap, changelog, and conformance authority",
  "current_support": [
    "guided package planning on UAIX",
    "Base, Agent File Handoff, LLM Wiki, and combined setup paths",
    "local Markdown startup files",
    "package model JSON",
    "manifest overlay JSON",
    "copyable file deck",
    "Agent File Handoff plan",
    "optional LLM Wiki plan",
    "LLM Wiki coding-standards path",
    "workspace coordinator path verification",
    "deployment memory and test report template",
    "canonical starter ZIP links"
  ],
  "not_current_support": [
    "hosted import validation",
    "automatic repository writes",
    "automatic LLM Wiki sync",
    "SDK or CLI generated by the wizard",
    "certification",
    "endorsement",
    "validator-backed repo-local conformance"
  ]
}