What AI 记忆 Means In UAIX
UAI AI 记忆 is a lightweight, portable, file-based standard for durable context. It gives humans and AI 代理s 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 记忆 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 记忆 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 source summaries, hashes, and dated logs. 提升 only the reviewed current conclusion back into the AI 记忆 packet.
Canonical AI 记忆
Use Canonical AI 记忆 when you need the layer map behind the packet: raw sources, reviewed LLM Wiki memory, derived graph projections, compact UAI AI 记忆, 项目交接 transfer context, and the execution agent that still has to obey local rules.
Fastest Practical Path
Most readers should start with the AI 记忆数据包向导. It turns the current supported presets into a reviewable startup packet, receiver brief, system profile, manifest overlay, wiki plan required for LLM Wiki configuration, copyable file deck, and canonical ZIP link without claiming hosted import, repository writes, automatic sync, SDK, CLI, certification, or endorsement.
Rare protected-anchor governance belongs on the 护符系统 page, not in the normal wizard flow. Use it only when a complicated, persistent, multi-actor ecosystem needs protected totem.uai and taboo.uai anchors, external enforcement, no-op talk-back, audit evidence, and rollback.
Why Unstructured AI 记忆 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-基础d 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 记忆 Taxonomy
UAIX now treats Project AI 记忆 as the ongoing working-memory configuration and 项目交接 as a subtype of AI 记忆 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 记忆配置
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 记忆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. 信任: 内部 or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent. |
uai-ai-memory-starter.zip |
Traspaso de proyectoproject-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. 信任: Can be internal or external, but external handoffs must be sanitized and approved before sharing. |
uai-project-handoff-starter.zip |
Agent Session Memoryagent-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. 信任: Often operational and sensitive. Keep permissions, tool access, blocked actions, and cleanup state explicit. |
uai-agent-session-memory-starter.zip |
Onboarding Memoryonboarding-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. 信任: Usually shareable after review, but remove internal strategy, customer data, credentials, and privileged operations. |
uai-onboarding-memory-starter.zip |
Decision Memorydecision-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. 信任: 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 Memoryexternal-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. 信任: 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 Memoryincident-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. 信任: 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 Memoryllm-wiki-export-memory
|
Use when a large internal wiki needs a small, reviewable, portable packet for a project, handoff, onboarding, or agent task. |
Lifecycle: 生成时间 from reviewed wiki material, checked against source citations, then promoted or discarded after use. 信任: 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 Memoryoffice-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. 信任: 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 Memoryexecutive-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. 信任: Highly sensitive. Requires strong redaction and authority boundaries before sharing. |
uai-executive-assistant-memory-starter.zip |
Personal Assistant Memorypersonal-assistant-memory
|
Use when privacy and freshness matter more than project history. |
Lifecycle: Continuously maintained; privacy and freshness are more important than project history. 信任: Private by default. Avoid unnecessary sensitive personal data. |
uai-personal-assistant-memory-starter.zip |
AI Chatbot Friend Memorychatbot-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. 信任: 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 记忆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. 信任: Private, sensitive, and safety-bound. Keep support boundaries explicit. |
uai-companion-memory-starter.zip |
Tutor or Coach Memorytutor-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. 信任: Educational or coaching context. Avoid sensitive records unless explicitly reviewed and necessary. |
uai-tutor-coach-memory-starter.zip |
Creative Partner Memorycreative-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. 信任: May contain private drafts, unreleased work, IP-sensitive ideas, brand strategy, or client material. |
uai-creative-partner-memory-starter.zip |
Household Assistant Memoryhousehold-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. 信任: 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 Memorycustomer-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. 信任: 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 记忆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. 信任: 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 记忆 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 记忆 plus Decision Memory.
Deferred configurations
- Certification Memory: 证据 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 记忆数据包向导 when one supported starter configuration should become a package model, populated system profile, receiver brief, startup packet, manifest overlay, copy-paste file deck, 代理文件交接 plan required for 代理文件交接 configuration, LLM Wiki memory-plan file required for LLM Wiki configuration, readiness review, and canonical ZIP download.
Which Configuration To Choose
| Situation | Use | Why |
|---|---|---|
| An active project needs continuity across AI sessions. | Project AI 记忆 | It keeps current state, constraints, decisions, next actions, and agent instructions alive without becoming a full wiki. |
| Ownership, execution, or responsibility is moving. | 项目交接 | 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 protected Totem and Taboo anchor governance. | 护符系统 | It keeps protected-anchor change requests behind no-op behavior, human review, audit evidence, rollback, and external controls. |
Project AI 记忆 And 项目交接
项目交接 is a subtype of UAI AI 记忆. AI 记忆 is the broad standard: durable AI-readable context. 项目交接 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 记忆 and 项目交接 share overlapping required files by profile. For a larger organization, Project AI 记忆 stays alive during everyday work, while 项目交接 is prepared and reviewed when responsibility moves.
Inspect The Project AI 记忆 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.
Live Starter 数据包
Project AI 记忆
The ZIP is generated on request from the 29 visible canonical files below, including the generated manifest. The download, page samples, and bundle presets share one source of truth.
Use when a project is active and context must persist across many AI sessions without turning the bundle into a full knowledge base.
.uai/exports/manifest.json
{
"bundle_id": "project-ai-memory",
"name": "Project AI 记忆",
"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": "内部 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/short-term-memory.uai",
".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": "/",
"declared_package_profiles": [
"project-ai-memory"
],
"universal_required_files": [
".uai/memory-maintenance.uai",
".uai/identity.uai",
".uai/world-context.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, protected paths, and enforcement rules.",
"missing_behavior": "package_invalid"
},
"protected_paths": [
{
"path": ".uai/taboo.uai",
"aliases": [
"taboo.uai"
],
"presence": "optional",
"protected_when_present": true,
"access": "operator_explicit_only",
"agent_default": "forbidden",
"outside_memory_maintenance": true,
"scan": false,
"validate": false,
"lint": false,
"create": false,
"modify": false,
"include_in_package": false,
"include_in_export": false,
"index": false,
"infer_from_absence": false,
"suggestion_policy": "Agents may recommend or request permission for a protected-artifact operation, but must not perform it without a human naming the exact artifact and exact operation."
},
{
"path": ".uai/totem.uai",
"aliases": [
"totem.uai"
],
"presence": "optional",
"protected_when_present": true,
"access": "operator_explicit_only",
"agent_default": "forbidden",
"outside_memory_maintenance": true,
"scan": false,
"validate": false,
"lint": false,
"create": false,
"modify": false,
"include_in_package": false,
"include_in_export": false,
"index": false,
"infer_from_absence": false,
"suggestion_policy": "Agents may recommend or request permission for a protected-artifact operation, but must not perform it without a human naming the exact artifact and exact operation."
},
{
"path": ".uai/talisman.uai",
"aliases": [
"talisman.uai"
],
"presence": "optional",
"protected_when_present": true,
"access": "operator_explicit_only",
"agent_default": "forbidden",
"outside_memory_maintenance": true,
"scan": false,
"validate": false,
"lint": false,
"create": false,
"modify": false,
"include_in_package": false,
"include_in_export": false,
"index": false,
"infer_from_absence": false,
"suggestion_policy": "Agents may recommend or request permission for a protected-artifact operation, but must not perform it without a human naming the exact artifact and exact operation."
}
],
"profile_required_file_sets": [
{
"profile": "project-ai-memory",
"requirement": "Required for Project AI 记忆 packages",
"files": [
".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"
]
}
],
"content_triggered_required_file_sets": [
{
"rule_id": "coding_standards",
"requirement": "存在代码、自动化、可执行工作流或类代码工件时必需。",
"matched_signals": [
"project_or_developer_profile",
"code_like_artifacts"
],
"files": [
".uai/coding-standards.uai"
]
},
{
"rule_id": "next_recursive_prompt",
"requirement": "next-recursive-prompt.uai is required for agents that deal with code, automation, executable workflows, or code-like artifacts. It is not required for agents that don't deal with any coding.",
"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/short-term-memory.uai",
".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"
],
"not_required_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/short-term-memory.uai",
".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 记忆 labels and ongoing-maintenance guidance."
],
"files": [
{
"path": ".uai/memory-maintenance.uai",
"template_id": "uai-memory-maintenance",
"source": "template:uai-memory-maintenance@1",
"bytes": 3292,
"sha256": "b6d28ba05d93b15a2c5f16fe009cb36a898d4669dacff4d9fefa789f980cc8cf"
},
{
"path": ".uai/identity.uai",
"template_id": "uai-identity",
"source": "template:uai-identity@1",
"bytes": 2216,
"sha256": "1987d3b153f917f5dc8b820cfe0bf025a53576b3344496d98cbb4ed3301562b3"
},
{
"path": ".uai/world-context.uai",
"template_id": "uai-world-context",
"source": "template:uai-world-context@1",
"bytes": 1834,
"sha256": "a0b763015d6800eb606f7271c2cdc4ca3e2b3b0877dcd2e53ddb79885755418e"
},
{
"path": ".uai/short-term-memory.uai",
"template_id": "uai-short-term-memory",
"source": "template:uai-short-term-memory@1",
"bytes": 2599,
"sha256": "2a24bf8cc35bdfffe807c7551a09c8d9efde8b228ee7203e01bad6174c2a1370"
},
{
"path": ".uai/README.md",
"template_id": "readme",
"source": "template:readme@1",
"bytes": 2036,
"sha256": "60c80e60333b5101c1f60c0d67738c2acf6f2a1de3075f036996f5fa86d394d8"
},
{
"path": "AGENTS.md",
"template_id": "agents-md",
"source": "template:agents-md@1",
"bytes": 1858,
"sha256": "0b69e407008a8bcb34bd7ac7cca7c21fb8e1d3cedc89e38b0f39804b38dbd7ef"
},
{
"path": ".uai/readme.human",
"template_id": "readme-human",
"source": "template:readme-human@1",
"bytes": 1139,
"sha256": "ae057765145681fda25012a9dbe705a1bb05cf6e7bc6638a86e6db6e52664aed"
},
{
"path": ".uai/overview.uai",
"template_id": "project-overview",
"source": "template:project-overview@1",
"bytes": 492,
"sha256": "39fa87d6ddcfd5060afdc9f223e3978d25544d43d6f6be690c01245ef03305ac"
},
{
"path": ".uai/current-state.uai",
"template_id": "current-state",
"source": "template:current-state@1",
"bytes": 325,
"sha256": "ea4124581f681c39c21f55f4a6172a1af2b48a13cb4a44d6951cfe63fb4c1462"
},
{
"path": ".uai/open-questions.uai",
"template_id": "open-questions",
"source": "template:open-questions@1",
"bytes": 382,
"sha256": "629fc8106161f23b5da9027a55078d16e9663ac44202ace5507fca766f260195"
},
{
"path": ".uai/next-actions.uai",
"template_id": "next-actions",
"source": "template:next-actions@1",
"bytes": 376,
"sha256": "09e1a5903710bf8d98febe30b35ac53d1a033a8cd61123165926c5723bbfd201"
},
{
"path": ".uai/risk-register.uai",
"template_id": "risks-and-constraints",
"source": "template:risks-and-constraints@1",
"bytes": 830,
"sha256": "8a35af3386d1f81160692a0691f31f6d80de71311ddbdeb55caa5fdf102da03b"
},
{
"path": ".uai/owners.uai",
"template_id": "contacts-and-owners",
"source": "template:contacts-and-owners@1",
"bytes": 283,
"sha256": "472c67e2d4bab2608eca127209ff669b692495d2e96326a63aeb305d5da6f54f"
},
{
"path": ".uai/agent-instructions.uai",
"template_id": "agent-instructions",
"source": "template:agent-instructions@1",
"bytes": 1019,
"sha256": "3945d08995ae18cb968beda0ca131f477e1ec594f3575e973a361305e5bc1944"
},
{
"path": ".uai/changelog.uai",
"template_id": "changelog",
"source": "template:changelog@1",
"bytes": 175,
"sha256": "8a1d064f7d02294329200521e29d6d5dc0961a9ba5fd44fa21e75b2af5dd2016"
},
{
"path": ".uai/deployment-memory-and-test-report.uai",
"template_id": "deployment-report",
"source": "template:deployment-report@1",
"bytes": 935,
"sha256": "dab28315ed510def2557450642658e7cec5de4d8a61ea7fc7c10ed9d165ad732"
},
{
"path": ".uai/context.uai",
"template_id": "uai-context",
"source": "template:uai-context@1",
"bytes": 285,
"sha256": "aa289be70b0aabadcab8d7a60fc906ddf465f7392580a9be278570cd45788661"
},
{
"path": ".uai/stack.uai",
"template_id": "uai-stack",
"source": "template:uai-stack@1",
"bytes": 204,
"sha256": "29f47ec11930fc90ba3c7ce77f37ae7b0638c12fd21a11ee897e93a366aea6f5"
},
{
"path": ".uai/architecture.uai",
"template_id": "uai-architecture",
"source": "template:uai-architecture@1",
"bytes": 278,
"sha256": "403282c4d3df335be44b4237bb258fcfb060f79569ff4ad3c1ba0959eee29d85"
},
{
"path": ".uai/constraints.uai",
"template_id": "uai-constraints",
"source": "template:uai-constraints@1",
"bytes": 520,
"sha256": "f0e8cd1948b215fae8fc97681c8348391b7d1a47a04444e1b936f716efd36853"
},
{
"path": ".uai/progress.uai",
"template_id": "uai-progress",
"source": "template:uai-progress@1",
"bytes": 188,
"sha256": "c47bf1fe21e9b1ca62d0c33de793f052252b499fcf78f9228ee1253a97e1fc50"
},
{
"path": ".uai/operations.uai",
"template_id": "uai-operations",
"source": "template:uai-operations@1",
"bytes": 323,
"sha256": "223ce4881883ee576721885162e6948285be16ad277fb4b95618aca87e2d85af"
},
{
"path": ".uai/test-plan.uai",
"template_id": "uai-test-plan",
"source": "template:uai-test-plan@1",
"bytes": 395,
"sha256": "087ac4dfc7daf2d0628cb5fc1c5079030f57024cc618f2d5ac37d0590c903322"
},
{
"path": ".uai/style.uai",
"template_id": "uai-style",
"source": "template:uai-style@1",
"bytes": 331,
"sha256": "b130ec2dbd3e0f3626cc145bc758fd7e4ce4b18c2502960608de5513f20f3209"
},
{
"path": ".uai/coding-standards.uai",
"template_id": "uai-coding-standards",
"source": "template:uai-coding-standards@1",
"bytes": 2047,
"sha256": "9e82c8ea5fdf8b95459824cb503a505155e40301a729281d8fabfb9ea630da42"
},
{
"path": ".uai/decisions.uai",
"template_id": "uai-decisions",
"source": "template:uai-decisions@1",
"bytes": 150,
"sha256": "7d5dca211562cbd843d0428ea3d5cceadb4c58967363caaefa6a41f34bea0286"
},
{
"path": ".uai/memory.uai",
"template_id": "uai-memory",
"source": "template:uai-memory@1",
"bytes": 1161,
"sha256": "3ee2bc2965c6676d1dd0ecfeb500d3fb3bc2012f70a3e85ec70d94c120c057e6"
},
{
"path": ".uai/next-recursive-prompt.uai",
"template_id": "uai-next-recursive-prompt",
"source": "template:uai-next-recursive-prompt@1",
"bytes": 9825,
"sha256": "2596c4c316e048b261626a4584fa2d3b93d6254b101353882e7e6f3939dbd99e"
}
]
}
.uai/memory-maintenance.uai
---
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, protected paths, review gates, validation behavior, and memory write safety.
## Lifecycle
- States: capture, review, promote, compact, archive, retire.
- 热记忆 memory: `.uai/short-term-memory.uai`, `.uai/progress.uai`, active task files, and files named by the current manifest for the declared package scope.
- 冷记忆 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.
## Access Control
- Read this file before broad memory loading.
- Apply protected path guards before scans, validation, indexing, package generation, exports, or memory compaction.
- Suggestions are allowed; action is forbidden without direct authorization for protected artifacts.
- General approval, broad review, default generation, validation, linting, indexing, export, or packaging permission is not authorization for protected artifacts.
## Protected Paths
These paths are optional and protected when present. Agents may refer to this metadata, but must not read, open, validate, lint, create, modify, package, export, index, inspect, or infer from the protected artifacts unless a human directly names the exact artifact and exact operation.
- path: `.uai/taboo.uai`
aliases: `taboo.uai`
presence: optional
protected_when_present: true
access: operator_explicit_only
agent_default: forbidden
include_in_package: false
include_in_export: false
scan: false
validate: false
lint: false
index: false
- path: `.uai/totem.uai`
aliases: `totem.uai`
presence: optional
protected_when_present: true
access: operator_explicit_only
agent_default: forbidden
include_in_package: false
include_in_export: false
scan: false
validate: false
lint: false
index: false
- path: `.uai/talisman.uai`
aliases: `talisman.uai`
presence: optional
protected_when_present: true
access: operator_explicit_only
agent_default: forbidden
include_in_package: false
include_in_export: false
scan: false
validate: false
lint: false
index: false
## Enforcement
Missing or invalid `.uai/memory-maintenance.uai` is a package, validation, deployment, and startup failure. Any generated package that includes protected artifacts, treats protected artifacts as required, or scans them without exact human authorization is non-compliant..uai/identity.uai
---
uai: "1.0"
type: identity
status: draft
---
# 身份
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 边界
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
---
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/short-term-memory.uai
---
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.
## 当前 Focus
- 当前 task:
- 当前 blocker:
- 当前 owner:
- 当前 evidence ledger:
## Required Read Set
- `AGENTS.md`
- `.uai/memory-maintenance.uai`
- Apply the protected-path guard before loading broad memory. Do not read, open, validate, lint, create, modify, package, export, index, inspect, or infer from `.uai/taboo.uai`, `.uai/totem.uai`, or `.uai/talisman.uai` unless a human directly names the exact artifact and exact operation.
- `.uai/identity.uai`
- `.uai/world-context.uai`
- `.uai/startup-packet.uai`
- `.uai/system-profile.uai`
- `.uai/receiver-brief.uai`
- `.uai/index.md`
- `.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, 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 named long-term wiki/archive or `.uai/archives/` evidence, 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 记忆, agent communication, capability description, handoff structure, privacy, accessibility, analytics, or support claims. Use UAIX Principles Charter at `/en-us/governance/principles/`, Principles Role Guidance at `/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..uai/README.md
# Project AI 记忆
This starter bundle is a UAI AI 记忆配置. It keeps portable, human-readable context in files that another person, team, or AI 代理 can inspect before acting.
## 数据包 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.
## 信任 边界
内部 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/short-term-memory.uai`
- `.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
# My Project AI 记忆
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 记忆 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
# My Project 人类简报
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 记忆`.
- The trust boundary is: 内部 or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent.
## Things The AI Will Defend
- 当前 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
# Project Overview
## Purpose
Describe what the project exists to do, who it serves, and what outcome matters most.
## 当前 Scope
- In scope:
- Out of scope:
- 当前 public or operational surface:
## Source Of Truth
- Code:
- Docs:
- Machine artifacts:
- 发布版本 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
# 当前 State
## What Is True Now
- Live or supported now:
- Experimental now:
- 已计划 but not supported:
## Recently Changed
- YYYY-MM-DD:
## Active Work
- 当前 focus:
- Active owner:
- Targeted checks:
## Stale Or Risky Context
List anything that should not be trusted without rechecking..uai/open-questions.uai
# Open Questions
Use this file for questions that should block, steer, or qualify future work.
| Question | Why It Matters | Owner | Needed By | 状态 |
|---|---|---|---|---|
| | | | | 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
# 下一步 Actions
Keep this file current and actionable. Remove completed work or move meaningful completions to `.uai/changelog.uai`.
## Now
- [ ]
## 下一步
- [ ]
## 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
# 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.
## 信任 边界
内部 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:
- 内部-only strategy:
- Agent permissions:
## Redaction 检查list
- [ ] Secrets removed.
- [ ] Customer data removed or approved.
- [ ] 内部-only strategy removed or approved.
- [ ] Public claims checked against evidence..uai/owners.uai
# 联系s And Owners
Do not add private personal data unless the bundle's trust boundary allows it.
| Area | Owner | Backup | 联系 Method | Notes |
|---|---|---|---|---|
| Project | | | | |
| Security or privacy review | | | | |
| 发布版本 approval | | | | |.uai/agent-instructions.uai
# 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
# 变更日志
Record meaningful bundle changes so future readers can tell when memory moved.
## YYYY-MM-DD
- Change:
- Why it matters:
- Files updated:
- 检查s run:.uai/deployment-memory-and-test-report.uai
# 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.
## 发布版本
- Version:
- 生成时间 UTC:
- 发布版本 owner:
- Deployment target:
## 热记忆 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:
## 冷记忆 Or Archive 证据
- Destination path:
- Source paths preserved:
- 检查sums or identity evidence:
- Actor and timestamp:
- Promotion or disposition notes:
## Test Run Report
- 检查s run:
- 检查s skipped:
- 失败s or blockers:
- Package or artifact paths:
- Rollback or follow-up owner:.uai/context.uai
---
uai: "1.0"
type: context
status: draft
---
# Context
This project uses UAI AI 记忆 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
---
uai: "1.0"
type: stack
status: draft
---
# Stack
## Runtime
- Language:
- Framework:
- Package manager:
- Database or storage:
## Commands
- Install:
- Run:
- Test:
- 发布版本:.uai/architecture.uai
---
uai: "1.0"
type: architecture
status: draft
---
# Architecture
## System Shape
Describe main surfaces, services, packages, routes, jobs, data stores, and ownership boundaries.
## Drift Risks
- Duplicated copy:
- 生成时间 output:
- Manual release steps:.uai/constraints.uai
---
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
---
uai: "1.0"
type: progress
status: draft
---
# Progress
## Recently Completed
- YYYY-MM-DD:
## 当前 Focus
-
## 下一步 Work
-
## Blockers
- None recorded..uai/operations.uai
---
uai: "1.0"
type: operations
status: draft
---
# Operations
## Normal Workflow
1. Load AI 记忆 files.
2. Inspect relevant code or docs.
3. Make narrow changes.
4. Run targeted checks.
5. Update memory when project truth changes.
## 发布版本 Workflow
- Package command:
- Smoke test:
- Rollback:.uai/test-plan.uai
---
uai: "1.0"
type: test-plan
status: draft
---
# Test Plan
## 默认 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 检查 Cannot Run
State the command, why it could not run, and what risk remains..uai/style.uai
---
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
---
uai: "1.0"
type: coding-standards
status: draft
---
# Coding Standards
This file is required for code-capable 项目交接 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.
- If the project is new, create an initial standard from the selected language, framework, package manager, test runner, deployment target, and owner instructions.
## Required 默认s
- 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
---
uai: "1.0"
type: decisions
status: draft
---
# Decisions
Record accepted decisions, why they were made, and what would cause a reversal..uai/memory.uai
---
uai: "1.0"
type: memory
status: draft
---
# AI 记忆
AI 记忆 is durable, reviewable context that lets a future AI continue useful work without relying on private chat history.
## 数据包 Configuration
- 数据包: Project AI 记忆
- 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.
- 信任 boundary: 内部 or controlled collaboration by default. Review before sharing externally or giving to an autonomous agent.
## UAI AI 记忆 And LLM Wiki
Use UAI AI 记忆 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. 提升 accepted project truth into AI 记忆, canonical docs, code, tests, release notes, or roadmap state.
4. Keep unreviewed material out of governing instructions..uai/next-recursive-prompt.uai
{
"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": "next-recursive-prompt.uai is required for agents that deal with code, automation, executable workflows, or code-like artifacts. It is not required for agents that don't deal with any coding.",
"out_of_scope_rule": "next-recursive-prompt.uai is not required for agents that don't deal with any coding.",
"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 代理文件交接, 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, and archive movement 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 detailed suggested next prompt to the human in chat so they can review, modify, or simply answer keep going. The prompt should name context, objective, scope, hard boundaries, expected touchpoints, targeted checks, and done criteria.",
"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."
},
"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 no-change evidence", "tests and skipped checks with reasons", "blockers or support-boundary risks", "next_detailed_suggested_prompt"],
"next_detailed_suggested_prompt_requirements": ["context", "objective", "scope", "hard boundaries", "expected touchpoints", "targeted checks", "done criteria"],
"user_choice": "The human can edit the prompt, replace it, or answer keep going."
},
"prompt": "Continue from this UAIX package when the user asks to continue, keep going, do the next thing, resume, or gives a directly related request. Read authoritative_refs first, treat .uai/next-recursive-prompt.uai as derived hot-memory only, use relevant plan ideas, and enumerate active 文件交接 intake; related intake supersedes or expands the stored loop and still requires project work before archive movement. Perform the next safe work chunk, run targeted checks, update .uai memory, regenerate this file from authoritative records, and provide a detailed suggested next prompt for the human to review, modify, or continue from. If the user gives a specific unrelated request, follow the current user instruction and regenerate this file after accepted work.",
"ordered_steps": [
"Read AGENTS.md and .uai/memory-maintenance.uai before broad memory loading.",
"Apply the protected-path guard from .uai/memory-maintenance.uai; do not read, scan, validate, lint, create, modify, package, export, index, inspect, or infer from protected operator-only artifacts without exact human authorization.",
"Read the remaining ordinary .uai files named in authoritative_refs for the declared package scope.",
"Review .uai/next-recursive-prompt.uai for relevant ideas when the current request continues, resumes, or directly relates to the stored next loop.",
"When 代理文件交接 is enabled, enumerate active Content and Improvement files; related intake supersedes or expands this next loop and must produce project work before archive movement.",
"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, tests, blockers, and the next recursive work prompt.",
"End the final response with a detailed suggested next prompt the human can review, modify, or answer with keep going."
],
"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"],
"not_required_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 记忆 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 记忆
- Project overview, current state, decisions, open questions, next actions, risks, constraints, owners, glossary, and agent instructions.
- Root
AGENTS.mdplus local memory files such as.uai/readme.humanwhen agents need a predictable load path. - Typed
.uaifiles 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 信任 Boundaries
Choose the bundle by trust boundary, not by name alone. 内部 Project AI 记忆 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 记忆 is not a dumping ground. Keep high-churn files current and keep durable files stable. .uai/CURRENT_STATE.md and .uai/NEXT_ACTIONS.md can change often. .uai/DECISIONS.md should be append-first or carefully revised. .uai/RISKS_AND_CONSTRAINTS.md and .uai/AGENT_INSTRUCTIONS.md should be reviewed whenever permissions, production boundaries, support claims, or safety posture change. .uai/CHANGELOG.md 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 记忆
- 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 站点, 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 站点s 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 站点s 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 记忆 And LLM Wiki
LLM Wiki is not required by UAI specs or 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 记忆 and LLM Wiki solve different memory problems. UAIX AI 记忆 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 记忆 bundles as portable snapshots, working context, onboarding exports, handoff packets, audit packets, or agent-run context.
When To Use UAIX AI 记忆
- Use Project AI 记忆 when a project is active and context needs to persist across sessions.
- Use 项目交接 when ownership, execution, or responsibility is moving.
- Use Agent Session Memory when an AI 代理 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 记忆, docs, code, tests, release notes, roadmap state, or public evidence.
When To Use 两者都要
Use both when a durable knowledge base needs portable working packets. The LLM Wiki remains expansive; the AI 记忆 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 将 UAI 包与 LLM Wiki 配合使用 and 项目交接 上下文预算. For the longer rationale, read LLM Wiki vs. UAIX 项目交接 and LLM Wiki and UAIX 项目交接.
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 路由 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.
Related UAIX Records
- 将 UAI 包与 LLM Wiki 配合使用Practical page for routing compact UAI packages beside deep wiki memory.
- 项目交接 上下文预算Run the hot/cold memory maintenance loop before startup context bloats.
- 项目交接The transfer subtype of UAI AI 记忆.
- AI 记忆数据包向导Guided package model, system profile, receiver brief, startup packet, copy-paste files, overlay JSON, LLM Wiki 计划 required for LLM Wiki configuration, readiness checks, and canonical ZIP links.
- 代理文件交接Chat-start intake for dropped files before broad work continues.
- AGENTS.md .uai Linking 规范ificationLink syntax, loader behavior, and typed-file background.
- UAI-1The public exchange and evidence contract when memory becomes interoperability evidence.
- 验证器证据 path for public UAI-1 claims.
- LLMWikis.orgDeep LLM Wiki memory for durable organizational knowledge.
- 路线图当前 versus planned tooling boundaries.
- 变更日志Dated public change trail.