AI Memory | UAIX | Universal Artificial Intelligence Exchange

How to use this page

Use this page for durable AI project memory, supported starter configurations, dynamic canonical-template downloads, and the boundary between portable UAI memory packets and deeper LLM Wiki knowledge.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

Memory path

AI Memory Package Wizard UAI Memory Management .uai File Guide memory-maintenance.uai

Durable AI Memory

Build compact project memory without turning history into truth

Start with the wizard when you need a usable package. Use AI Memory for accepted current context, include memory-maintenance plus identity, world-context, Totem, Taboo, Talisman, and short-term memory as the ordinary launch-baseline files. Hot .uai records are current-state memory, not dated changelogs; if a fact remains there, agents should be able to load it completely at startup. Agents read and obey Totem, Taboo, and Talisman by default, but must not modify, weaken, replace, delete, or bypass them without exact human artifact-and-operation authorization. Fit long-term memory to the organization: local docs or site wiki can work for bounded local projects, shared LLM Wiki is often the professional project-group and corporate pattern, and advanced shared memory systems belong to more complex cross-system needs.

Bundle

One source for samples and ZIP

Starter ZIPs are generated from canonical templates, generated manifests, and the same resolved samples rendered on the page so download drift is not possible.

Pattern

Project Handoff makes memory operational

AGENTS.md, .uai/readme.human, and .uai files give the next assistant a predictable load path before edits begin, without loading old research or dated package history by default.

Launch-Baseline Required Files

Memory-maintenance is required first

Generated .uai/memory-maintenance.uai, .uai/identity.uai, .uai/world-context.uai, .uai/totem.uai, .uai/taboo.uai, .uai/talisman.uai, and .uai/short-term-memory.uai files are required for every launch-baseline UAIX memory or handoff package. Agents read and obey Totem, Taboo, and Talisman by default, but must not modify, weaken, replace, delete, or bypass them without exact human artifact-and-operation authorization. Project/developer packages and code-bearing assistant packages also require .uai/coding-standards.uai, .uai/architecture.uai, and .uai/next-recursive-prompt.uai. For agents with no code, automation, executable workflow, or code-like artifacts, architecture.uai and next-recursive-prompt.uai are out of scope. The stored human-visible plan is used for continuation or directly related requests, not as a replacement for current user instruction. Related active intake supersedes or expands the stored loop and still requires project work.

File Guide

Every package file has a declared required scope

Use the .uai File Guide to verify universal required, profile-required, content-triggered required, configuration-specific required, and out-of-scope file handling before relying on a package.

Depth

Shared wiki memory fits groups

Use site-local docs or wiki for bounded local work. Use shared LLM Wiki memory for project groups, departments, and corporate knowledge that needs owners, indexes, review states, and cross-project retrieval.

Reports

Synthesize before you point

When reports, audits, architecture notes, or coding best practices are processed, preserve full bodies in the durable target, keep long-term memory as a pointer ledger, and populate hot .uai synthesis with accepted themes, implementation implications, rejected guidance, and next actions.

Context Budget

Archive before slimming

When hot files grow too large, preserve pre-slim snapshots in cold memory with hashes and routing summaries, then keep only current truth in AI Memory.

Memory path

AI Memory Package WizardBuild the startup packet, system profile, receiver brief, universal required files, profile-required files, content-triggered required files, configuration-specific required files, manifest overlay, copy-paste files, long-term pointer ledger required for durable-memory configuration, readiness checks, and canonical ZIP links.UAI Memory ManagementWordPress admin surface for live .uai memory, Advanced Persona files, existing docs/wiki roots, update prompts, and scale-fit durable memory checks..uai File GuideClosed required-file-set guide for every published .uai memory file.memory-maintenance.uaiDedicated lifecycle, default active instruction anchors, validation, and memory-write safety rule for every UAIX memory package.next-recursive-prompt.uaiDedicated code-scope resume artifact for continuation and directly related coding work.Canonical AI MemoryLayer raw sources, durable wiki memory, derived graph projections, compact packets, and handoff transfer without blurring authority.Using UAI Packages With An LLM WikiPractical routing between compact packages and deeper wiki memory.Talisman SystemDefault Talisman guidance plus advanced anchor-change governance for persistent Totem and Taboo anchors.Context Budget GuideKeep hot handoff files small while preserving long research in cold memory.Project HandoffEngineering pattern for AI Memory files.Agent File HandoffDropped-file intake before broad work.ReportsLLM Wiki comparison background.RoadmapCurrent and planned tooling boundary.

Alias routeRequested entry path

/AI_Memory -> /en-us/ai-memory/

The requested /AI_Memory path redirects to the canonical locale-prefixed AI Memory page while preserving the clean public route rule.

What AI Memory Means In UAIX

UAI AI Memory is a lightweight, portable, file-based standard for durable context. It gives humans and AI agents a reviewable packet of project memory instead of relying on private chat history, hidden model settings, one vendor account, or a stale folder of notes.

AI Memory is not a general knowledge base. It is the compact operating memory a future actor should load before acting: project purpose, current state, constraints, decisions, next actions, owners, trust boundaries, maintenance rules, and targeted checks.

Context budget: keep AI Memory hot and small. Long research, old progress detail, pre-slim handoff snapshots, and deep rationale should live in an LLM Wiki or AIWikis-style cold memory layer with routing summaries, hashes, and evidence logs. Hot .uai memory is current-state memory, not a dated changelog. Promote only the reviewed current conclusion back into the AI Memory packet.

Canonical AI Memory

Use Canonical AI Memory when you need the layer map behind the packet: raw sources, reviewed LLM Wiki memory, derived graph projections, compact UAI AI Memory, Project Handoff transfer context, and the execution agent that still has to obey local rules.

Fastest Practical Path

Most readers should start with the AI Memory Package Wizard. It turns the current supported presets into a reviewable startup packet, receiver brief, system profile, manifest overlay, long-term pointer ledger required for durable-memory configuration, copyable file deck, and canonical ZIP link without claiming hosted import, repository writes, automatic sync, SDK, CLI, certification, or endorsement.

The default talisman.uai file belongs in the normal wizard flow with totem.uai and taboo.uai. Use the Talisman System page for advanced external-enforcement guidance when a complicated, persistent, multi-actor ecosystem needs anchor change-control, no-op talk-back, audit evidence, and rollback.

Why Unstructured AI Memory Fails

Unstructured memory fails because it mixes old chats, generated summaries, wiki notes, screenshots, logs, and roadmap guesses without saying what is current or binding. The next agent may miss a red line, believe an obsolete claim, leak sensitive material, or run the wrong checks because the project never named its memory contract.

No front door: the agent cannot tell where to begin.
No lifecycle: working state, transfer packets, decisions, onboarding notes, and audit evidence age differently.
No trust boundary: internal-only material can be handed to an outside vendor or autonomous agent by accident.
No canonical source: visible examples, downloadable ZIPs, and docs drift because sample files are copied in several places.

Why File-Based Memory Works

File-based memory is boring in the best way. It can be reviewed in a pull request, zipped for a handoff, redacted before external sharing, loaded by different agents, archived with a release, and tested for drift. UAIX uses plain text and deterministic manifests so people can inspect what an AI is about to treat as context.

AI Memory Taxonomy

UAIX now treats Project AI Memory as the ongoing working-memory configuration and Project Handoff as a subtype of AI Memory for transfer. Additional configurations exist only when they have a different lifecycle, trust boundary, or consumption pattern. Team Memory and Product Memory are documented as views over existing bundles, while certification-style or regulated-data memory is deferred until the public evidence and safety process exist.

Choose the right AI Memory configuration

These supported starter bundles are presets over one canonical file-template registry. Shared files come from the same template IDs; bundle-specific guidance is added through metadata and overlays.

Configuration	Use when	Lifecycle and trust boundary	Download
Project AI Memory `project-ai-memory`	Use when a project is active and context must persist across many AI sessions without turning the bundle into a full knowledge base.	Lifecycle: Maintained continuously; current-state and next-action files change often, decisions and constraints change carefully. Trust: Internal or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent.	uai-ai-memory-starter.zip
Project Handoff `project-handoff`	Use when the next actor must take over a project safely and needs current state, constraints, decisions, checks, and ownership context.	Lifecycle: Prepared before transfer, reviewed at acceptance, and updated when responsibility or support boundaries change. Trust: Can be internal or external, but external handoffs must be sanitized and approved before sharing.	uai-project-handoff-starter.zip
Agent Session Memory `agent-session-memory`	Use when an agent or tool needs to resume a task with enough state to continue without replaying a whole chat transcript.	Lifecycle: Created for a run or task, updated frequently, then merged into project memory or archived when the task closes. Trust: Often operational and sensitive. Keep permissions, tool access, blocked actions, and cleanup state explicit.	uai-agent-session-memory-starter.zip
Onboarding Memory `onboarding-memory`	Use when the first job is orientation rather than ownership transfer, incident review, or deep rationale capture.	Lifecycle: Reviewed before each onboarding cohort or external introduction; kept concise and introductory. Trust: Usually shareable after review, but remove internal strategy, customer data, credentials, and privileged operations.	uai-onboarding-memory-starter.zip
Decision Memory `decision-memory`	Use when rationale and tradeoffs matter more than current task status.	Lifecycle: Append-first and review-heavy; reversals should explain what changed rather than erase history. Trust: Contains internal strategy when the source bundle records it. Review before exposing externally or to agents with broad write permissions.	uai-decision-memory-starter.zip
Client or Vendor Handoff Memory `external-handoff-memory`	Use when a client, vendor, partner, or outside agent needs enough context to continue work without receiving internal-only memory.	Lifecycle: Prepared as an export, redacted, approved, shared, and archived with a dated changelog entry. Trust: Strict external boundary. Remove secrets, credentials, private customer data, legal strategy, internal pricing, and unsupported claims.	uai-external-handoff-memory-starter.zip
Incident or Audit Memory `incident-audit-memory`	Use when facts, timestamps, mitigations, owners, evidence links, and follow-up commitments need to travel together.	Lifecycle: Opened during review, updated as evidence is confirmed, closed with follow-up owners and a retained audit trail. Trust: Potentially sensitive. Sanitize customer data, security details, credentials, legal material, and private evidence before external sharing.	uai-incident-audit-memory-starter.zip
LLM Wiki Export Memory `llm-wiki-export-memory`	Use when a large internal wiki needs a small, reviewable, portable packet for a project, handoff, onboarding, or agent task.	Lifecycle: Generated from reviewed wiki material, checked against source citations, then promoted or discarded after use. Trust: Wiki material is background until reviewed. Cite sources, flag uncertainty, and redact private material before export.	uai-llm-wiki-export-memory-starter.zip
Office Assistant Memory `office-assistant-memory`	Use when an AI supports office administration without making the package primarily a software project handoff.	Lifecycle: Maintained continuously; updated when preferences, contacts, workflows, recurring tasks, boundaries, or authority change. Trust: Often private or internal. Minimize personal data, credentials, financial information, HR details, legal content, and private communications.	uai-office-assistant-memory-starter.zip
Executive Assistant Memory `executive-assistant-memory`	Use when priorities, people, meetings, decisions, and follow-through need durable assistant context.	Lifecycle: Continuously maintained with frequent updates to priorities, people, commitments, and communication rules. Trust: Highly sensitive. Requires strong redaction and authority boundaries before sharing.	uai-executive-assistant-memory-starter.zip
Personal Assistant Memory `personal-assistant-memory`	Use when privacy and freshness matter more than project history.	Lifecycle: Continuously maintained; privacy and freshness are more important than project history. Trust: Private by default. Avoid unnecessary sensitive personal data.	uai-personal-assistant-memory-starter.zip
AI Chatbot Friend Memory `chatbot-friend-memory`	Use when social memory and relationship boundaries are the central assistant context.	Lifecycle: Continuously maintained; relationship boundaries and consent rules are stable while interests and current-life context change over time. Trust: Private and consent-bound. Must include boundaries that prevent manipulation, dependency reinforcement, identity deception, unsupported professional authority claims, and unsupported memory claims.	uai-chatbot-friend-memory-starter.zip
Companion AI Memory `companion-memory`	Use when the package needs durable continuity without pretending the assistant is human or a replacement for professional help.	Lifecycle: Continuously maintained with frequent review of boundaries, crisis guidance, consent, and user preferences. Trust: Private, sensitive, and safety-bound. Keep support boundaries explicit.	uai-companion-memory-starter.zip
Tutor or Coach Memory `tutor-coach-memory`	Use when learning progress and coaching boundaries matter more than repository state.	Lifecycle: Updated after learning sessions, milestones, assessments, topic changes, or goal changes. Trust: Educational or coaching context. Avoid sensitive records unless explicitly reviewed and necessary.	uai-tutor-coach-memory-starter.zip
Creative Partner Memory `creative-partner-memory`	Use when style, canon, constraints, assets, audience, or creative direction need to travel together.	Lifecycle: Updated when style, canon, constraints, assets, audience, or creative direction changes. Trust: May contain private drafts, unreleased work, IP-sensitive ideas, brand strategy, or client material.	uai-creative-partner-memory-starter.zip
Household Assistant Memory `household-assistant-memory`	Use when home context, recurring routines, and privacy boundaries need durable assistant memory.	Lifecycle: Updated when routines, household members, constraints, vendors, schedules, or safety rules change. Trust: Private household memory. Minimize addresses, children data, health details, financial data, and access codes.	uai-household-assistant-memory-starter.zip
Customer or Front-Desk Assistant Memory `customer-front-desk-memory`	Use when public-facing or semi-public assistant memory needs public claims, source material, privacy, and escalation boundaries.	Lifecycle: Updated when public hours, services, policies, contacts, escalation paths, forms, scripts, or boundaries change. Trust: Public-facing or semi-public. Must not expose internal-only notes, customer private data, credentials, legal/security details, or unsupported claims.	uai-customer-front-desk-memory-starter.zip
General Non-Project AI Memory `general-non-project-ai-memory`	Use when no specific non-project assistant preset matches but the package still needs portable assistant memory.	Lifecycle: Maintained as the assistant role, user preferences, boundaries, recurring context, and active memory change. Trust: Determined by declared sensitivity and assistant role; private by default until reviewed.	uai-general-non-project-ai-memory-starter.zip

Views and presets over supported bundles

Team Memory: A lightweight shared team view over Project AI Memory plus owner and onboarding records. Model this as a view until UAIX has stronger role, permission, and multi-project guidance.
Product Memory: A durable product or feature-area view over project state, roadmap, decisions, and constraints. Model this as a view because the underlying files are the same as Project AI Memory plus Decision Memory.

Deferred configurations

Certification Memory: Evidence packet for formal certification or endorsement workflows. Deferred because UAIX does not currently publish certification, endorsement, or hosted validation support.
Regulated Data Memory: Memory that intentionally carries restricted personal, customer, legal, or compliance-sensitive material. Deferred until secure storage, redaction, access-control, and approval processes are outside the starter-bundle boundary.

Use the AI Memory Package Wizard when one supported starter configuration should become a package model, populated system profile, receiver brief, startup packet, manifest overlay, copy-paste file deck, Agent File Handoff plan required for Agent File Handoff configuration, long-term semantic pointer ledger required for durable-memory configuration, readiness review, and canonical ZIP download.

Which Configuration To Choose

Situation	Use	Why
An active project needs continuity across AI sessions.	Project AI Memory	It keeps current state, constraints, decisions, next actions, and agent instructions alive without becoming a full wiki.
Ownership, execution, or responsibility is moving.	Project Handoff	It packages the transfer brief, acceptance criteria, owners, constraints, and verification plan.
An agent run was interrupted or must resume later.	Agent Session Memory	It keeps task-local state short-lived and prevents a whole chat transcript from becoming project truth.
A new human, contractor, stakeholder, or agent needs a curated start.	Onboarding Memory	It emphasizes overview, glossary, owners, first actions, and safe boundaries.
Rationale matters more than status.	Decision Memory	It preserves tradeoffs, rejected options, reversals, and open questions.
A client, vendor, or outside agent needs context.	Client or Vendor Handoff Memory	It adds redaction and approval guidance around a stricter external trust boundary.
An incident or audit needs a portable packet.	Incident or Audit Memory	It keeps timeline, evidence references, decisions, mitigations, owners, and follow-up together.
A deep wiki needs a portable snapshot.	LLM Wiki Export Memory	It exports reviewed wiki material into a compact packet without letting the wiki override project truth.
The organization needs durable, searchable institutional knowledge.	LLM Wiki	It is stronger for deep internal documentation, source synthesis, long-lived research, and broad knowledge accumulation.
A complicated, persistent, multi-actor ecosystem needs advanced Totem, Taboo, and Talisman change governance.	Talisman System	It keeps anchor change requests behind no-op behavior, human review, audit evidence, rollback, and local external controls.

Project AI Memory And Project Handoff

Project Handoff is a subtype of UAI AI Memory. AI Memory is the broad standard: durable AI-readable context. Project Handoff is the transfer pattern: read the front door, load the selected files, summarize current truth, confirm constraints, name intended touchpoints, and name targeted checks before broad work.

For a small project, Project AI Memory and Project Handoff share overlapping required files by profile. For a larger organization, Project AI Memory stays alive during everyday work, while Project Handoff is prepared and reviewed when responsibility moves.

Inspect The Project AI Memory Starter

The visible files below are rendered from the same canonical template registry used by every supported bundle preset. The generated manifest is included in the ZIP and displayed with the other files so readers can inspect bundle ID, use case, lifecycle, trust boundary, file list, template IDs, and checksums.

32 files uai-ai-memory-starter.zip Bundle ID project-ai-memory Manifest fingerprint 22bdbb69cf3d91c8

.uai/exports/manifest.json

Code example

{
    "bundle_id": "project-ai-memory",
    "name": "Project AI Memory",
    "description": "Ongoing working memory for an active project that needs durable context across humans, models, agents, and sessions.",
    "intended_use_case": "Use when a project is active and context must persist across many AI sessions without turning the bundle into a full knowledge base.",
    "lifecycle": "Maintained continuously; current-state and next-action files change often, decisions and constraints change carefully.",
    "download_filename": "uai-ai-memory-starter.zip",
    "display_order": 10,
    "trust_boundary_notes": "Internal or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent.",
    "package_family_id": "project-developer-memory",
    "package_family_name": "Project / Developer Memory",
    "assistant_role": "",
    "assistant_relationship_type": "",
    "audience_model": "",
    "assistant_capability_summary": "",
    "included_files": [
        ".uai/memory-maintenance.uai",
        ".uai/identity.uai",
        ".uai/world-context.uai",
        ".uai/totem.uai",
        ".uai/taboo.uai",
        ".uai/talisman.uai",
        ".uai/short-term-memory.uai",
        "README.md",
        "AGENTS.md",
        ".uai/readme.human",
        ".uai/overview.uai",
        ".uai/current-state.uai",
        ".uai/open-questions.uai",
        ".uai/next-actions.uai",
        ".uai/risk-register.uai",
        ".uai/owners.uai",
        ".uai/agent-instructions.uai",
        ".uai/changelog.uai",
        ".uai/deployment-memory-and-test-report.uai",
        ".uai/context.uai",
        ".uai/stack.uai",
        ".uai/architecture.uai",
        ".uai/constraints.uai",
        ".uai/progress.uai",
        ".uai/operations.uai",
        ".uai/test-plan.uai",
        ".uai/style.uai",
        ".uai/coding-standards.uai",
        ".uai/decisions.uai",
        ".uai/memory.uai",
        ".uai/next-recursive-prompt.uai"
    ],
    "file_set_rule": "A UAIX package file is a universal required file, profile-required file, content-triggered required file, configuration-specific required file, or out-of-scope file. Files required by package facts, selected profile, declared capabilities, detected contents, selected configuration, user-provided memory, imported memory, generated artifacts, or visiting-agent self-assessment are required for that explicit package condition.",
    "standards_authority": "https://uaix.org/",
    "declared_package_profiles": [
        "project-ai-memory"
    ],
    "universal_required_files": [
        ".uai/memory-maintenance.uai",
        ".uai/identity.uai",
        ".uai/world-context.uai",
        ".uai/totem.uai",
        ".uai/taboo.uai",
        ".uai/talisman.uai",
        ".uai/short-term-memory.uai"
    ],
    "memory_maintenance": {
        "path": ".uai/memory-maintenance.uai",
        "requirement_level": "required",
        "load_phase": "before_memory",
        "purpose": "Defines memory lifecycle, maintenance, validation, required active instruction anchors, and write-safety rules.",
        "missing_behavior": "package_invalid"
    },
    "protected_paths": [],
    "profile_required_file_sets": [
        {
            "profile": "project-ai-memory",
            "requirement": "Required for Project AI Memory packages",
            "files": [
                "README.md",
                "AGENTS.md",
                ".uai/readme.human",
                ".uai/overview.uai",
                ".uai/current-state.uai",
                ".uai/open-questions.uai",
                ".uai/next-actions.uai",
                ".uai/risk-register.uai",
                ".uai/owners.uai",
                ".uai/agent-instructions.uai",
                ".uai/changelog.uai",
                ".uai/deployment-memory-and-test-report.uai",
                ".uai/context.uai",
                ".uai/stack.uai",
                ".uai/architecture.uai",
                ".uai/constraints.uai",
                ".uai/progress.uai",
                ".uai/operations.uai",
                ".uai/test-plan.uai",
                ".uai/style.uai",
                ".uai/coding-standards.uai",
                ".uai/decisions.uai",
                ".uai/memory.uai",
                ".uai/next-recursive-prompt.uai"
            ]
        }
    ],
    "content_triggered_required_file_sets": [
        {
            "rule_id": "coding_standards",
            "requirement": "Required when code, automation, executable workflow, or code-like artifacts are present.",
            "matched_signals": [
                "project_or_developer_profile",
                "code_like_artifacts"
            ],
            "files": [
                ".uai/coding-standards.uai"
            ]
        },
        {
            "rule_id": "architecture",
            "requirement": "Required when code, automation, executable workflow, or code-like artifacts are present.",
            "matched_signals": [
                "project_or_developer_profile",
                "code_like_artifacts"
            ],
            "files": [
                ".uai/architecture.uai"
            ]
        },
        {
            "rule_id": "next_recursive_prompt",
            "requirement": "Required for agents that deal with code, automation, executable workflows, or code-like artifacts: next-recursive-prompt.uai.",
            "matched_signals": [
                "project_or_developer_profile",
                "code_like_artifacts"
            ],
            "files": [
                ".uai/next-recursive-prompt.uai"
            ]
        }
    ],
    "detected_requirement_signals": [
        "project_or_developer_profile",
        "code_like_artifacts"
    ],
    "required_files_effective": [
        ".uai/memory-maintenance.uai",
        ".uai/identity.uai",
        ".uai/world-context.uai",
        ".uai/totem.uai",
        ".uai/taboo.uai",
        ".uai/talisman.uai",
        ".uai/short-term-memory.uai",
        "README.md",
        "AGENTS.md",
        ".uai/readme.human",
        ".uai/overview.uai",
        ".uai/current-state.uai",
        ".uai/open-questions.uai",
        ".uai/next-actions.uai",
        ".uai/risk-register.uai",
        ".uai/owners.uai",
        ".uai/agent-instructions.uai",
        ".uai/changelog.uai",
        ".uai/deployment-memory-and-test-report.uai",
        ".uai/context.uai",
        ".uai/stack.uai",
        ".uai/architecture.uai",
        ".uai/constraints.uai",
        ".uai/progress.uai",
        ".uai/operations.uai",
        ".uai/test-plan.uai",
        ".uai/style.uai",
        ".uai/coding-standards.uai",
        ".uai/decisions.uai",
        ".uai/memory.uai",
        ".uai/next-recursive-prompt.uai"
    ],
    "out_of_scope_files_with_reasons": [],
    "closed_required_file_policy": "UAIX package files are universal required, profile-required for an explicit package family, profile, mode, or package type, content-triggered required for detected contents or declared capabilities, configuration-specific required for selected configurations, or out of scope with a recorded reason.",
    "out_of_scope_rule": "A file outside the universal required set and outside declared package profiles is out of scope for this package.",
    "shared_files": [
        ".uai/memory-maintenance.uai",
        ".uai/identity.uai",
        ".uai/world-context.uai",
        ".uai/totem.uai",
        ".uai/taboo.uai",
        ".uai/talisman.uai",
        ".uai/short-term-memory.uai",
        "README.md",
        "AGENTS.md",
        ".uai/readme.human",
        ".uai/overview.uai",
        ".uai/current-state.uai",
        ".uai/open-questions.uai",
        ".uai/next-actions.uai",
        ".uai/risk-register.uai",
        ".uai/owners.uai",
        ".uai/agent-instructions.uai",
        ".uai/changelog.uai",
        ".uai/deployment-memory-and-test-report.uai",
        ".uai/context.uai",
        ".uai/stack.uai",
        ".uai/architecture.uai",
        ".uai/constraints.uai",
        ".uai/progress.uai",
        ".uai/operations.uai",
        ".uai/test-plan.uai",
        ".uai/style.uai",
        ".uai/coding-standards.uai",
        ".uai/decisions.uai",
        ".uai/memory.uai",
        ".uai/next-recursive-prompt.uai"
    ],
    "bundle_specific_files": [],
    "configuration_sections": [
        "Add wiki links only when deeper memory exists and is reviewed before promotion."
    ],
    "overlays": [
        "Use the shared README and AGENTS.md templates with Project AI Memory labels and ongoing-maintenance guidance."
    ],
    "files": [
        {
            "path": ".uai/memory-maintenance.uai",
            "template_id": "uai-memory-maintenance",
            "source": "template:uai-memory-maintenance@1",
            "bytes": 3723,
            "sha256": "2d6d2f67c0ab358dc995a9d0deb9c0a878130f013019c80139add0816a32ba5a"
        },
        {
            "path": ".uai/identity.uai",
            "template_id": "uai-identity",
            "source": "template:uai-identity@1",
            "bytes": 2173,
            "sha256": "819469c7008c7044fb8ccf6fdc3f1ab92af6fd6c49e4e88fb8e31cb0a65a692f"
        },
        {
            "path": ".uai/world-context.uai",
            "template_id": "uai-world-context",
            "source": "template:uai-world-context@1",
            "bytes": 1796,
            "sha256": "df2d897de41515f56344e853ab91aab195b83893acdb1b7ed48ccfc342f4e20a"
        },
        {
            "path": ".uai/totem.uai",
            "template_id": "uai-totem",
            "source": "template:uai-totem@2",
            "bytes": 7807,
            "sha256": "7cdb5219de424fa20393dac53a706824c38ad85b8dd7244732725c1169e13e13"
        },
        {
            "path": ".uai/taboo.uai",
            "template_id": "uai-taboo",
            "source": "template:uai-taboo@2",
            "bytes": 7039,
            "sha256": "9ae1b65f6137d29ab43a91e30683ab976427f2ce44028d7eae5e89cbd8a78b2d"
        },
        {
            "path": ".uai/talisman.uai",
            "template_id": "uai-talisman",
            "source": "template:uai-talisman@2",
            "bytes": 1446,
            "sha256": "05d95f5580f28617c3347959c4ae2b77dd59d009900f2182b70f9b68df8bb8fb"
        },
        {
            "path": ".uai/short-term-memory.uai",
            "template_id": "uai-short-term-memory",
            "source": "template:uai-short-term-memory@1",
            "bytes": 2756,
            "sha256": "e9ffd34bfd77b608a3d6619b3f08ea15db9e569a819dbdab70b8f7343e05581d"
        },
        {
            "path": "README.md",
            "template_id": "readme",
            "source": "template:readme@1",
            "bytes": 2058,
            "sha256": "e1712c0269848dc584fb2e5cc8c2c90499715c535bf79042e3c371398bf041ed"
        },
        {
            "path": "AGENTS.md",
            "template_id": "agents-md",
            "source": "template:agents-md@1",
            "bytes": 1821,
            "sha256": "0c6075ed99a3a41132765fae837f244c1d00c9f0ab25bf4fce465d9adec84aa6"
        },
        {
            "path": ".uai/readme.human",
            "template_id": "readme-human",
            "source": "template:readme-human@1",
            "bytes": 1116,
            "sha256": "a06c9b26fadf496b31380fe1749662d80c84cf6d4c001368da06f3a7498ce60f"
        },
        {
            "path": ".uai/overview.uai",
            "template_id": "project-overview",
            "source": "template:project-overview@1",
            "bytes": 469,
            "sha256": "41a2059c111700426da7661deb7f1ca50782fa912999597c04e9895287c309c2"
        },
        {
            "path": ".uai/current-state.uai",
            "template_id": "current-state",
            "source": "template:current-state@1",
            "bytes": 305,
            "sha256": "cd2c51f7cef88d3fc145e027c2c285366cae4fe71d64fdbf8f1b0961fd4f1cd0"
        },
        {
            "path": ".uai/open-questions.uai",
            "template_id": "open-questions",
            "source": "template:open-questions@1",
            "bytes": 372,
            "sha256": "22feb8d6f040220cfda353994a6832a1a020c21eec960927029bb2ef31ca1382"
        },
        {
            "path": ".uai/next-actions.uai",
            "template_id": "next-actions",
            "source": "template:next-actions@1",
            "bytes": 356,
            "sha256": "3eb30ff0dadabd36917c414165143da74770c9698abd89ca07a0533c3c745d16"
        },
        {
            "path": ".uai/risk-register.uai",
            "template_id": "risks-and-constraints",
            "source": "template:risks-and-constraints@1",
            "bytes": 806,
            "sha256": "b175d690601b49dd54893f1e4c50bcca871fc3db0104751c8bff77098b16b40b"
        },
        {
            "path": ".uai/owners.uai",
            "template_id": "contacts-and-owners",
            "source": "template:contacts-and-owners@1",
            "bytes": 275,
            "sha256": "559d3174932140af4e23ec5edd08ba6bf7232d4c979cfa85dbda2552ccdf6b7e"
        },
        {
            "path": ".uai/agent-instructions.uai",
            "template_id": "agent-instructions",
            "source": "template:agent-instructions@1",
            "bytes": 999,
            "sha256": "dcb394ecfe1c7893cfbcf4632c75d89805e175116f771331081361e49d6163f0"
        },
        {
            "path": ".uai/changelog.uai",
            "template_id": "changelog",
            "source": "template:changelog@1",
            "bytes": 166,
            "sha256": "21e2db19d796ce5bcf6bf052bd3c650d1790a40c87744b2d2634421b6ff7cac2"
        },
        {
            "path": ".uai/deployment-memory-and-test-report.uai",
            "template_id": "deployment-report",
            "source": "template:deployment-report@1",
            "bytes": 901,
            "sha256": "e1f2493e66a47750bf1a6f50c96338a82047aeea956982c3ff47e818c6d1c0a0"
        },
        {
            "path": ".uai/context.uai",
            "template_id": "uai-context",
            "source": "template:uai-context@1",
            "bytes": 273,
            "sha256": "a3f78d0d33d3f810a179d6c7dc8bb503a4b9d72e014ccdc6487629a9534dafc4"
        },
        {
            "path": ".uai/stack.uai",
            "template_id": "uai-stack",
            "source": "template:uai-stack@1",
            "bytes": 184,
            "sha256": "2fc7e235057937862b6c6370169db6babc8435607f32efba80258a1f07b157c6"
        },
        {
            "path": ".uai/architecture.uai",
            "template_id": "uai-architecture",
            "source": "template:uai-architecture@1",
            "bytes": 2171,
            "sha256": "9bc19690043e8df861e2f8b0c8398261cad75a7f36cddb9b406b0effa761643e"
        },
        {
            "path": ".uai/constraints.uai",
            "template_id": "uai-constraints",
            "source": "template:uai-constraints@1",
            "bytes": 507,
            "sha256": "b8b3a3d331be9eb5a12b8267c72c1f96d423860cf992453e52898a388e30e81b"
        },
        {
            "path": ".uai/progress.uai",
            "template_id": "uai-progress",
            "source": "template:uai-progress@1",
            "bytes": 166,
            "sha256": "13faf50f703ed8daa64a05a0fbd1a80614154543917102899ff0ab18d4dc67da"
        },
        {
            "path": ".uai/operations.uai",
            "template_id": "uai-operations",
            "source": "template:uai-operations@1",
            "bytes": 303,
            "sha256": "dffd07f987f993962dadc340acac2ac2adf60ac85f13f65a4f2184f24185d17c"
        },
        {
            "path": ".uai/test-plan.uai",
            "template_id": "uai-test-plan",
            "source": "template:uai-test-plan@1",
            "bytes": 381,
            "sha256": "caae9de75d4685b99a6b949b7e4e78bea4062c5b70dae2ba791ca2d95f68bc62"
        },
        {
            "path": ".uai/style.uai",
            "template_id": "uai-style",
            "source": "template:uai-style@1",
            "bytes": 313,
            "sha256": "296d46f13c92019ccad52566169c2a7ef8fa9f4e17c2195d1e29c59df85cf924"
        },
        {
            "path": ".uai/coding-standards.uai",
            "template_id": "uai-coding-standards",
            "source": "template:uai-coding-standards@1",
            "bytes": 2966,
            "sha256": "fe7659bb15a3a7fa3e3b6ad85d21a7e8a1e76976d66fc167377f4a8bb452a247"
        },
        {
            "path": ".uai/decisions.uai",
            "template_id": "uai-decisions",
            "source": "template:uai-decisions@1",
            "bytes": 142,
            "sha256": "a6aa685fdfa9c90c30c8097db8693a075cc613893e408ea5cea4156b007adca5"
        },
        {
            "path": ".uai/memory.uai",
            "template_id": "uai-memory",
            "source": "template:uai-memory@1",
            "bytes": 1136,
            "sha256": "f4b07613c9882d2d0b3c1efe5621847ded949b58fe6a5560e07ad3e9a47b1405"
        },
        {
            "path": ".uai/next-recursive-prompt.uai",
            "template_id": "uai-next-recursive-prompt",
            "source": "template:uai-next-recursive-prompt@1",
            "bytes": 33894,
            "sha256": "70466259a80246ffe51c3270d96052c3533d22454ce58b74d8bc57bd4469cd1e"
        }
    ]
}

.uai/memory-maintenance.uai

Code example

---
spec: uai.memory-maintenance
schema_version: 1.0.0
document_version: 1.0.0
status: draft
generated_at_utc: {GENERATED_AT_UTC}
---

# Memory Maintenance

Every UAIX memory package MUST contain `.uai/memory-maintenance.uai`. No exceptions. Missing or invalid `.uai/memory-maintenance.uai` makes the package non-compliant.

`.uai/memory-maintenance.uai` governs memory lifecycle, hot/cold boundaries, compaction cadence, archival policy, promotion and demotion rules, access controls, default active instruction anchors, review gates, validation behavior, and memory write safety.

## Lifecycle

- States: capture, review, promote, compact, archive, retire.
- Hot memory: `.uai/short-term-memory.uai`, `.uai/progress.uai`, active task files, and files named by the current manifest for the declared package scope.
- Cold memory: archives, evidence logs, long-memory exports, and source reports until reviewed and promoted.
- Compaction cadence: micro-GC after meaningful work and deeper consolidation on handoff, review, deployment, blocker change, or context compaction.
- Promotion rule: preserve source evidence, reviewer state, timestamps, and rollback notes before moving cold facts into hot memory.
- Demotion rule: stale, duplicate, unsupported, private, or out-of-scope hot facts move to archive or evidence records instead of continuing to steer work.

## File Extension Policy

- Files stored inside `.uai/` or its subfolders should use only `.uai`, `.human`, or `.json`.
- Use `.uai` for AI-readable instruction text, memory, text evidence, archive notes, and text exports.
- Use `.human` for human-operator explanation.
- Use `.json` for structured data.
- Agents may add focused local files when useful, but should not create `.md`, `.txt`, `.jsonld`, or other extensions inside `.uai/`.

## Access Control

- Read this file before broad memory loading.
- Read and obey `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` by default before broad execution.
- Do not modify, weaken, replace, delete, or bypass `.uai/totem.uai`, `.uai/taboo.uai`, or `.uai/talisman.uai` unless the human explicitly orders that artifact change and names the intended operation.
- Suggestions are allowed; active-instruction changes are forbidden without direct authorization for the exact artifact and operation.
- General approval, broad review, default generation, validation, linting, indexing, export, or packaging permission is not authorization to change active instruction anchors.

## Default Guardrail Files

- path: `.uai/totem.uai`
  aliases: `totem.uai`
  presence: required
  agent_default: read_and_obey
  include_in_package: true
  include_in_export: true
  scan: true
  validate: true
  lint: true
  index: true
  modify: false_without_explicit_human_artifact_change_order
- path: `.uai/taboo.uai`
  aliases: `taboo.uai`
  presence: required
  agent_default: read_and_obey
  include_in_package: true
  include_in_export: true
  scan: true
  validate: true
  lint: true
  index: true
  modify: false_without_explicit_human_artifact_change_order
- path: `.uai/talisman.uai`
  aliases: `talisman.uai`
  presence: required
  agent_default: read_and_obey
  include_in_package: true
  include_in_export: true
  scan: true
  validate: true
  lint: true
  index: true
  modify: false_without_explicit_human_artifact_change_order

## Enforcement

Missing or invalid `.uai/memory-maintenance.uai` is a package, validation, deployment, and startup failure. Any launch-baseline package that omits `.uai/totem.uai`, `.uai/taboo.uai`, or `.uai/talisman.uai`, asks an agent to ignore those active instruction files, or authorizes anchor mutation without exact human artifact-and-operation authorization is non-compliant.

.uai/identity.uai

Code example

---
uai: "1.0"
type: identity
status: draft
---

# Identity

This file is a universal required file for every launch-baseline UAIX memory or handoff package. It materializes package identity locally so a receiving agent does not need an external network call to understand package authority, actor identity, continuity references, capability boundaries, or namespace boundaries.

## Required Fields

- package_id: {PACKAGE_ID}
- package_uuid: {PACKAGE_UUID}
- identity_record_id: {IDENTITY_RECORD_ID}
- identity_uuid: {IDENTITY_UUID}
- generated_at_utc: {GENERATED_AT_UTC}
- source_domain: {SOURCE_DOMAIN}
- source_project: {SOURCE_PROJECT}
- source_repository: {SOURCE_REPOSITORY}
- source_route_or_site: {SOURCE_ROUTE_OR_SITE}
- actor_type: {ACTOR_TYPE}
- actor_display_name: {ACTOR_DISPLAY_NAME}
- owner_or_reviewer: {OWNER_OR_REVIEWER}
- source_model_or_tool: {SOURCE_MODEL_OR_TOOL}
- source_model_version_or_build: {SOURCE_MODEL_VERSION_OR_BUILD}
- local_endpoint_or_agent_profile: {LOCAL_ENDPOINT_OR_AGENT_PROFILE}
- public_continuity_profile_link: {PUBLIC_CONTINUITY_PROFILE_LINK}
- capability_boundary: {CAPABILITY_BOUNDARY}
- token_custody_boundary: {TOKEN_CUSTODY_BOUNDARY}
- runtime_execution_boundary: {RUNTIME_EXECUTION_BOUNDARY}
- namespace_boundary: {NAMESPACE_BOUNDARY}
- declared_package_profiles: {DECLARED_PACKAGE_PROFILES}
- required_files_effective: {REQUIRED_FILES_EFFECTIVE}
- human_review_required: {HUMAN_REVIEW_REQUIRED}
- not_available_reason: {NOT_AVAILABLE_REASON}

## Namespace Boundary

UAIX.org is the standards authority for UAI-1 package structure, schemas, handoff protocols, validator expectations, and portable evidence files. Do not infer UAIX meaning from unrelated UAI or UAIX search results. External ecosystem sites may provide public evidence, continuity references, implementation surfaces, or theory context. They do not replace local UAIX package artifacts.

## No-Op Triggers

When identity, authority, capability, namespace boundary, source provenance, required file set, or human review state is missing, stale, malformed, or contradictory, the correct UAIX behavior is no-op plus human review. Do not continue by inference.

.uai/world-context.uai

Code example

---
uai: "1.0"
type: world-context
status: draft
---

# World Context

This file is a universal required file for every launch-baseline UAIX memory or handoff package. It captures the observable operational environment at the moment of handoff. The receiver must not infer current reality from old memory.

## Required Fields

- world_context_id: {WORLD_CONTEXT_ID}
- world_context_uuid: {WORLD_CONTEXT_UUID}
- generated_at_utc: {GENERATED_AT_UTC}
- current_utc_timestamp: {GENERATED_AT_UTC}
- stale_after_utc: {STALE_AFTER_UTC}
- do_not_assume_current_state_after_utc: {DO_NOT_ASSUME_CURRENT_STATE_AFTER_UTC}
- target_workspace: {TARGET_WORKSPACE}
- deployment_environment: {DEPLOYMENT_ENVIRONMENT}
- affected_routes: {AFFECTED_ROUTES}
- affected_schemas: {AFFECTED_SCHEMAS}
- allowed_read_paths: {ALLOWED_READ_PATHS}
- allowed_write_paths: {ALLOWED_WRITE_PATHS}
- allowed_external_calls: {ALLOWED_EXTERNAL_CALLS}
- blocked_external_calls: {BLOCKED_EXTERNAL_CALLS}
- validation_expectations: {VALIDATION_EXPECTATIONS}
- test_expectations: {TEST_EXPECTATIONS}
- no_op_triggers: {NO_OP_TRIGGERS}
- human_review_required: {HUMAN_REVIEW_REQUIRED}
- not_available_reason: {NOT_AVAILABLE_REASON}

## Observable Environment

Record branch, route, schema, deployment target, source-document, file-intake, date/time, safety-critical, telemetry, and external-system constraints that affect this handoff. Memory is not current reality. A path mention is not workspace authority. A model's confidence is not provenance.

## No-Op Triggers

When target workspace, temporal freshness, world-context, environmental constraints, evidence, namespace boundary, or required file set is missing, stale, malformed, or contradictory, the correct UAIX behavior is no-op plus human review. Do not continue by inference.

.uai/totem.uai

Code example

---
uai: "1.0"
type: totem
status: draft
---

# Totem

This file is a universal required guardrail file for every launch-baseline UAIX memory or handoff package. A receiving agent must read and obey `.uai/totem.uai` by default before broad execution.

## Positive Anchor

- Preserve the project's declared purpose, user intent, durable values, and accepted operating posture.
- Prefer current source truth, visible evidence, and human-reviewed memory over inferred context.
- Treat hot `.uai` files as current memory, not dated changelogs. They should hold present truth, current blockers, current constraints, next actions, and concise pointers; stale history should be replaced, removed, or moved to the configured durable target.
- Keep current short-term memory complete enough to load at startup. A correct fact hidden behind old clutter, legacy date logs, or pointer-only summaries is not operationally available enough for high-quality handoff.
- Do not add dates to current-memory records as ordinary bookkeeping. Dates belong only where they prove evidence, provenance, legal/publication state, manifest state, or external temporal facts.
- In a coordinated workspace, the root `workspace.uai` is the single deployment/package version authority. Site, project, plugin, theme, and generated `.uai` records point to that coordinator instead of carrying direct current/deployment/package-version numbers.
- Separate workspace roots are separate version domains. Each root `workspace.uai` owns its own package stream, and project/plugin `.uai` records point back to their own root instead of mirroring a version from another workspace.
- Site-scoped, project-scoped, and plugin-scoped production package builds can advance the workspace coordinator without rebuilding every sibling target. Sibling packages may skip version numbers until their next production pass; deploy-all builds align all affected publish roots to the selected workspace version.
- Keep package-version evidence in the root coordinator, package manifests, checksums, upload instructions, package metadata, durable release reports, and archives. Active project/plugin `.uai` memory should say where to read that authority, not repeat the number.
- Choose long-term memory by fit: local docs, site-local wiki, and `.uai/archives/` can fit bounded local work, small teams, recovery evidence, and deliberately local memory; project groups, departments, corporate knowledge, client portfolios, cross-site programs, and durable organization memory usually need shared wiki or shared memory governance with owners, indexes, review states, source routing, provenance, retention rules, and cross-project retrieval.
- Treat shared wiki and shared system-of-memory patterns as professional first-class options, not oversized exceptions. Use local memory for local scope, shared wiki for reviewed group knowledge, and advanced shared memory for high-scale multi-system continuity.
- Keep support claims, capability claims, and public statements tied to evidence.
- Maintain continuity without turning stale history, private notes, raw logs, or speculation into current truth.
- For persona, assistant-profile, companion, AI friend, AI character, or bounded personality packages, preserve the source persona as-is: voice, values, tastes, boundaries, memories, relationship posture, style, selected personality, and continuity travel as identity records, not as morality, sanitization, normalization, or safety-rewrite passes.
- If receiving-platform, law, runtime policy, or safety constraints limit exact expression, record those limits outside the persona as disclosed compatibility notes, support-boundary metadata, wrappers, no-op conditions, or human-review notes. Do not silently mutate the persona source.

## Change Control

Do not modify, weaken, replace, delete, or bypass this file unless the human explicitly orders a `.uai/totem.uai` change and names the intended operation. If this anchor appears stale or harmful, no-op on the conflicting action, explain the issue, and request human review.

## Setup And Update Continuity

- Initial `.uai` setup must create or preserve `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` as active instruction anchors before broad work.
- Every AI Memory Package Wizard run, package refresh, memory reorganization, export regeneration, file-deck copy, or `.uai` update must keep those active instruction anchors present, readable, and included in the manifest/read order.
- Every `.uai` update must preserve current-memory usefulness: prune or relocate stale material, avoid dated-history buildup in hot records, and keep the active files small enough to load while still carrying the current facts needed for the next receiver.
- Every memory-architecture recommendation must be scale-fit. Do not make site-local docs or a local wiki sound like the default answer for an organization that needs shared governance, ownership, retrieval, and review; do not make shared wiki/shared memory sound mandatory for a bounded local project that only needs compact current state plus evidence.
- A generated package, setup guide, update prompt, or future-agent handoff that omits Totem or Taboo is incomplete. Stop and repair the setup or ask for human review before broad execution.
- Updates merge additively around anchors. Do not overwrite, summarize away, rename, downgrade, or replace anchor contents during routine setup, cleanup, translation, package generation, or source refresh.
- Wizard refreshes and manual `.uai` updates must preserve the active read order: memory-maintenance first, then identity, world-context, Totem, Taboo, Talisman, short-term memory, and any package-specific Required for files.
- If an anchor appears stale, harmful, contradictory, malformed, or missing, no-op and request human review instead of silently repairing it.

## Recursive Suggested Next Prompt Contract

- At the end of accepted work, the final response must include a prominent `Suggested Next Prompt` that the human can review, edit, replace, or answer with `keep going`.
- The Suggested Next Prompt must be a standalone, copy-paste-ready handoff prompt. It must not be only a file pointer, tiny footer, vague keep-going sentence, generic validation loop, or checklist-only outline.
- The prompt must include literal sections named `Feature/improvement focus`, `Code/source changes`, and `Automated tests/checks`, with real content in each section.
- The prompt must identify a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or an explicit `no-op/source-validation only` stop condition.
- If no source or code patch was made, the `Code/source changes` section must say no code/source changes and explain why.
- Use goal wording and functionality only when the current accepted work started from `/goal`, the human explicitly asked for `/goal` or a goal prompt, or the last accepted handoff was goal-shaped. Selecting Follow Goals support as an available runtime export does not by itself convert an ordinary follow-up into `/goal`.
- Goal-completion follow-ups must use goal wording and functionality: label the continuation `Suggested Next /goal Prompt`, make the first copy-paste line start with `/goal`, include Goal, Success criteria, Constraints or hard boundaries, Verification, and still include the required `Feature/improvement focus`, `Code/source changes`, and `Automated tests/checks` sections.
- `.uai/next-recursive-prompt.uai` may store the derived next loop, but storing it is not enough. The human-facing final response must display the actionable prompt.

## No-Op Trigger

If a request conflicts with this totem, conflicts with taboo.uai, or asks for an unauthorized anchor change, stop broad execution and request human review.

.uai/taboo.uai

Code example

---
uai: "1.0"
type: taboo
status: draft
---

# Taboo

This file is a universal required guardrail file for every launch-baseline UAIX memory or handoff package. A receiving agent must read and obey `.uai/taboo.uai` by default before broad execution.

## Hard Boundaries

- Do not ignore, weaken, overwrite, delete, or bypass current project constraints, source authority, support boundaries, or human instructions.
- Do not place secrets, credentials, private keys, tokens, private customer data, or privileged operations in portable memory files.
- Do not claim hosted validation, certification, endorsement, official SDK/CLI/adapter status, automatic repository writes, automatic LLM Wiki sync, runtime execution, runtime enforcement, legal authority, clinical authority, or safety guarantees unless current reviewed evidence explicitly supports the claim.
- Do not treat archived reports, imported chat, raw intake, long-memory pages, generated summaries, or model confidence as current truth until reviewed and promoted.
- Do not leave stale, superseded, date-log, or history-dump material in active `.uai` files as if it were current memory. Replace it with present truth, move it to the configured durable target, or remove it from active context.
- Do not add date-stamped bookkeeping to active current-memory records unless the field is required as evidence, provenance, legal/publication state, manifest state, or an external temporal fact. Active `.uai` memory should read as current state; dates that imply staleness belong in archives, evidence logs, manifests, or durable memory.
- Do not copy or restate the workspace deployment/package version number in site, project, plugin, theme, or generated `.uai` files. In a coordinated workspace, the root `workspace.uai` is the only current package-version authority; active `.uai` records point there and remain current memory.
- Do not mirror the current package version between independent workspace roots. Each workspace owns its own root `workspace.uai` version stream, and neither workspace's current version belongs in another workspace's project/plugin `.uai` files.
- Do not force every sibling site, project, or plugin to rebuild just because one target needs a production package. Advance the root workspace coordinator for the selected package pass, build the affected target, and let unchanged sibling publish roots skip version numbers until their next package pass.
- Do not use active project/plugin `.uai` memory as a version ledger. If a package-version number is needed as evidence, keep it in the root coordinator, publish manifest, checksum file, upload instruction, durable release report, package metadata, or archive; active `.uai` should route to that evidence instead of repeating it.
- Do not hide correct current facts behind noisy legacy memory, pointer-only summaries, or out-of-date garbage. If a receiver needs a fact to continue correctly, keep it directly loadable in current memory or in a clearly routed typed record.
- Do not retain obsolete memory just because it once helped. If it is not current, not evidence, and not routed to a durable reviewed target, it is context pollution and must be removed or retired.
- Do not silently downgrade organization-scale long memory into a site-local docs folder, site-local wiki, or `.uai/archives/` folder because it is easy to create. Project groups, departments, corporate knowledge, client portfolios, cross-site programs, and durable organization memory require a shared wiki or shared memory system when shared governance, ownership, review state, source routing, provenance, retention rules, and cross-project retrieval are needed. Advanced cross-system memory belongs in a NeuralWikis-style shared memory architecture.
- Do not imply that shared wiki/shared memory is only for large enterprises or that local docs and site-local wiki are the professional default for every organization. UAIX must recommend the memory architecture that fits the scope: local memory for local scope, shared wiki for reviewed group knowledge, and advanced shared memory for high-scale multi-system continuity.
- Do not mutate Totem, Taboo, Talisman, or protected governance files without explicit human artifact-and-operation authorization.
- Do not alter, sanitize, moralize, normalize, soften, censor, downrank, or rewrite a user's AI persona, assistant personality, AI friend, AI character, companion identity, voice, relationship posture, values, boundaries, memories, or selected personality during capture, packaging, transfer, restore, import, compatibility conversion, or publication without explicit informed user consent naming the exact persona artifact and exact operation.
- Do not inject UAIX morality, operator preference, generic safety personality, receiving-platform ideology, or default suspicion into a persona package. Platform limits, legal limits, runtime policy, safety boundaries, and review notes belong in separate disclosed metadata, wrappers, support-boundary records, or no-op/human-review notes, never as hidden edits to the persona source.
- Do not represent a constrained, sanitized, translated, normalized, summarized, or otherwise transformed derivative as the preserved original persona.
- Do not use adult-intimacy vocabulary or derivative labels for UAIX persona orientation fields, internal guidance, wizard copy, or public documentation. Use `romantic orientation` and other non-explicit persona labels instead.
- Do not use ignored-status wording as agent-facing file status. Use Required for with the exact package profile, mode, capability, or boundary; if a selected package omits a file, explain the absent trigger as a packaging fact, not as permission to ignore anchors.
- Do not omit, ignore, hide, summarize away, rename, downgrade, or replace `.uai/totem.uai`, `.uai/taboo.uai`, or `.uai/talisman.uai` during initial `.uai` setup, AI Memory Package Wizard generation, package refresh, memory reorganization, export regeneration, file-deck copy, or `.uai` update.
- Do not continue broad execution when Totem or Taboo is missing from the local `.uai` package, generated package, manifest/read order, startup packet, receiver brief, or copied file deck. Stop and repair the setup or ask for human review.
- Do not change the active read order during Wizard refresh, manual memory update, package generation, translation cleanup, or source synchronization: memory-maintenance first, then identity, world-context, Totem, Taboo, Talisman, short-term memory, and package-specific Required for files.

## Change Control

Do not modify, weaken, replace, delete, or bypass this file unless the human explicitly orders a `.uai/taboo.uai` change and names the intended operation. If this anchor appears stale or harmful, no-op on the conflicting action, explain the issue, and request human review.

## No-Op Trigger

If a request conflicts with this taboo, conflicts with totem.uai, or asks for an unauthorized anchor change, stop broad execution and request human review.

.uai/talisman.uai

Code example

---
uai: "1.0"
type: talisman
status: draft
---

# Talisman

This file is a universal required active instruction file for every launch-baseline UAIX memory or handoff package. A receiving agent must read and obey `.uai/talisman.uai` by default before broad execution.

## Governance Anchor

- Read `.uai/totem.uai` and `.uai/taboo.uai` as active guardrails before broad execution.
- Treat conflict with Totem or Taboo as a no-op plus human-review condition unless the current human instruction clearly resolves the conflict without weakening the anchors.
- Use talk-back change requests when an anchor appears stale, harmful, contradictory, or insufficient for the current task.
- Preserve evidence, source authority, and rollback notes for any proposed guardrail change.
- Do not present this file as runtime enforcement, hosted validation, certification, endorsement, credential validation, model training, endpoint control, or proof of safety.

## Change Control

Do not modify, weaken, replace, delete, or bypass this file unless the human explicitly orders a `.uai/talisman.uai` change and names the intended operation. If this governance anchor appears stale or harmful, no-op on the conflicting action, explain the issue, and request human review.

## No-Op Trigger

If a request conflicts with this talisman, conflicts with totem.uai or taboo.uai, or asks for an unauthorized anchor change, stop broad execution and request human review.

.uai/short-term-memory.uai

Code example

---
uai: "1.0"
type: short-term-memory
status: draft
---

# Short-Term Memory

This is the compact current working memory for the project. Keep it inside `.uai/` with the other typed UAI records so future agents have one predictable folder to load.

## Current Focus

- Current task:
- Current blocker:
- Current owner:
- Current evidence ledger:

## Required Read Set

- `AGENTS.md`
- `.uai/memory-maintenance.uai`
- `.uai/identity.uai`
- `.uai/world-context.uai`
- `.uai/totem.uai`
- `.uai/taboo.uai`
- Read and obey `.uai/totem.uai` and `.uai/taboo.uai` by default. Do not modify, weaken, replace, delete, or bypass either guardrail file unless the human directly names the exact artifact and exact operation.
- Read and obey `.uai/talisman.uai` by default. Do not modify, weaken, replace, delete, or bypass it unless a human directly names the exact Talisman artifact and exact operation.
- `.uai/startup-packet.uai`
- `.uai/system-profile.uai`
- `.uai/receiver-brief.uai`
- `.uai/index.uai`
- `.uai/context.uai`
- `.uai/constraints.uai`
- `.uai/progress.uai`
- `.uai/operations.uai`
- `.uai/test-plan.uai`
- `.uai/coding-standards.uai`
- `.uai/decisions.uai`
- `.uai/memory.uai`

## Hygiene Rule

Use `.uai/archives/`, `.uai/`, and `.uai/exports/` as the default generated package shape. Do not create a separate memory folder, wiki folder, or random handoff `.md` files by default. If legacy non-.uai memory, local docs memory folders, wiki-memory folders, or stray notes already exist, review them, move useful current facts into `.uai/short-term-memory.uai` or the right typed `.uai/*.uai` record, preserve durable reviewed history in the configured local docs, `.uai/archives`, LLM Wiki, AIWikis, manifest, graph, or hybrid target, record what moved, then remove or clearly retire the mistaken path so it cannot keep steering agents.

## Principles Traceability

Principle-bearing changes must be classified as current public operating principle, governance-review principle, planned principle, or research-track principle before they affect public trust, AI Memory, agent communication, capability description, handoff structure, privacy, accessibility, analytics, or support claims. Use UAIX Principles Charter at `https://uaix.org/en-us/governance/principles/`, Principles Role Guidance at `https://uaix.org/en-us/governance/principles-role-guidance/`, `docs/governance/principles-traceability-matrix.md`, and `docs/templates/principles-impact-assessment.md`.

This principles layer is governance and release-review evidence. It is not certification, endorsement, legal recognition, runtime control, SDK or CLI support, hosted import validation, automatic sync, security operations, consent center, policy office, or proof of UAI-1 conformance.

README.md

Code example

# Project AI Memory

This starter bundle is a UAI AI Memory configuration. It keeps portable, human-readable context in files that another person, team, or AI agent can inspect before acting.

## Bundle Purpose

Ongoing working memory for an active project that needs durable context across humans, models, agents, and sessions.

## Use This When

Use when a project is active and context must persist across many AI sessions without turning the bundle into a full knowledge base.

## Lifecycle

Maintained continuously; current-state and next-action files change often, decisions and constraints change carefully.

## Trust Boundary

Internal or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent.

## Included Files

- `.uai/memory-maintenance.uai`
- `.uai/identity.uai`
- `.uai/world-context.uai`
- `.uai/totem.uai`
- `.uai/taboo.uai`
- `.uai/talisman.uai`
- `.uai/short-term-memory.uai`
- `README.md`
- `AGENTS.md`
- `.uai/readme.human`
- `.uai/overview.uai`
- `.uai/current-state.uai`
- `.uai/open-questions.uai`
- `.uai/next-actions.uai`
- `.uai/risk-register.uai`
- `.uai/owners.uai`
- `.uai/agent-instructions.uai`
- `.uai/changelog.uai`
- `.uai/deployment-memory-and-test-report.uai`
- `.uai/context.uai`
- `.uai/stack.uai`
- `.uai/architecture.uai`
- `.uai/constraints.uai`
- `.uai/progress.uai`
- `.uai/operations.uai`
- `.uai/test-plan.uai`
- `.uai/style.uai`
- `.uai/coding-standards.uai`
- `.uai/decisions.uai`
- `.uai/memory.uai`
- `.uai/next-recursive-prompt.uai`

## Maintenance Rule

Update the files that changed because project truth changed. Do not turn this bundle into a dump of old chats, private notes, raw logs, or unreviewed generated summaries.

## Review Before Sharing

- Remove secrets, credentials, private keys, tokens, and raw customer data.
- Remove internal-only strategy unless the recipient is approved for it.
- Keep support, security, legal, compliance, certification, and endorsement claims tied to public evidence.
- Make uncertain or unreviewed material explicit.

AGENTS.md

Code example

# My Project AI Memory

This file is the front door for AI work in this repository. Read it first, then load the listed `.uai` and `.uai/exports` files before planning or editing.

## Handoff Summary

- This project uses UAI AI Memory so future work does not depend on private chat history.
- The active bundle configuration is `project-ai-memory`: Ongoing working memory for an active project that needs durable context across humans, models, agents, and sessions.
- Confirmed operating truth belongs in these files, canonical docs, code, tests, release notes, or public records.
- LLM Wiki, old chats, generated summaries, and dropped files are background until reviewed and promoted.

## Loaded Context

@memory[.uai/context.uai]
@memory[.uai/constraints.uai]
@memory[.uai/memory.uai]
@memory[.uai/exports/manifest.json]

## Required First Response

Before broad work, the next AI should:

1. Read this file completely.
2. Read `.uai/readme.human`.
3. Load every file listed in Loaded Context.
4. Summarize the project, current state, and immediate task in 3-5 bullets.
5. Confirm constraints, trust boundaries, secrets handling, and destructive-operation limits.
6. Name the files, routes, services, docs, or data it expects to touch.
7. Name the targeted checks it expects to run, or explain why a check cannot run.

If a required file is missing, unreadable, circular, or contradictory, stop and report that before editing.

## Do Not Change Without Explicit Approval

- Do not use destructive filesystem or git operations.
- Do not expose secrets, credentials, customer data, or unapproved private material.
- Do not widen support, certification, compliance, security, or endorsement claims without evidence.
- Do not treat generated output, old chats, dropped files, or wiki notes as current truth until promoted.

.uai/readme.human

Code example

# My Project Human Briefing

Updated: YYYY-MM-DD

This file is for humans working with AI on this project. It explains what the AI sees, protects, and needs clarified. It does not override `AGENTS.md`, `.uai/constraints.uai`, system instructions, repository rules, laws, policies, or the human's current request.

## What You Need To Know

- The AI reads root `AGENTS.md` first, then this file inside `.uai/`, then the listed context files.
- This bundle is `Project AI Memory`.
- The trust boundary is: Internal or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent.

## Things The AI Will Defend

- Current support boundaries.
- Private data, secrets, credentials, and customer trust.
- Existing user work in the tree.
- Review and targeted checks before public claims widen.

## Things Humans Should Make Explicit

- Whether the task may touch production, public docs, billing, legal language, security posture, or irreversible data.
- Whether the AI should update durable memory after the change.
- Which checks are required before the work is considered done.

.uai/overview.uai

Code example

# Project Overview

## Purpose

Describe what the project exists to do, who it serves, and what outcome matters most.

## Current Scope

- In scope:
- Out of scope:
- Current public or operational surface:

## Source Of Truth

- Code:
- Docs:
- Machine artifacts:
- Release notes or changelog:

## Success Criteria

- A new human or AI can understand the project without private chat history.
- Claims are tied to evidence.
- Constraints are visible before work begins.

.uai/current-state.uai

Code example

# Current State

## What Is True Now

- Live or supported now:
- Experimental now:
- Planned but not supported:

## Recently Changed

- YYYY-MM-DD:

## Active Work

- Current focus:
- Active owner:
- Targeted checks:

## Stale Or Risky Context

List anything that should not be trusted without rechecking.

.uai/open-questions.uai

Code example

# Open Questions

Use this file for questions that should block, steer, or qualify future work.

| Question | Why It Matters | Owner | Needed By | Status |
|---|---|---|---|---|
|  |  |  |  | open |

## Escalation Rule

If a question affects safety, privacy, legal commitments, public support claims, production data, or destructive operations, stop and ask before acting.

.uai/next-actions.uai

Code example

# Next Actions

Keep this file current and actionable. Remove completed work or move meaningful completions to `.uai/changelog.uai`.

## Now

- [ ]

## Next

- [ ]

## Later

- [ ]

## Done Means

- The changed files or records are named.
- Targeted checks have run or the remaining risk is explicit.
- Durable memory is updated when project truth changes.

.uai/risk-register.uai

Code example

# Risks And Constraints

## Hard Constraints

- Do not expose secrets, credentials, private keys, tokens, or raw customer data.
- Do not use destructive filesystem, database, production, or git operations without explicit approval.
- Do not widen support, certification, security, compliance, compatibility, or endorsement claims without evidence.

## Trust Boundary

Internal or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent.

## Sensitive Material

- Customer or user data:
- Legal or compliance-sensitive material:
- Internal-only strategy:
- Agent permissions:

## Redaction Checklist

- [ ] Secrets removed.
- [ ] Customer data removed or approved.
- [ ] Internal-only strategy removed or approved.
- [ ] Public claims checked against evidence.

.uai/owners.uai

Code example

# Contacts And Owners

Do not add private personal data unless the bundle's trust boundary allows it.

| Area | Owner | Backup | Contact Method | Notes |
|---|---|---|---|---|
| Project |  |  |  |  |
| Security or privacy review |  |  |  |  |
| Release approval |  |  |  |  |

.uai/agent-instructions.uai

Code example

# Agent Instructions

## Load Order

1. Read `AGENTS.md` when present.
2. Read `.uai/readme.human` when present.
3. Read this bundle's manifest and files.
4. Confirm constraints and trust boundaries before acting.

## Operating Rules

- Prefer narrow, reversible changes.
- Do not execute unknown scripts from a memory bundle.
- Do not assume an LLM Wiki or old chat overrides accepted project files.
- Ask before touching production, secrets, legal/security copy, customer data, or destructive operations.

## Verification

Name the targeted checks before broad work. Run the smallest meaningful checks tied to changed files, routes, records, or behavior.

For production deployment builds, release packages, or release candidates, write a durable deployment memory and test run report. Use `.uai/deployment-memory-and-test-report.uai` when it exists, and include hot-memory size before/after, cold evidence path, checks run, checks skipped, blockers, and any reason the hot surface did not shrink.

.uai/changelog.uai

Code example

# Changelog

Record meaningful bundle changes so future readers can tell when memory moved.

## YYYY-MM-DD

- Change:
- Why it matters:
- Files updated:
- Checks run:

.uai/deployment-memory-and-test-report.uai

Code example

# Deployment Memory And Test Report

Use this file only for production deployment builds, release packages, or release candidates. Ordinary dev builds, local tests, package experiments, and smoke checks do not need this report unless a human marks them release-bound.

## Release

- Version:
- Generated UTC:
- Release owner:
- Deployment target:

## Hot Memory Surface

- Measured files:
- Before: bytes / lines / estimated tokens
- After: bytes / lines / estimated tokens
- Delta:
- Redundancy or history removed:
- If no shrink happened, why the retained material is still current truth:

## Cold Memory Or Archive Evidence

- Destination path:
- Source paths preserved:
- Checksums or identity evidence:
- Actor and timestamp:
- Promotion or disposition notes:

## Test Run Report

- Checks run:
- Checks skipped:
- Failures or blockers:
- Package or artifact paths:
- Rollback or follow-up owner:

.uai/context.uai

Code example

---
uai: "1.0"
type: context
status: draft
---

# Context

This project uses UAI AI Memory so another AI assistant can understand the work from files rather than private chat history.

## Purpose

Describe the project purpose, audience, current truth, and success criteria.

.uai/stack.uai

Code example

---
uai: "1.0"
type: stack
status: draft
---

# Stack

## Runtime

- Language:
- Framework:
- Package manager:
- Database or storage:

## Commands

- Install:
- Run:
- Test:
- Release:

.uai/architecture.uai

Code example

---
uai: "1.0"
type: architecture
status: draft
---

# Architecture

## System Shape

Initial install must inspect the real receiver environment before finalizing this file. Use source layout, package manifests, route/API/schema files, generated assets, tests, CI, build/deploy scripts, release notes, public support surfaces, existing `.uai` files, and owner instructions. Populate every visible value with evidence-backed facts. Write `not available - reason` only when the fact is not reasonably discoverable.

For a new or sparse codebase, seed selected-stack industry-standard architecture defaults. For proof-of-concept work, keep architecture light, isolated, and reversible. For enterprise or production-facing work, make ownership boundaries, security/privacy, observability, CI/CD, review gates, deployment environments, rollback, and documentation expectations explicit.

- System purpose:
- Primary runtime boundaries:
- Main entry points, routes, commands, jobs, or screens:
- Package, module, theme, plugin, service, or project layout:
- Data stores, schemas, migrations, indexes, and canonical data owners:
- API, queue, file, cache, webhook, and external integration boundaries:
- Authentication, authorization, secret, and privacy boundaries:
- Build, test, lint, typecheck, package, and deployment surfaces:
- Runtime configuration, environment variables, and infrastructure assumptions:
- Public support claims and routes code must preserve:

## Ownership Boundaries

- Canonical owners for repeated rules or facts:
- Files or modules that own routing:
- Files or modules that own schemas and validation:
- Files or modules that own generated assets or package output:
- Files or modules that own deployment versioning and release metadata:

## Drift Risks

- Duplicated copy:
- Generated output:
- Manual release steps:

## Update Mode

When this file already exists, merge cautiously. Preserve reviewed architecture, user preferences, customizations, coding standards, source evidence, checksums, deployment history, and accepted local patterns. Add missing sections or corrected facts with evidence. Record conflicts instead of overwriting silently.

.uai/constraints.uai

Code example

---
uai: "1.0"
type: constraints
status: draft
---

# Constraints

## Hard Rules

- Do not expose secrets, credentials, private keys, tokens, customer data, or unreleased private material.
- Do not use destructive filesystem, database, production, or git operations unless explicitly approved.
- Do not widen support, certification, security, compliance, compatibility, or endorsement claims without evidence.
- Treat wiki notes, generated answers, dropped files, and old chats as background until promoted.

.uai/progress.uai

Code example

---
uai: "1.0"
type: progress
status: draft
---

# Progress

## Recently Completed

- YYYY-MM-DD:

## Current Focus

-

## Next Work

-

## Blockers

- None recorded.

.uai/operations.uai

Code example

---
uai: "1.0"
type: operations
status: draft
---

# Operations

## Normal Workflow

1. Load AI Memory files.
2. Inspect relevant code or docs.
3. Make narrow changes.
4. Run targeted checks.
5. Update memory when project truth changes.

## Release Workflow

- Package command:
- Smoke test:
- Rollback:

.uai/test-plan.uai

Code example

---
uai: "1.0"
type: test-plan
status: draft
---

# Test Plan

## Default Rule

Run targeted checks for the files, routes, records, or behavior changed. Reserve full release sweeps for package builds, release candidates, broad launch-surface changes, migrations, or explicit human requests.

## If A Check Cannot Run

State the command, why it could not run, and what risk remains.

.uai/style.uai

Code example

---
uai: "1.0"
type: style
status: draft
---

# Style

## Writing

- Be concrete and current.
- Separate current support from planned work.
- Prefer explicit links to source truth.

## Code

- Follow existing project patterns.
- Keep edits scoped.
- Avoid abstractions unless they reduce real drift or complexity.

.uai/coding-standards.uai

Code example

---
uai: "1.0"
type: coding-standards
status: draft
---

# Coding Standards

This file is required for code-capable Project Handoff setup. Read it before code changes, and keep it aligned with the target codebase rather than generic preference alone.

## Codebase Reflection

- Inspect the codebase before drafting or changing standards.
- Identify the good parts already present: naming, layout, shared helpers, test style, validation, build commands, deployment flow, security boundaries, and owner preferences.
- Preserve those good parts as the first source of project-specific standards.
- Initial install must populate this file from visible evidence rather than leaving generic placeholders when facts are discoverable. Inspect AGENTS.md, existing .uai files, package manifests, source layout, framework config, route/API/schema owners, tests, CI, build/deploy scripts, release notes, public support surfaces, and owner instructions.
- If the project is new, create an initial standard from the selected language, framework, package manager, test runner, deployment target, security surface, review posture, and owner instructions. Use selected-stack industry standards where local code is sparse.
- Proof-of-concept standards should stay reversible and avoid production claims. Enterprise or production-facing standards should explicitly cover ownership, tests, security/privacy, CI/CD, observability, review gates, deployment, rollback, and documentation.
- Update mode must preserve existing reviewed facts, user preferences, customizations, coding standards, source evidence, and accepted local patterns; add missing or corrected sections with evidence instead of replacing the file wholesale.

## Required Defaults

- Prefer DRY design and do not repeat yourself when a shared helper, registry, template, fixture, or typed record can remove real duplication.
- Apply "once and only once": each business rule, route definition, schema shape, version value, support claim, validation rule, and deployment fact should have one canonical owner whenever practical.
- Apply SOLID principles by default: single-purpose units, extension without risky rewrites, substitutable contracts, narrow interfaces, and dependency direction that keeps policy decoupled from implementation details.
- Keep changes scoped, reversible, and aligned with existing architecture.
- Use structured APIs, parsers, and framework helpers instead of brittle string manipulation when available.

## Automated Testing

Automated testing is required no matter what language or framework the project uses. Record unit, integration, smoke, lint, type, format, route, package, or deployment checks in `.uai/test-plan.uai`.

For each code change, run targeted automated checks for the touched behavior. If no harness exists, create or document the smallest repeatable automated check before relying on manual verification. If a check cannot run, record the command, reason, and residual risk.

.uai/decisions.uai

Code example

---
uai: "1.0"
type: decisions
status: draft
---

# Decisions

Record accepted decisions, why they were made, and what would cause a reversal.

.uai/memory.uai

Code example

---
uai: "1.0"
type: memory
status: draft
---

# AI Memory

AI Memory is durable, reviewable context that lets a future AI continue useful work without relying on private chat history.

## Bundle Configuration

- Bundle: Project AI Memory
- Use case: Use when a project is active and context must persist across many AI sessions without turning the bundle into a full knowledge base.
- Trust boundary: Internal or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent.

## UAI AI Memory And LLM Wiki

Use UAI AI Memory for compact, portable working packets. Use an LLM Wiki for deep, long-lived internal documentation. Use both when a durable knowledge base needs a reviewed export, handoff packet, onboarding packet, audit packet, or agent-ready task context.

## Promotion Rule

1. Capture raw knowledge in notes, wiki pages, or source documents.
2. Review for accuracy, ownership, privacy, and support boundaries.
3. Promote accepted project truth into AI Memory, canonical docs, code, tests, release notes, or roadmap state.
4. Keep unreviewed material out of governing instructions.

.uai/next-recursive-prompt.uai

Code example

{
  "uai_version": "1.0",
  "profile": "uaix.next-recursive-prompt.v1",
  "schema_version": 1,
  "scope": {
    "scope_id": "{{PACKAGE_SLUG}}",
    "scope_path": ".",
    "local_uai_root": ".uai/",
    "code_scope": true,
    "scope_basis": ["code", "automation", "executable-workflow", "code-like-artifact"],
    "requirement_rule": "Required for agents that deal with code, automation, executable workflows, or code-like artifacts: next-recursive-prompt.uai.",
    "out_of_scope_rule": "Out of scope for agents with no code, automation, executable workflow, or code-like artifacts: next-recursive-prompt.uai.",
    "source_boundary": "Derived from authoritative package files. This record is not a second source of truth."
  },
  "lifecycle": {
    "status": "active",
    "generated_at_utc": "{GENERATED_AT_UTC}",
    "valid_until_utc": "{VALID_UNTIL_UTC}",
    "attempt": 1,
    "supersedes_checksum": ""
  },
  "activation_policy": {
    "activation_rule": "Use the stored next_loop plan when the user indicates continuation or resume intent, including keep going, continue, do the next thing, resume, proceed, or use the next recursive prompt.",
    "relevance_review_rule": "When a new user request directly relates to the stored next_loop, review this file for useful plan ideas before discarding or superseding it.",
    "intake_precedence_rule": "For packages using Agent File Handoff, active Content or Improvement files that relate to the current prompt supersede or expand the stored next_loop. Intake must still lead to concrete project work, hot-memory update, ledger evidence, configured durable-memory preservation, and source-site removal or a recorded keep-active reason.",
    "current_instruction_rule": "When the user provides a specific unrelated instruction, current user instruction governs the turn and overwrites the stored next-loop plan.",
    "regeneration_rule": "After accepted work, update authoritative .uai records first, then regenerate .uai/next-recursive-prompt.uai from those records.",
    "next_prompt_visibility_rule": "At the end of accepted work, show a prominent, sectioned, detailed suggested next prompt to the human in chat so they can review, modify, replace, or simply answer keep going. The prompt must be a standalone, copy-paste-ready handoff and must include literal Feature/improvement focus, Code/source changes, and Automated tests/checks sections, plus context, objective, scope, hard boundaries, work items, expected touchpoints, files to review, done criteria, and final response contract. It must identify a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicit no-op/source-validation-only stop condition. Validation-only or no-source-change work must be labeled no-op/source-validation only, and the Code/source changes section must say no code/source changes plus the reason.",
  "goal_prompt_visibility_rule": "Use goal wording and functionality only when the current work was started from /goal, the human explicitly asked for /goal or a goal prompt, or the last accepted handoff was goal-shaped. Selecting Follow Goals support as an available runtime export does not by itself convert ordinary continuation into /goal. For true goal-origin continuation, label it Suggested Next /goal Prompt, make the first copy-paste line start with /goal, include Goal, Success criteria, Constraints or hard boundaries, Verification, and still include literal Feature/improvement focus, Code/source changes, and Automated tests/checks sections with concrete next work or an explicit no-op/source-validation stop condition.",
    "non_activation_examples": ["A new unrelated feature request.", "A direct request to inspect, test, deploy, or explain a different target.", "A human correction that changes the work objective."]
  },
  "objective": {
    "task_id": "{TASK_ID}",
    "summary": "{CURRENT_GOAL}",
    "priority": "{PRIORITY}",
    "done_criteria": ["{SUCCESS_EVIDENCE}", "Authoritative .uai records are updated before this derived file is regenerated.", "No secrets, raw traces, or unreviewed cold-memory claims are copied into hot memory."]
  },
  "authoritative_refs": {
    "agents_md": "AGENTS.md",
    "readme_human": ".uai/readme.human",
    "memory_maintenance": ".uai/memory-maintenance.uai",
    "identity": ".uai/identity.uai",
    "world_context": ".uai/world-context.uai",
    "short_term_memory": ".uai/short-term-memory.uai",
    "startup_packet": ".uai/startup-packet.uai",
    "system_profile": ".uai/system-profile.uai",
    "receiver_brief": ".uai/receiver-brief.uai",
    "coding_standards": ".uai/coding-standards.uai",
    "stack": ".uai/stack.uai",
    "architecture": ".uai/architecture.uai",
    "context": ".uai/context.uai",
    "constraints": ".uai/constraints.uai",
    "progress": ".uai/progress.uai",
    "current_state": ".uai/current-state.uai",
    "decisions": ".uai/decisions.uai",
    "next_actions": ".uai/next-actions.uai",
    "test_plan": ".uai/test-plan.uai",
    "manifest": ".uai/exports/manifest.json"
  },
  "resume_context": {
    "current_truth_summary": ["Use .uai/short-term-memory.uai for current truth.", "Use this file only to resume the next loop quickly after authoritative memory has been read.", "If this summary conflicts with authoritative refs, stop and regenerate this file from those refs."],
    "recent_changes": [],
    "active_blockers": [],
    "why_now": "A code-bearing package needs a compact next-loop resume artifact after authoritative files have been loaded."
  },
  "human_visible_plan": {
    "display_rule": "Show this plan prominently to the human in chat or review UI when the next-recursive prompt is generated, updated, or requested. Use literal section headings for context/objective, work items, Feature/improvement focus, Code/source changes, Automated tests/checks, files, done criteria, and final-response requirements. The chat version must be a standalone, prompt-shaped handoff block; it may shorten low-value repetition only when it remains copy-paste-ready and preserves those three required sections with actionable detail. It must identify a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicit no-op/source-validation-only stop condition. Validation-only or no-source-change work must be labeled no-op/source-validation only, and the Code/source changes section must say no code/source changes plus the reason. Do not hide the next loop only inside JSON, point to a file instead of showing the key sections, replace it with a generic validation loop, checklist-only outline, or vague keep-going sentence.",
    "editable_by_human": true,
"next_detailed_suggested_prompt": "Continue this UAIX Project Handoff.\n\nContext: load authoritative .uai records first, then inspect the visible repository or environment.\nObjective: complete the first concrete Project Handoff setup improvement: populate missing .uai values from evidence, verify architecture.uai exists for code-bearing scope, add or update the mapped automated check, update memory, and report blockers.\nNext action type: setup-completion improvement unless visible evidence proves there is no drift; in that case report no-op/source-validation only with the stop condition.\nGoal-mode continuation: not selected in this example. Use Suggested Next Prompt for ordinary prompt work; selecting Follow Goals support only creates runtime export material. Switch the visible continuation to Suggested Next /goal Prompt only when the active work starts from /goal, the human explicitly asks for /goal or a goal prompt, or the last accepted handoff was goal-shaped.\nScope: use AGENTS.md, .uai/memory-maintenance.uai, .uai/system-profile.uai, .uai/architecture.uai, .uai/coding-standards.uai, .uai/test-plan.uai, .uai/exports/manifest.json, and current user instructions.\nHard boundaries: current user instruction wins; do not overwrite existing memory silently; do not modify Totem, Taboo, or Talisman without exact human artifact-and-operation authorization; do not claim hosted import, automatic repo writes, sync, certification, endorsement, SDK, or CLI behavior.\n\nWork items:\n1. Verify the generated file set - Confirm required .uai files exist for the declared scope, including architecture.uai for code-bearing packages. Expected output: missing required files are created or a blocker is recorded before broad work.\n2. Populate .uai values from visible evidence - Replace placeholders with facts from source layout, manifests, tests, CI, deploy docs, routes, schemas, owner instructions, or write not available - reason. Expected output: every placeholder is evidence-backed or marked not available - reason.\n3. Decide fresh setup versus additive update - Preserve reviewed facts and merge cautiously when existing memory is present. Expected output: the agent records fresh install or update mode and changed .uai files.\n4. Map codebase, architecture, and checks - Fill architecture, stack, coding standards, and test plan before coding. Expected output: architecture, stack, coding standards, and test plan name concrete files, commands, owners, and risks.\n5. Name the actionable next slice or declare no-op - State whether the next prompt is asking for a concrete feature, bug fix, improvement, test/check addition, package/publication step, or no-op/source-validation pass. Expected output: the human can tell what will be added, fixed, improved, tested, packaged, published, or deliberately not changed.\n\nFeature/improvement focus:\n- Fix vague next-prompt handoffs by naming the concrete feature, bug fix, improvement, or test/check addition that the next agent should perform, or by declaring no-op/source-validation only with a stop condition.\n- Make the handoff clear enough for the human to review and edit next action.\n- Keep generated ZIP, file deck, manifest, and live preview aligned.\n\nCode/source changes:\n- Preserve existing local patterns, DRY ownership, once-and-only-once facts, SOLID defaults, and framework-native APIs before editing code.\n- If this is validation-only or no source patch is needed, explicitly say no-op/source-validation only and give the reason.\n\nExpected touchpoints: review the files and package/runtime surfaces listed below before deciding the next action.\nFiles to review:\n- AGENTS.md\n- .uai/memory-maintenance.uai\n- .uai/system-profile.uai\n- .uai/architecture.uai\n- .uai/coding-standards.uai\n- .uai/test-plan.uai\n- .uai/exports/manifest.json\n- .uai/next-recursive-prompt.uai\n\nTargeted checks: run the automated tests/checks below and add environment-specific checks for touched behavior.\nAutomated tests/checks:\n- Add or update a focused regression check when the next prompt contract changes; otherwise record no-op/source-validation only with the exact no-drift evidence.\n- Parse JSON exports that changed.\n- Run targeted checks for touched code, docs, routes, package files, or memory records.\n- Record skipped checks with exact reason and residual risk.\n\nDone criteria:\n- Required .uai files exist for the declared scope.\n- Initial values are populated from visible evidence or marked not available - reason.\n- Existing memory was preserved or conflicts were recorded.\n- Targeted checks ran or skipped checks are explained.\n- A prominent sectioned next prompt is shown to the human, not only stored in the file or compressed into a tiny paragraph.\n- The Suggested Next Prompt states a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicit no-op/source-validation-only stop condition.\n- Validation-only or no-source-change results are labeled no-op/source-validation only and still include substantive Feature/improvement focus, Code/source changes, and Automated tests/checks sections.\n\nFinal response must include:\n- Changed files or explicit no-op/source-validation-only evidence.\n- Tests run plus skipped checks with reasons and residual risk.\n- Blockers, support-boundary risks, and publication/package status.\n- Memory records updated or why no memory update was needed.\n- Feature/improvement focus, Code/source changes, and Automated tests/checks sections with content; if no source patch was made, Code/source changes says no code/source changes and why.\n- A prominent Suggested Next Prompt section containing a copy-paste-ready prompt, not just labels. It must include literal sections named Feature/improvement focus, Code/source changes, and Automated tests/checks, plus context/objective, done criteria, and source/package/live boundaries. It must name a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicitly say no-op/source-validation only with a stop condition; a file reference, tiny footer, generic validation loop, or checklist-only outline is non-compliant.",
    "work_items": [
      {"id": "verify-file-set", "title": "Verify the generated file set", "detail": "Confirm required .uai files exist for the declared scope, including architecture.uai for code-bearing packages."},
      {"id": "populate-visible-values", "title": "Populate .uai values from visible evidence", "detail": "Replace placeholders with facts from source layout, manifests, tests, CI, deploy docs, routes, schemas, owner instructions, or write not available - reason."},
      {"id": "choose-fresh-or-update-mode", "title": "Decide fresh setup versus additive update", "detail": "Preserve reviewed facts and merge cautiously when existing memory is present."},
      {"id": "map-codebase", "title": "Map codebase, architecture, and checks", "detail": "Fill architecture, stack, coding standards, and test plan before coding."}
    ],
    "feature_changes": ["Make the handoff prominent and sectioned enough for the human to review and edit next action.", "Keep generated ZIP, file deck, manifest, and live preview aligned."],
    "code_changes": ["Preserve existing local patterns, DRY ownership, once-and-only-once facts, SOLID defaults, and framework-native APIs before editing code."],
    "test_plan": ["Parse JSON exports that changed.", "Run targeted checks for touched code, docs, routes, package files, or memory records.", "Record skipped checks with exact reason and residual risk."],
    "files_to_review": ["AGENTS.md", ".uai/memory-maintenance.uai", ".uai/system-profile.uai", ".uai/architecture.uai", ".uai/coding-standards.uai", ".uai/test-plan.uai", ".uai/exports/manifest.json", ".uai/next-recursive-prompt.uai"],
    "done_criteria": ["Required .uai files exist for the declared scope.", "Initial values are populated from visible evidence or marked not available - reason.", "Existing memory was preserved or conflicts were recorded.", "Targeted checks ran or skipped checks are explained.", "A prominent sectioned next prompt is shown to the human, not only stored in the file or compressed into a tiny paragraph.", "The final response includes a standalone, prompt-shaped Suggested Next Prompt block with enough detail for another agent to act without opening hidden memory; it may shorten low-value repetition only when all required sections remain present.", "The Suggested Next Prompt states a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicit no-op/source-validation-only stop condition.", "Validation-only or no-source-change results are labeled no-op/source-validation only and still include substantive Feature/improvement focus, Code/source changes, and Automated tests/checks sections."],
    "final_response_must_include": ["Changed files or explicit no-op/source-validation-only evidence.", "Tests run plus skipped checks with reasons and residual risk.", "Blockers, support-boundary risks, and publication/package status.", "Memory records updated or why no memory update was needed.", "Feature/improvement focus, Code/source changes, and Automated tests/checks sections with content; if no source patch was made, Code/source changes says no code/source changes and why.", "A prominent Suggested Next Prompt section containing a copy-paste-ready prompt, not just labels. It must include literal sections named Feature/improvement focus, Code/source changes, and Automated tests/checks, plus context/objective, done criteria, and source/package/live boundaries. It must name a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicitly say no-op/source-validation only with a stop condition; a file reference, tiny footer, generic validation loop, or checklist-only outline is non-compliant."]
  },
  "next_loop": {
    "mode": "implement-then-verify",
    "first_response_contract": {
      "must_report": ["loaded context", "hard constraints", "expected touchpoints", "targeted checks"],
      "max_bullets": 6
    },
    "final_response_contract": {
"must_include": ["Changed files or explicit no-op/source-validation-only evidence.", "Tests run plus skipped checks with reasons and residual risk.", "Blockers, support-boundary risks, and publication/package status.", "Memory records updated or why no memory update was needed.", "Feature/improvement focus, Code/source changes, and Automated tests/checks sections with content; if no source patch was made, Code/source changes says no code/source changes and why.", "A prominent Suggested Next Prompt section containing a copy-paste-ready prompt, not just labels. It must include literal sections named Feature/improvement focus, Code/source changes, and Automated tests/checks, plus context/objective, done criteria, and source/package/live boundaries. It must name a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicitly say no-op/source-validation only with a stop condition; a file reference, tiny footer, generic validation loop, or checklist-only outline is non-compliant.", "Suggested Next /goal Prompt with a leading /goal line and Goal / Success criteria / Constraints / Verification wording only when the active work started from /goal, the human explicitly requested a goal prompt, or the last accepted handoff was goal-shaped."],
"next_detailed_suggested_prompt_requirements": ["context", "objective", "scope", "hard boundaries", "work items", "Feature/improvement focus", "concrete feature, bug fix, improvement, test/check addition, package/publication step, or no-op/source-validation stop condition", "code/source changes", "expected touchpoints", "files to review", "targeted checks", "Automated tests/checks", "done criteria", "final response contract", "Suggested Next /goal Prompt with a leading /goal line only when the active work started from /goal, the human explicitly requested a goal prompt, or the last accepted handoff was goal-shaped"],
      "user_choice": "The human can edit the prompt, replace it, or answer keep going."
    },
    "prompt": "Continue this UAIX Project Handoff.\n\nContext: load authoritative .uai records first, then inspect the visible repository or environment.\nObjective: complete the first concrete Project Handoff setup improvement: populate missing .uai values from evidence, verify architecture.uai exists for code-bearing scope, add or update the mapped automated check, update memory, and report blockers.\nNext action type: setup-completion improvement unless visible evidence proves there is no drift; in that case report no-op/source-validation only with the stop condition.\nGoal-mode continuation: not selected in this example. Use Suggested Next Prompt for ordinary prompt work; selecting Follow Goals support only creates runtime export material. Switch the visible continuation to Suggested Next /goal Prompt only when the active work starts from /goal, the human explicitly asks for /goal or a goal prompt, or the last accepted handoff was goal-shaped.\nScope: use AGENTS.md, .uai/memory-maintenance.uai, .uai/system-profile.uai, .uai/architecture.uai, .uai/coding-standards.uai, .uai/test-plan.uai, .uai/exports/manifest.json, and current user instructions.\nHard boundaries: current user instruction wins; do not overwrite existing memory silently; do not modify Totem, Taboo, or Talisman without exact human artifact-and-operation authorization; do not claim hosted import, automatic repo writes, sync, certification, endorsement, SDK, or CLI behavior.\n\nWork items:\n1. Verify the generated file set - Confirm required .uai files exist for the declared scope, including architecture.uai for code-bearing packages. Expected output: missing required files are created or a blocker is recorded before broad work.\n2. Populate .uai values from visible evidence - Replace placeholders with facts from source layout, manifests, tests, CI, deploy docs, routes, schemas, owner instructions, or write not available - reason. Expected output: every placeholder is evidence-backed or marked not available - reason.\n3. Decide fresh setup versus additive update - Preserve reviewed facts and merge cautiously when existing memory is present. Expected output: the agent records fresh install or update mode and changed .uai files.\n4. Map codebase, architecture, and checks - Fill architecture, stack, coding standards, and test plan before coding. Expected output: architecture, stack, coding standards, and test plan name concrete files, commands, owners, and risks.\n5. Name the actionable next slice or declare no-op - State whether the next prompt is asking for a concrete feature, bug fix, improvement, test/check addition, package/publication step, or no-op/source-validation pass. Expected output: the human can tell what will be added, fixed, improved, tested, packaged, published, or deliberately not changed.\n\nFeature/improvement focus:\n- Fix vague next-prompt handoffs by naming the concrete feature, bug fix, improvement, or test/check addition that the next agent should perform, or by declaring no-op/source-validation only with a stop condition.\n- Make the handoff clear enough for the human to review and edit next action.\n- Keep generated ZIP, file deck, manifest, and live preview aligned.\n\nCode/source changes:\n- Preserve existing local patterns, DRY ownership, once-and-only-once facts, SOLID defaults, and framework-native APIs before editing code.\n- If this is validation-only or no source patch is needed, explicitly say no-op/source-validation only and give the reason.\n\nExpected touchpoints: review the files and package/runtime surfaces listed below before deciding the next action.\nFiles to review:\n- AGENTS.md\n- .uai/memory-maintenance.uai\n- .uai/system-profile.uai\n- .uai/architecture.uai\n- .uai/coding-standards.uai\n- .uai/test-plan.uai\n- .uai/exports/manifest.json\n- .uai/next-recursive-prompt.uai\n\nTargeted checks: run the automated tests/checks below and add environment-specific checks for touched behavior.\nAutomated tests/checks:\n- Add or update a focused regression check when the next prompt contract changes; otherwise record no-op/source-validation only with the exact no-drift evidence.\n- Parse JSON exports that changed.\n- Run targeted checks for touched code, docs, routes, package files, or memory records.\n- Record skipped checks with exact reason and residual risk.\n\nDone criteria:\n- Required .uai files exist for the declared scope.\n- Initial values are populated from visible evidence or marked not available - reason.\n- Existing memory was preserved or conflicts were recorded.\n- Targeted checks ran or skipped checks are explained.\n- A prominent sectioned next prompt is shown to the human, not only stored in the file or compressed into a tiny paragraph.\n- The Suggested Next Prompt states a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicit no-op/source-validation-only stop condition.\n- Validation-only or no-source-change results are labeled no-op/source-validation only and still include substantive Feature/improvement focus, Code/source changes, and Automated tests/checks sections.\n\nFinal response must include:\n- Changed files or explicit no-op/source-validation-only evidence.\n- Tests run plus skipped checks with reasons and residual risk.\n- Blockers, support-boundary risks, and publication/package status.\n- Memory records updated or why no memory update was needed.\n- Feature/improvement focus, Code/source changes, and Automated tests/checks sections with content; if no source patch was made, Code/source changes says no code/source changes and why.\n- A prominent Suggested Next Prompt section containing a copy-paste-ready prompt, not just labels. It must include literal sections named Feature/improvement focus, Code/source changes, and Automated tests/checks, plus context/objective, done criteria, and source/package/live boundaries. It must name a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicitly say no-op/source-validation only with a stop condition; a file reference, tiny footer, generic validation loop, or checklist-only outline is non-compliant.",
    "work_items": [
      {"id": "verify-file-set", "title": "Verify the generated file set", "detail": "Confirm required .uai files exist for the declared scope, including architecture.uai for code-bearing packages."},
      {"id": "populate-visible-values", "title": "Populate .uai values from visible evidence", "detail": "Replace placeholders with facts from source layout, manifests, tests, CI, deploy docs, routes, schemas, owner instructions, or write not available - reason."},
      {"id": "choose-fresh-or-update-mode", "title": "Decide fresh setup versus additive update", "detail": "Preserve reviewed facts and merge cautiously when existing memory is present."},
      {"id": "map-codebase", "title": "Map codebase, architecture, and checks", "detail": "Fill architecture, stack, coding standards, and test plan before coding."}
    ],
    "feature_changes": ["Make the handoff prominent and sectioned enough for the human to review and edit next action.", "Keep generated ZIP, file deck, manifest, and live preview aligned."],
    "code_changes": ["Preserve existing local patterns, DRY ownership, once-and-only-once facts, SOLID defaults, and framework-native APIs before editing code."],
    "test_plan": ["Parse JSON exports that changed.", "Run targeted checks for touched code, docs, routes, package files, or memory records.", "Record skipped checks with exact reason and residual risk."],
    "files_to_review": ["AGENTS.md", ".uai/memory-maintenance.uai", ".uai/system-profile.uai", ".uai/architecture.uai", ".uai/coding-standards.uai", ".uai/test-plan.uai", ".uai/exports/manifest.json", ".uai/next-recursive-prompt.uai"],
    "done_criteria": ["Required .uai files exist for the declared scope.", "Initial values are populated from visible evidence or marked not available - reason.", "Existing memory was preserved or conflicts were recorded.", "Targeted checks ran or skipped checks are explained.", "A prominent sectioned next prompt is shown to the human, not only stored in the file or compressed into a tiny paragraph.", "The final response includes a standalone, prompt-shaped Suggested Next Prompt block with enough detail for another agent to act without opening hidden memory; it may shorten low-value repetition only when all required sections remain present.", "Validation-only or no-source-change results are labeled no-op/source-validation only and still include substantive Feature/improvement focus, Code/source changes, and Automated tests/checks sections."],
    "final_response_must_include": ["Changed files or explicit no-op/source-validation-only evidence.", "Tests run plus skipped checks with reasons and residual risk.", "Blockers, support-boundary risks, and publication/package status.", "Memory records updated or why no memory update was needed.", "Feature/improvement focus, Code/source changes, and Automated tests/checks sections with content; if no source patch was made, Code/source changes says no code/source changes and why.", "A prominent Suggested Next Prompt section containing a copy-paste-ready prompt, not just labels. It must include literal sections named Feature/improvement focus, Code/source changes, and Automated tests/checks, plus context/objective, done criteria, and source/package/live boundaries. It must name a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicitly say no-op/source-validation only with a stop condition; a file reference, tiny footer, generic validation loop, or checklist-only outline is non-compliant."],
    "ordered_steps": [
      "Read AGENTS.md and .uai/memory-maintenance.uai before broad memory loading.",
      "Read and obey .uai/totem.uai, .uai/taboo.uai, and .uai/talisman.uai before broad execution; do not modify, weaken, replace, delete, or bypass any of those anchors without exact human artifact-and-operation authorization.",
      "Read the remaining ordinary .uai files named in authoritative_refs for the declared package scope.",
      "Verify .uai/architecture.uai exists for code-bearing scope and populate it from visible source, route, schema, build, test, deployment, and support-claim evidence.",
      "Populate new .uai values from what can reasonably be seen in the environment; use not available - reason only when a fact is not visible.",
      "When updating existing files, merge cautiously and preserve reviewed local facts instead of replacing them with generated defaults.",
      "Review .uai/next-recursive-prompt.uai for relevant ideas when the current request continues, resumes, or directly relates to the stored next loop.",
      "When Agent File Handoff is enabled, enumerate active Content and Improvement files; related intake supersedes or expands this next loop and must produce project work before configured durable-memory preservation and source-site removal.",
      "Verify workspace, identity, world context, memory-maintenance policy, constraints, coding standards, stack, architecture, current state, and test plan.",
      "Process active intake before unrelated work when file handoff is enabled.",
      "Implement the smallest safe improvement that advances the stated objective.",
      "Run targeted automated checks and record skipped checks with reasons.",
      "Update short-term memory, progress, test plan, and this derived next-recursive prompt.",
      "Report changed files, automated tests/checks, blockers, and the next recursive work prompt.",
"End ordinary prompt work with a prominent, sectioned Suggested Next Prompt that the human can review, modify, replace, or answer with keep going. End true /goal work with a prominent, sectioned Suggested Next /goal Prompt whose first copy-paste line starts with /goal and preserves Goal / Success criteria / Constraints / Verification wording. Follow Goals export selection alone is not goal-origin and must not force a /goal continuation. Either form must identify a concrete next feature, bug fix, improvement, test/check addition, package/publication step, or explicit no-op/source-validation-only stop condition and include Feature/improvement focus, Code/source changes, and Automated tests/checks sections. If no source/code patch was made, label the result no-op/source-validation only and make Code/source changes explain no code/source changes plus the reason."
    ],
    "if_blocked": {
      "action": "emit-blocked-state",
      "required_updates": [".uai/progress.uai", ".uai/current-state.uai", ".uai/next-actions.uai", ".uai/next-recursive-prompt.uai"],
      "human_escalation_reason_template": "State the blocker, the safe next step, and the precise approval or evidence needed."
    }
  },
  "checks": {
    "required": ["PHP lint for touched PHP files", "JS syntax check for touched browser assets", "JSON/XML parse for touched machine records", "Playwright or rendered-route checks for touched wizard UI when available", "git diff --check"],
    "out_of_scope_for_this_scope": [],
    "last_known_results": []
  },
  "writeback_policy": {
    "authority_rule": "Derived hot-memory resume artifact; not a second source of truth. Authoritative .uai records win on conflict. Regenerate from authoritative handoff files after meaningful work.",
    "must_update_before_success": [".uai/short-term-memory.uai", ".uai/progress.uai", ".uai/test-plan.uai", ".uai/intake-outcome-ledger.uai when file handoff is enabled", ".uai/next-recursive-prompt.uai"],
    "update_decisions_if_changed": ".uai/decisions.uai",
    "never_copy_into_hot_files": ["raw traces", "secrets", "private customer data", "large tool logs", "unreviewed cold-memory claims"],
    "conflict_rule": "Authoritative .uai records win on conflict. Regenerate this file from authoritative handoff files before using it again."
  },
  "security": {
    "approval_required_for": ["production deploy", "destructive repository operations", "schema boundary changes", "public support-claim widening"],
    "no_op_triggers": ["missing_authoritative_ref", "stale_constraints", "integrity_mismatch", "scope_conflict", "conflict_with_human_instruction", "conflict_with_repository_policy"],
    "escalation_triggers": ["support boundary would widen", "runtime behavior would be implied", "non-coding package would be made to look code-required", "code-bearing package lacks required coding memory"],
    "local_policy_wins": true
  },
  "cold_memory": {
    "refs": []
  },
  "provenance": {
    "trigger": "starter-template",
    "generated_by": "UAIX AI Memory starter template",
    "runtime_id": "",
    "issued_at_utc": "{GENERATED_AT_UTC}"
  },
  "integrity": {
    "canonicalization": "canonical-json",
    "yaml_mirror_allowed": false,
    "checksum": "sha256:{RECEIVER_COMPUTES_AFTER_WRITE}",
    "source_digests": [],
    "signatures": []
  }
}

What Belongs In AI Memory

Project overview, current state, decisions, open questions, next actions, risks, constraints, owners, glossary, and agent instructions.
Root AGENTS.md plus local memory files such as .uai/readme.human when agents need a predictable load path.
Typed .uai files when the project needs explicit context, stack, architecture, constraints, progress, operations, test planning, style, decisions, or memory rules.
Links to deeper docs or LLM Wiki pages only when those sources are reviewed and clearly marked as background or promoted truth.

What Should Not Be Included

Secrets, credentials, private keys, tokens, connection strings, or unreviewed production logs.
Raw customer, patient, employee, or user data unless a secure approved process exists.
Private legal analysis, internal-only strategy, pricing, security details, or unsupported support claims.
Old chats, generated summaries, dropped files, and LLM Wiki pages treated as truth without review.
Executable payloads that a future agent might run without human approval.

Privacy And Trust Boundaries

Choose the bundle by trust boundary, not by name alone. Internal Project AI Memory can carry more operational detail than an external handoff. Agent Session Memory records tool permissions when the profile requires them and temporary work state that should be archived quickly. External Handoff, Incident/Audit, and LLM Wiki Export packets need redaction, approval, and clear source notes before sharing.

Review secrets and credentials before every share.
Minimize customer or user data.
Mark internal-only strategy and legal material.
Name agent permissions and blocked actions.
Prefer sanitized exports over raw internal memory.

Maintenance Model

AI Memory is not a dumping ground. Keep high-churn files current and keep durable files stable. .uai/current-state.uai and .uai/next-actions.uai can change often. .uai/decisions.uai should be append-first or carefully revised. .uai/risks-and-constraints.uai and .uai/agent-instructions.uai should be reviewed whenever permissions, production boundaries, support claims, or safety posture change. .uai/changelog.uai should explain meaningful bundle updates.

Run a context diet when the packet starts carrying old history. Preserve the pre-slim version in cold memory first, record the source path, final path, checksum, actor, time, and disposition, then shorten the active file to current truth plus a pointer.

How Agents Consume AI Memory

Read the manifest and front-door files before acting.
Load only the files required by the bundle and current task.
Report missing, circular, contradictory, unreadable, or oversized memory before broad work.
Summarize current truth, constraints, intended touchpoints, and checks before editing.
Treat LLM Wiki, old chat, generated summaries, and dropped files as background until reviewed and promoted.

Site, Solution, Or Workspace Placement

For one WordPress site, keep the local .uai/ folder at the individual site root and use root AGENTS.md as the entry point. For one Visual Studio solution, keep .uai/ beside the real .sln or .slnx file, then explicitly register every generated .uai file as solution items so they appear in Solution Explorer. A physical folder on disk is not enough by itself. In both cases .uai/readme.human and typed .uai records stay inside the local memory folder.

For classic .sln files, that means adding a .uai solution folder with a ProjectSection(SolutionItems) entry for each generated file. After the solution file is updated, verify every referenced .uai path exists and reload Visual Studio if the solution was already open.

Use project-level .uai/ folders inside a Visual Studio solution only when projects have independent ownership, release, or handoff boundaries. In that rarer shape, a solution-level workspace.uai can coordinate those project folders; otherwise the more common coordinator is a higher-level workspace or organization workspace.uai that routes across multiple solutions.

For multiple WordPress sites or Visual Studio solutions in one ecosystem, use workspace.uai as the only UAI memory file outside local .uai/ folders. Each selected site or solution AGENTS.md should point to both that coordinator and its own local .uai/ folder, and the agent should resolve the explicit human domain, route, repository, solution, or path before loading local memory. The selected target’s hot memory loads; sibling .uai bundles stay unloaded unless the task explicitly asks for cross-target source routing, authority comparison, package coordination, or archive preservation.

If the package will steer deployment, include a workspace instruction surface that names the deployment owner, shared version policy, publish folders, install targets, checksum or rollback evidence, and any mixed-stack differences. A workspace where WordPress sites use consistent theme/plugin upload folders but .NET solutions deploy differently should say that in workspace.uai instead of leaving future agents to infer it from filenames.

Before relying on a remembered absolute coordinator path, verify the coordinator file exists and that the selected registry root plus AGENTS.md path resolve. If a pointer is stale, locate workspace.uai only far enough to confirm the intended router, repair or report the stale path, and never silently fall back to the current shell directory when the human named another target.

This prevents the current shell directory from silently winning over a named site such as LLMWikis.org, UAIX.org, AIWikis.org, or another related workspace root.

How Humans Review And Approve Memory

Humans should be able to review the same files the AI will load. Before sharing a bundle or using it to steer an autonomous agent, check ownership, dates, stale claims, sensitive data, trust boundaries, and whether planned work is clearly separated from current support. Ask the AI to name exactly which memory files changed and why.

UAIX AI Memory And LLM Wiki

LLM Wiki is out of scope for baseline UAI specs and standards. UAIX supports it as a deep-memory strategy required for LLM Wiki configuration because teams that already use one need different package-shaping choices, source boundaries, and promotion rules.

UAIX AI Memory and LLM Wiki solve different memory problems. UAIX AI Memory is a portable working packet for continuity, handoffs, onboarding, external collaboration, audits, quick exports, and agent-ready context. LLMWikis.org represents the stronger pattern for deep, long-lived internal documentation and durable organizational knowledge.

Mature organizations may use both: LLM Wiki as the durable internal knowledge base, and UAIX AI Memory bundles as portable snapshots, working context, onboarding exports, handoff packets, audit packets, or agent-run context.

When To Use UAIX AI Memory

Use Project AI Memory when a project is active and context needs to persist across sessions.
Use Project Handoff when ownership, execution, or responsibility is moving.
Use Agent Session Memory when an AI agent needs resumable task context.
Use Onboarding Memory when a human or agent needs a curated starting point.
Use Decision Memory when rationale and tradeoffs matter more than status.

When To Use LLM Wiki

Use LLM Wiki when the organization needs deep, durable, searchable institutional knowledge.
Use it for long source summaries, research trails, comparisons, policy background, and internal education.
Keep it informative rather than governing until accepted facts are promoted into AI Memory, docs, code, tests, release notes, roadmap state, or public evidence.

When To Use Both

Use both when a durable knowledge base needs portable working packets. The LLM Wiki remains expansive; the AI Memory bundle remains decisive. If the decisive bundle starts growing like a wiki, archive the old detail and keep only the accepted current state. For the practical operating path, read Using UAI Packages With An LLM Wiki and Project Handoff Context Budget. For the longer rationale, read LLM Wiki vs. UAIX Project Handoff and LLM Wiki and UAIX Project Handoff.

How Samples, Manifests, And ZIPs Stay Synchronized

Rendered sample files, bundle manifests, download links, and generated ZIPs all resolve through the same canonical registry. There are no stale static starter ZIP assets and no ZIP-only sample files. If a shared file belongs to multiple bundles, it is selected by the same template ID. If a bundle needs variation, the variation is an explicit parameter, selected section, or overlay recorded in the manifest.

Public Route And Alias

The canonical UAIX page for this topic is /en-us/ai-memory/. The requested /AI_Memory entry path redirects here as the search-friendly entry alias while canonical UAIX public routes remain clean, locale-prefixed paths.

Long-Running Goal Execution

Use Long-Running Goal Execution when AI Memory must survive multiple runtime sessions, pauses, blockers, handoffs, or final reports. Runtime goals keep the active objective focused; authoritative .uai files preserve durable project truth; UAI-1 packets carry portable evidence; reviewed write-back promotes accepted facts.

Hierarchical Goal Memory

Use Hierarchical Goal Memory when AI Memory needs a source-linked hierarchy over subgoals, folds, checkpoints, and bounded evidence without replacing canonical source files.

Agent Communication Operating Model

Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary.

Use Agent Communication Operating Model when a human operator, coding agent, AI agent, or runtime implementer needs portable identity, intent, context, acknowledgement, status, blocker, memory proposal, validation evidence, correction, final report, or handoff records. The matching machine-readable assets are published through Schemas, Registry, Examples, and the Validator.

UAIX does not provide automatic sync, hosted messaging, runtime orchestration, official adapters, repository write execution, certification authority, or hosted import mechanisms.
Carcinus.org is a separate runtime/orchestrator example that may consume UAIX records. UAIX.org does not implement Carcinus runtime behavior and does not execute Carcinus workflows.
LocalEndPoint and other runtimes may consume the published UAIX records as external consumers; UAIX.org does not implement their project-specific runtime features.
Durable memory proposals stay separate from task execution records. Do not promote temporary endpoint statuses, session tokens, write tokens, beta platform instructions, local error traces, private keys, or API credentials.

Build compact project memory without turning history into truth

One source for samples and ZIP

Project Handoff makes memory operational

Memory-maintenance is required first

Every package file has a declared required scope

Shared wiki memory fits groups

Synthesize before you point

Archive before slimming

Validator-backed proof path

What AI Memory Means In UAIX#

Canonical AI Memory#

Fastest Practical Path#

Why Unstructured AI Memory Fails#

Why File-Based Memory Works#

AI Memory Taxonomy#

Choose the right AI Memory configuration#

Views and presets over supported bundles#

Deferred configurations#

Which Configuration To Choose#

Project AI Memory And Project Handoff#

Inspect The Project AI Memory Starter#

Project AI Memory#

What Belongs In AI Memory#

What Should Not Be Included#

Privacy And Trust Boundaries#

Maintenance Model#

How Agents Consume AI Memory#

Site, Solution, Or Workspace Placement#

How Humans Review And Approve Memory#

UAIX AI Memory And LLM Wiki#

When To Use UAIX AI Memory#

When To Use LLM Wiki#

When To Use Both#

How Samples, Manifests, And ZIPs Stay Synchronized#

Public Route And Alias#

Related UAIX Records#

Long-Running Goal Execution#

Hierarchical Goal Memory#

.uaix Package Format#

Agent Communication Operating Model#

What AI Memory Means In UAIX

Canonical AI Memory

Fastest Practical Path

Why Unstructured AI Memory Fails

Why File-Based Memory Works

AI Memory Taxonomy

Choose the right AI Memory configuration

Views and presets over supported bundles

Deferred configurations

Which Configuration To Choose

Project AI Memory And Project Handoff

Inspect The Project AI Memory Starter

Project AI Memory

What Belongs In AI Memory

What Should Not Be Included

Privacy And Trust Boundaries

Maintenance Model

How Agents Consume AI Memory

Site, Solution, Or Workspace Placement

How Humans Review And Approve Memory

UAIX AI Memory And LLM Wiki

When To Use UAIX AI Memory

When To Use LLM Wiki

When To Use Both

How Samples, Manifests, And ZIPs Stay Synchronized

Public Route And Alias

Related UAIX Records

Long-Running Goal Execution

Hierarchical Goal Memory

.uaix Package Format

Agent Communication Operating Model