Project Handoff

How to use this page

Use this practical start page to create portable project memory that OpenAI, Codex, Claude, local agents, humans, vendors, teams, and future sessions can load before work and update after work.

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.

Continue the handoff

OpenAI Handoff Guide Context Budget Guide UAI Memory Management UAI-1

Project Handoff

Portable project memory for humans and AI agents

Use this draft format when a repository needs durable AI-readable context that OpenAI, Codex, Claude, local agents, vendors, human teams, and future sessions can load before work and update after accepted work. .uai/memory-maintenance.uai, .uai/identity.uai, .uai/world-context.uai, .uai/totem.uai, .uai/taboo.uai, .uai/talisman.uai, .uai/startup-packet.uai, and .uai/progress.uai travel beside Project Handoff memory as local launch-baseline files; project/developer packages also require .uai/coding-standards.uai, .uai/architecture.uai, and .uai/next-recursive-prompt.uai.

Root File

AGENTS.md coordinates the handoff

The root file summarizes current state, loaded context, next steps, open questions, recent agent history, and constraints without becoming a research archive.

Human Briefing

.uai/readme.human tells people what to clarify

The local .uai human briefing explains what the AI needs humans to know, what it will defend, and which assumptions are unsafe.

Context Files

.uai files split durable knowledge

Typed files keep current stack, architecture, decisions, constraints, progress, operations, test plan, style, startup read order, file handoff, and intake state in one predictable .uai/ folder beside the repo.

Required Coding Standards

Required for Project Handoff and code-bearing packages: standards, architecture, and next prompt

Project/developer packages and packages that declare code-like artifacts must include coding standards, architecture.uai, and next-recursive-prompt.uai. A programming agent must inspect the codebase, infer applicable language/framework/data/API/security profiles and architecture boundaries, preserve the good parts, require DRY, once-and-only-once, SOLID, and automated tests, use the recursive prompt only for continuation or directly related requests, and record blockers when standards, architecture evidence, or checks are missing.

Required Local Files

Memory-maintenance protects the load path

Read .uai/memory-maintenance.uai before broad local memory loading, then load identity, world-context, Totem, Taboo, Talisman, startup-packet, progress, and the declared typed package files. Totem, Taboo, and Talisman are default read-and-obey anchors; agents may suggest or ask permission for changes, but must not modify, weaken, replace, delete, or bypass any of those files without exact artifact-and-operation authorization.

References

@uai[] tells the next AI what to load

References make the required context explicit before the next assistant starts editing code, copy, or release evidence.

Cold Memory

Long history stays outside the startup path

Archive old progress detail, research, and pre-slim snapshots in an LLM Wiki or AIWikis-style memory layer, then leave a concise pointer in the handoff bundle.

Guardrails

Runtime separate from memory

OpenAI runs the agents. Project Handoff gives harnesses bounded input before work and a reviewable write-back target after accepted work, with human approval required for high-impact actions.

Continue the handoff

OpenAI Handoff GuideUse Project Handoff beside OpenAI Agents and Codex.Context Budget GuidePrevent AGENTS.md and .uai records from turning into archives.UAI Memory ManagementWordPress admin package for inspecting .uai, Advanced Persona, docs/wiki roots, stale-memory warnings, and update prompts.UAI-1Public message and evidence envelope.Adoption KitStarter proof bundle for UAI-1 onboarding.ValidatorCheck release-facing UAI-1 records.Standards FitBoundary between UAI-1 and adjacent protocols.AGENTS.md SpecPublic link syntax and .uai reference proposal.Refining ReportBackground architecture, validation, and security analysis.ReportsPermanent source-note report index.

Onboarding promptGive this to the next AI

You are joining an existing project. Before doing anything else:

1. Read AGENTS.md in the project root.
2. Read .uai/readme.human.
3. Load every file listed under Loaded Context using the @uai[] references.
4. Report missing, contradictory, or oversized hot-context files; use cold-memory pointers only when the task needs old evidence.
5. Read the Handoff Summary, Current State, and Next Steps sections.
6. Summarize your understanding in 3-5 bullet points.
7. Confirm the hard constraints from constraints.uai.
8. Name the files, routes, or docs you expect to touch.
9. If code may change, read or create .uai/coding-standards.uai and .uai/architecture.uai, confirm .uai/next-recursive-prompt.uai is present for code-bearing scope, infer the applicable language/framework profiles and architecture boundaries from the codebase, use the recursive prompt for continuation or directly related requests, enumerate related active File Handoff intake because intake supersedes or expands the stored loop, and map automated checks before editing.
10. Name the targeted checks you expect to run and whether full release or package checks are out of scope.
11. Then ask what we are working on today.

Do not skip steps 1-10 or begin coding before completing them.

This prompt makes the handoff behavior explicit even when the model has never seen the project before.

Project Handoff is portable project memory for humans and AI agents. It helps humans and AI agents transfer project state without relying on private chat history.

It gives OpenAI, Codex, Claude, local agents, vendors, and human teams a shared repo-local starting point: what this project is, what changed, what constraints matter, what decisions were made, and what must be verified before the next edit.

OpenAI runs the agents. Project Handoff preserves the project memory.

Project/developer packages also require .uai/coding-standards.uai. Before coding, the receiving agent must infer applicable language/framework/data/API/security profiles from the visible codebase, manifests, tests, CI, deployment files, routes, schemas, and owner instructions, then map automated checks before editing.

What This Is / What This Is Not

What Project Handoff is What Project Handoff is not

What Project Handoff is	What Project Handoff is not
Project Handoff is a portable repository-context standard for transferring work between AI models, agent systems, vendors, internal teams, companies, and future sessions of the same project. It defines durable files such as `AGENTS.md`, `readme.human`, and typed `.uai` records for context, stack, architecture, constraints, decisions, progress, errors, prompts, and verification.	Project Handoff is not an OpenAI replacement, an agent scheduler, a runtime orchestrator, a competing tool-calling framework, a private memory store, or a chat transcript archive. It is the source-of-truth project brief that orchestrators can load before they act and update after they finish.

Project Handoff is a portable repository-context standard for transferring work between AI models, agent systems, vendors, internal teams, companies, and future sessions of the same project.

It defines durable files such as AGENTS.md, readme.human, and typed .uai records for context, stack, architecture, constraints, decisions, progress, errors, prompts, and verification.

Project Handoff is not an OpenAI replacement, an agent scheduler, a runtime orchestrator, a competing tool-calling framework, a private memory store, or a chat transcript archive.

It is the source-of-truth project brief that orchestrators can load before they act and update after they finish.

Hot Context, Cold Memory

Project Handoff should be hot context: current truth, current constraints, accepted decisions, active blockers, next work, and checks. It should not become the place where every research report, old session note, or historical roadmap paragraph is loaded by default.

When a handoff bundle grows too large, preserve the pre-slim files in an LLM Wiki or AIWikis-style cold memory layer with a manifest, source paths, checksums, summaries, and a dated log. Then keep the active AGENTS.md, readme.human, and .uai files concise and point to cold memory only when the task needs original evidence.

AI Dreaming Memory Frameworks

In UAIX guidance, AI Dreaming Memory is a selected reviewed consolidation pass over visible project memory. It can reread recent handoff files, accepted intake outcomes, evidence ledgers, and named cold-memory archives to propose duplicate merges, stale-fact pruning, contradiction notes, next-action updates, and hot/cold memory changes.

A dreaming pass should produce proposed deltas, not silent truth. Record the input scope, prompts or job settings, redactions, before/after memory summary, accepted and rejected changes, reviewer, checks, archive path, and rollback snapshot in Project Handoff or the selected evidence ledger.

Use it for: periodic memory hygiene, release-bound memory review, contradiction discovery, source-preserving summaries, and handoff readiness checks.
Do not use it for: hidden model memory, model-weight updates, unsupervised private-data processing, automatic repository writes, automatic LLM Wiki sync, or public support claims without review.
Promotion rule: a dream output becomes operational only when its accepted slice is written into AGENTS.md, readme.human, typed .uai records, docs, code, tests, release notes, roadmap state, changelog, machine artifacts, or long-memory evidence.

Production Deployment Memory Sorting

Production deployment builds and release packages are the right moment to run memory management. Before calling a deployment complete, update hot memory with the current deployed truth, the workspace-version authority pointer, changed files, checks run, blockers, owners, and next actions. Keep exact current and next package-version values in the root workspace.uai coordinator and release evidence, not in active project or plugin .uai memory. Move bulky history, old reports, raw sources, stale plans, and background or rejected rationale into the named LLM Wiki, AIWikis-style archive, or cold-memory path when one exists with transfer evidence. Write a durable deployment memory and test run report beside the release artifacts or in the selected evidence ledger; a chat-only final note is not enough.

Do not run that pass for ordinary dev builds, test runs, local package experiments, or smoke checks unless a human explicitly marks the build as release-bound or a release candidate.

How It Fits With OpenAI, Codex, Skills, MCP, And Agent Runtimes

Agent runtimes are built to execute work: choose tools, call APIs, apply approvals, delegate between specialists, preserve run state, and produce traces or pull requests. Project Handoff lives one layer earlier and one layer later. It tells the runtime what durable project memory to load before work starts, and it gives humans a reviewable place to write back the accepted result after work finishes.

Project Handoff is the bounded input and write-back surface for harness engineering: load the current spec, constraints, owners, checks, and support boundaries before a run; after review, write back only accepted decisions, changed files, test or eval results, blockers, page digests, adoption signals, and next actions.

Use OpenAI, Codex, Skills, MCP servers, Claude, local agents, or other orchestration systems to run the work. Use Project Handoff to make sure those systems start with the right project memory, constraints, decisions, and verification plan.

OpenAI Runtime Orchestration Vs Project Handoff

Layer	OpenAI Agents / Codex / orchestration	UAIX Project Handoff
Runtime execution	Strong	Not the goal
Agent-to-agent delegation	Strong	Not the main layer
Tool calls and approvals	Strong	Defines repo-side policy inputs
Session memory	Strong inside the platform	Portable outside the platform
AGENTS.md project guidance	Supported	Uses it as the front door
Human briefing	Runtime or workflow dependent	`readme.human`
Typed project records	Runtime-specific configs and traces	`.uai` records
Vendor portability	Partial	Core purpose
Audit-friendly project state	Runtime traces	Repo-local handoff artifacts
Best use	Run the work	Preserve and transfer the context

Use OpenAI to run agents. Use Project Handoff to make sure those agents start with the right project memory, constraints, decisions, and verification plan.

Minimum Handoff Bundle

Code example

my-project/
AGENTS.md
readme.human
.uai/
  context.uai
  stack.uai
  constraints.uai
  progress.uai
  test-plan.uai

AGENTS.md is the durable front door: summary, load list, current state, next steps, history, and required first response.
readme.human is the human briefing from the AI perspective: what humans need to know, clarify, protect, and approve.
.uai/context.uai explains what the project is, who it serves, and what success means.
.uai/stack.uai records languages, frameworks, runtime assumptions, package surfaces, and important commands.
.uai/constraints.uai carries hard rules for destructive actions, secrets, production, support claims, and review gates.
.uai/progress.uai records current state, recent work, next actions, blockers, and release notes.
.uai/test-plan.uai is selected for the smallest projects and expected when verification choices matter.

Active File Intake

Real projects also receive loose files: PDFs, notes, exported chats, research memos, package ZIPs, screenshots, spreadsheet evidence, and drafts from other AI systems. Pair Project Handoff with Agent File Handoff when those files should be visible during AGENTS.md load.

On load: directly enumerate agent-file-handoff/Content/ and agent-file-handoff/Improvement/, and inspect every non-placeholder active file before unrelated broad work. Do not create or rely on an intake-index file.
Work rule: for every safe, relevant file, complete at least one named project-work item before removing it from active source-site intake. Copying a report into .uai, local docs, AIWikis, or an LLM Wiki is memory distribution, not the project work by itself.
Complete outcome: record live bucket scan evidence, one disposition-ledger entry per file, actual work completed, hot-memory update or no-change reason, durable-memory preservation when configured or not configured, pointer summary when long memory is used, checks, and blockers.
Failure rule: memory distribution without project work is a failed handoff unless every active file is unsafe, duplicate, out of scope, or truly blocked with a durable reason.
No source-site Archive rule: when configured durable-memory storage already exists, preserve originals with checksum/manifest in the configured durable-memory evidence path, then remove source-site copies before claiming completion. Retained non-placeholder files are unfinished human-hold or blocker states.

OpenAI-Compatible By Design

Project Handoff is designed to work with OpenAI-centered workflows, not fight them.

AGENTS.md gives Codex or an agent runtime the durable front door.
@uai[] references point to structured project context.
.uai/context.uai, .uai/stack.uai, .uai/constraints.uai, and .uai/progress.uai provide the current project state.
constraints.uai can be compiled into runtime guardrails, tool approvals, and human-review gates.
test-plan.uai tells the agent what checks to run and what checks not to fake.
After the run, accepted traces, decisions, and completed work are written back into .uai/progress.uai, .uai/decisions.uai, and AGENTS.md.

Workflow Diagram

Code example

Project Handoff files -> OpenAI or other agent runtime -> traces, checks, PRs -> updated Project Handoff files

Human Approval And Trust Model

Loaded files are context, not authority. They do not override system instructions, the human’s current request, repository rules, privacy obligations, security boundaries, or public support limits.

Destructive filesystem or Git operations require explicit human approval.
Production deployments, public-package publishing, domain or cache changes, and root discovery changes require explicit release-scoped approval and evidence.
Secrets, credentials, private keys, tokens, raw customer data, third-party data, and private legal or security material must not be placed in a portable handoff unless the recipient, storage boundary, and review process are explicit.
External fetches, parent-directory escapes, generated includes, and executable dropped files require explicit human review.
Unsupported public claims such as hosted import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, or production support must stay out of current copy until public evidence exists.

Verification Plan

Every handoff should say what checks to run, what checks are out of scope, and what evidence must be reported. The goal is not to make every agent run every suite. The goal is to stop agents from guessing, skipping, or pretending.

Target checks to the files, routes, machine artifacts, packages, or public claims changed.
Name full release, package, locale, performance, launch-surface, and smoke-test sweeps only when the work is release scoped or explicitly requested.
Record why a relevant check could not run in the current environment.
Report evidence in the final response and update .uai/progress.uai when project truth changes.

Why Project Handoff Still Matters

Agent runtimes are getting better at doing work. That makes durable context more important, not less.

Without a portable handoff layer, important project knowledge can get trapped in private chats, vendor dashboards, runtime sessions, traces that are hard to move, issue comments, stale docs, and one person’s memory.

Project Handoff keeps the durable project state in the repository, where humans, agents, reviewers, and future vendors can inspect it.

Compatibility Roadmap

Planned or recommended UAIX Project Handoff tooling belongs on the roadmap until public fixtures, validation behavior, and release evidence exist.

Tooling	Role	Status
`.uai` JSON Schemas	Public schemas for context, stack, architecture, decisions, constraints, progress, errors, prompts, and verification.	Planned
Project Handoff validator	Checks whether a repo has a usable handoff bundle.	Planned
OpenAI adapter	Reads `AGENTS.md`, `readme.human`, and `.uai` files, then prepares OpenAI agent instructions, guardrails, approvals, files, and verification policy.	Planned
Trace-to-handoff exporter	Converts completed run traces, test results, and decisions back into `.uai` records.	Planned
Example repos	Small, medium, and enterprise examples across OpenAI, Claude, local agents, and human teams.	Planned
Conformance tests	A public suite proving that a handoff bundle is portable and self-sufficient.	Planned

Live Starter Bundle

AI Memory is the broad public framing, and Project Handoff is the transfer configuration for repository takeover or responsibility movement. This starter ZIP is generated on demand from the same canonical template registry and generated-manifest path used on the AI Memory page.

31 files uai-project-handoff-starter.zip Bundle ID project-handoff Manifest fingerprint 693f002710f05fb4

.uai/exports/manifest.json

Code example

{
    "bundle_id": "project-handoff",
    "name": "Project Handoff",
    "description": "A transfer packet for moving execution, ownership, or responsibility to another human, team, agent, or vendor.",
    "intended_use_case": "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.",
    "download_filename": "uai-project-handoff-starter.zip",
    "display_order": 20,
    "trust_boundary_notes": "Can be internal or external, but external handoffs must be sanitized and approved before sharing.",
    "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/progress.uai",
        "README.md",
        "AGENTS.md",
        ".uai/readme.human",
        ".uai/overview.uai",
        ".uai/open-questions.uai",
        ".uai/next-actions.uai",
        ".uai/risk-register.uai",
        ".uai/owners.uai",
        ".uai/agent-instructions.uai",
        ".uai/archives/changelog.uai",
        "reports/deployment-memory-and-test-report.uai",
        ".uai/context.uai",
        ".uai/stack.uai",
        ".uai/architecture.uai",
        ".uai/constraints.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",
        ".uai/handoff-brief.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-handoff"
    ],
    "universal_required_files": [
        ".uai/memory-maintenance.uai",
        ".uai/identity.uai",
        ".uai/world-context.uai",
        ".uai/totem.uai",
        ".uai/taboo.uai",
        ".uai/talisman.uai",
        ".uai/startup-packet.uai",
        ".uai/progress.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-handoff",
            "requirement": "Required for Project Handoff packages",
            "files": [
                "README.md",
                "AGENTS.md",
                ".uai/readme.human",
                ".uai/overview.uai",
                ".uai/open-questions.uai",
                ".uai/next-actions.uai",
                ".uai/risk-register.uai",
                ".uai/owners.uai",
                ".uai/agent-instructions.uai",
                ".uai/archives/changelog.uai",
                "reports/deployment-memory-and-test-report.uai",
                ".uai/context.uai",
                ".uai/stack.uai",
                ".uai/architecture.uai",
                ".uai/constraints.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",
                ".uai/handoff-brief.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/progress.uai",
        "README.md",
        "AGENTS.md",
        ".uai/readme.human",
        ".uai/overview.uai",
        ".uai/open-questions.uai",
        ".uai/next-actions.uai",
        ".uai/risk-register.uai",
        ".uai/owners.uai",
        ".uai/agent-instructions.uai",
        ".uai/archives/changelog.uai",
        "reports/deployment-memory-and-test-report.uai",
        ".uai/context.uai",
        ".uai/stack.uai",
        ".uai/architecture.uai",
        ".uai/constraints.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",
        ".uai/handoff-brief.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/progress.uai",
        "README.md",
        "AGENTS.md",
        ".uai/readme.human",
        ".uai/overview.uai",
        ".uai/open-questions.uai",
        ".uai/next-actions.uai",
        ".uai/risk-register.uai",
        ".uai/owners.uai",
        ".uai/agent-instructions.uai",
        ".uai/archives/changelog.uai",
        "reports/deployment-memory-and-test-report.uai",
        ".uai/context.uai",
        ".uai/stack.uai",
        ".uai/architecture.uai",
        ".uai/constraints.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": [
        ".uai/handoff-brief.uai"
    ],
    "configuration_sections": [
        "Add release evidence, validator output, or implementation records only when the handoff also carries public support claims."
    ],
    "overlays": [
        "The handoff overlay emphasizes acceptance criteria, owner transfer, and required first-response checks."
    ],
    "files": [
        {
            "path": ".uai/memory-maintenance.uai",
            "template_id": "uai-memory-maintenance",
            "source": "template:uai-memory-maintenance@1",
            "bytes": 4800,
            "sha256": "832eccecf3b88aeb432a4428957bd24cde43d1682d46199ca827f66e01dbcf14"
        },
        {
            "path": ".uai/identity.uai",
            "template_id": "uai-identity",
            "source": "template:uai-identity@1",
            "bytes": 2313,
            "sha256": "dae58a3f99eca679162387a633ea7a106d4c97827486a490e42c9c57b94ac6b9"
        },
        {
            "path": ".uai/world-context.uai",
            "template_id": "uai-world-context",
            "source": "template:uai-world-context@1",
            "bytes": 1794,
            "sha256": "53c42684ee4ac1d112c9e135569c18199242b4ea0bfbaea90fe9da1a63d3115c"
        },
        {
            "path": ".uai/totem.uai",
            "template_id": "uai-totem",
            "source": "template:uai-totem@2",
            "bytes": 8384,
            "sha256": "85815d98f44dbac2859514130f525de3081db2cd441aa4a7530de8b1c6877ace"
        },
        {
            "path": ".uai/taboo.uai",
            "template_id": "uai-taboo",
            "source": "template:uai-taboo@2",
            "bytes": 7146,
            "sha256": "6f91429685a0f30ed294405bf0693c03f25bb7d39748a67a607624e0967ca8e6"
        },
        {
            "path": ".uai/talisman.uai",
            "template_id": "uai-talisman",
            "source": "template:uai-talisman@2",
            "bytes": 1470,
            "sha256": "1652c2295fc9f4387813bf9c0347ef50bcd9306e5e2aa82f254b2937d9d4f8cc"
        },
        {
            "path": ".uai/progress.uai",
            "template_id": "uai-progress",
            "source": "template:uai-progress@1",
            "bytes": 246,
            "sha256": "386a536a146d392a23449e998467da16b1813ffb2629e21fdaf56c492a735c2b"
        },
        {
            "path": "README.md",
            "template_id": "readme",
            "source": "template:readme@1",
            "bytes": 2042,
            "sha256": "1b3e737001417fff26d4627cc4403020e243b9101d46acae567b12dba71d51c4"
        },
        {
            "path": "AGENTS.md",
            "template_id": "agents-md",
            "source": "template:agents-md@1",
            "bytes": 2228,
            "sha256": "3062f5f5f9ed186bdcb9ff2797e0944a3717bc83751da7399bc084d2c87d0af6"
        },
        {
            "path": ".uai/readme.human",
            "template_id": "readme-human",
            "source": "template:readme-human@1",
            "bytes": 1669,
            "sha256": "4ed0803cf8b6ceeba037d03262a2e75dcade47fd21f486868a1d38f40c96008d"
        },
        {
            "path": ".uai/overview.uai",
            "template_id": "project-overview",
            "source": "template:project-overview@1",
            "bytes": 492,
            "sha256": "39fa87d6ddcfd5060afdc9f223e3978d25544d43d6f6be690c01245ef03305ac"
        },
        {
            "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": 442,
            "sha256": "d7f1c27919d7401748e2c06c200383d99553e9b8fc15d4ada1553b027c91da26"
        },
        {
            "path": ".uai/risk-register.uai",
            "template_id": "risks-and-constraints",
            "source": "template:risks-and-constraints@1",
            "bytes": 812,
            "sha256": "416f636e595a74dafb4c6f5b1d89a1ed7c8ea29ae9663c498986b3b20743288c"
        },
        {
            "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": 1022,
            "sha256": "e6b30fee7775c10fda0a3defca19da6db1e8d6f6afcab7e61f32c062b94e2b01"
        },
        {
            "path": ".uai/archives/changelog.uai",
            "template_id": "changelog",
            "source": "template:changelog@1",
            "bytes": 175,
            "sha256": "8a1d064f7d02294329200521e29d6d5dc0961a9ba5fd44fa21e75b2af5dd2016"
        },
        {
            "path": "reports/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": 2212,
            "sha256": "7eea396ba0ffe8d1d5529756058962049f1fd6aeabed7ca42463d6f46fcc2174"
        },
        {
            "path": ".uai/constraints.uai",
            "template_id": "uai-constraints",
            "source": "template:uai-constraints@1",
            "bytes": 520,
            "sha256": "f0e8cd1948b215fae8fc97681c8348391b7d1a47a04444e1b936f716efd36853"
        },
        {
            "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": 2998,
            "sha256": "634c84dd59fc4f2c79bb8aeea3951e8d3011f8f1bd25f2410052603f50305a06"
        },
        {
            "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": 1434,
            "sha256": "acf429b528d9909a0494a9651f4d36a6a096a3d3f7d48e365f36e532489b2cb9"
        },
        {
            "path": ".uai/next-recursive-prompt.uai",
            "template_id": "uai-next-recursive-prompt",
            "source": "template:uai-next-recursive-prompt@1",
            "bytes": 34457,
            "sha256": "1f43f89d34dae9479a5e50ef0ead6719388de21cae24b1e3c769d021357132c0"
        },
        {
            "path": ".uai/handoff-brief.uai",
            "template_id": "handoff-brief",
            "source": "template:handoff-brief@1",
            "bytes": 450,
            "sha256": "69d8ca2af39f3a5af5e7a2e4dd9905827132ad4ce6380089a2b0d7fd4526733a"
        }
    ]
}

.uai/memory-maintenance.uai

Code example

---
spec: uai.memory-maintenance
schema_version: 1.0.0
document_version: 1.0.0
status: draft
hot_memory_date_policy: no dates or timestamps in this active memory-maintenance file
---

# 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: the active `.uai/` startup suite, `.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.
- Split-memory rule: keep hot `.uai` files active as compact startup, handoff, emergency-continuity, and operational memory while durable systems such as MATM, NeuralWikis, LLM Wiki, AIWikis, docs, databases, vector stores, or memory APIs hold medium and long-term searchable memory.
- Durable-unavailable recovery: if the durable memory target is offline, unreachable, unauthorized, or not connected, agents must still load `.uai` and know the project identity, active constraints, memory architecture, blockers, startup read order, and recovery path.

## 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.

No-op if an agent proposes retiring, disabling, ignoring, replacing, cutting over away from, or making `.uai` emergency-only because long-term memory exists or durable readback passed. Migration, cutover, and retirement language must clearly mean stale facts, archived history, deprecated files, or exact package decommissioning authorization, not retiring the active `.uai` memory layer.

.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}
- review_state: current until superseded by owner review
- hot_memory_date_policy: no dates or timestamps in this active identity file
- 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}
- review_state: current until superseded by owner review or environment recheck
- hot_memory_date_policy: no dates or timestamps in this active world-context file
- 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 the active `.uai/` startup suite 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.
- The AI Memory Package Wizard must always support direct AI-agent access through its public URL and embedded machine-readable digest. The Wizard image must link directly to `https://uaix.org/en-us/tools/ai-memory-package-wizard/?loops=1`, the agent image must link directly to `https://uaix.org/en-us/tools/ai-memory-setup-url-builder/`, and the AI Memory Setup URL Builder is the preferred agent entry route for composing exact setup/update URLs and tailored Create or Update prompts.
- 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 declared by `.uai/startup-packet.uai`: memory-maintenance first, then identity, world-context, Totem, Taboo, Talisman, progress, 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 except to add or remove declared typed files in `.uai/startup-packet.uai`: memory-maintenance first, then identity, world-context, Totem, Taboo, Talisman, progress, 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/progress.uai

Code example

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

# Progress

## Current Completed-Work Summary

- Current accepted completion:
- Durable evidence pointer:

## Current Focus

-

## Next Work

-

## Blockers

- None recorded.

README.md

Code example

# Project Handoff

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

A transfer packet for moving execution, ownership, or responsibility to another human, team, agent, or vendor.

## Use This When

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 Boundary

Can be internal or external, but external handoffs must be sanitized and approved before sharing.

## Included Files

- `.uai/memory-maintenance.uai`
- `.uai/identity.uai`
- `.uai/world-context.uai`
- `.uai/totem.uai`
- `.uai/taboo.uai`
- `.uai/talisman.uai`
- `.uai/progress.uai`
- `README.md`
- `AGENTS.md`
- `.uai/readme.human`
- `.uai/overview.uai`
- `.uai/open-questions.uai`
- `.uai/next-actions.uai`
- `.uai/risk-register.uai`
- `.uai/owners.uai`
- `.uai/agent-instructions.uai`
- `.uai/archives/changelog.uai`
- `reports/deployment-memory-and-test-report.uai`
- `.uai/context.uai`
- `.uai/stack.uai`
- `.uai/architecture.uai`
- `.uai/constraints.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`
- `.uai/handoff-brief.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-handoff`: A transfer packet for moving execution, ownership, or responsibility to another human, team, agent, or vendor.
- 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.

## UAIX Wizard Update URL

- Wizard update URL: https://uaix.org/en-us/tools/ai-memory-package-wizard/
- Use this exact route for package refreshes so the next agent preserves the setup mode that created this package.
- The wizard URL is update guidance only. It is not a hosted importer, automatic repository writer, certification, endorsement, or credential validator.

## 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

This active briefing is current-state memory. Dated evidence, dated headings, and timestamps belong in `.uai/archives/`, `reports/`, `docs/`, `.uai/exports/`, or a durable long-memory target.

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 Handoff`.
- The trust boundary is: Can be internal or external, but external handoffs must be sanitized and approved before sharing.

## UAIX Wizard Update URL

- Wizard update URL: https://uaix.org/en-us/tools/ai-memory-package-wizard/
- Use this exact route for package refreshes so the next agent preserves the setup mode that created this package.
- The wizard URL is update guidance only. It is not a hosted importer, automatic repository writer, certification, endorsement, or credential validator.

## 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/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/archives/changelog.uai`, `reports/`, `docs/`, or another durable evidence target.

## 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

Can be internal or external, but external handoffs must be sanitized and approved before sharing.

## 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 `reports/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/archives/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:

reports/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/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 Handoff
- Use case: Use when the next actor must take over a project safely and needs current state, constraints, decisions, checks, and ownership context.
- Trust boundary: Can be internal or external, but external handoffs must be sanitized and approved before sharing.

## UAI AI Memory And LLM Wiki

Use UAI AI Memory for compact, portable working packets. Use an LLM Wiki, NeuralWikis, AIWikis, docs, databases, or another durable system for deep, long-lived searchable memory.

Split Memory Architecture: keep hot `.uai` files active as compact short-term, startup, handoff, emergency-continuity, and operational memory. Durable memory augments `.uai`; it does not replace startup `.uai` memory or make `.uai` emergency-only after durable readback succeeds.

## 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.
5. Do not stop consulting active `.uai` files because a long-term memory plane exists.

.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",
    "review_state": "current until superseded by accepted work or human review",
    "hot_memory_date_policy": "no dates, timestamps, dated headings, chronological sections, or date-stamped package filenames in this active file",
    "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 before completion; retained files are unfinished human-hold or blocker states.",
    "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",
    "startup_memory_suite": ".uai/",
    "active_suite_read_order": ".uai/startup-packet.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",
    "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 the active .uai/ startup suite for current truth; .uai/startup-packet.uai is the read-order index.", "Do not create or load a single catch-all active memory file in place of typed .uai records.", "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 `.uai/progress.uai`, the relevant typed active `.uai` records, 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/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/startup-packet.uai", ".uai/progress.uai", ".uai/report-synthesis.uai when report or intake synthesis changes", ".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": []
  }
}

.uai/handoff-brief.uai

Code example

# Handoff Brief

## Transfer Context

- What is being transferred:
- From:
- To:
- Effective date:

## Acceptance Criteria

- The recipient can explain current state and constraints.
- Open questions are acknowledged.
- Required checks and next actions are clear.
- Trust-boundary and redaction review is complete.

## Handoff Risks

- Missing context:
- Unsupported claims:
- Sensitive material:
- Production or customer impact:

Plain-Language Summary

OpenAI is building better ways for AI agents to do work. That does not kill Project Handoff. It changes what Project Handoff should claim.

Project Handoff should not try to be an agent runner. It should be the thing that tells any agent: here is the project, here is what matters, here is what changed, here are the rules, here are the decisions already made, here is what you must verify, and here is what you are not allowed to do without a human.

OpenAI runs the work. UAIX Project Handoff preserves the project memory.

Current Support Boundary

This page publishes the draft AGENTS.md, readme.human, and .uai handoff pattern for public review and early use.
The visible starter ZIP is current and is generated from canonical templates and manifests.
Hosted .uai upload/import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, and endorsement support remain planned until public tooling, fixtures, validation behavior, and release evidence exist.
Do not describe a project as certified or endorsed by UAIX just because it uses AGENTS.md, readme.human, or .uai files.
When a handoff becomes public release evidence, attach the relevant Validator result, Conformance Pack evidence, Implementation record, and Changelog entry.

Long-running work

For extended or interruptible goals, use Long-Running Goal Execution. Follow Goals carries the runtime objective; authoritative .uai files carry durable checkpoints; UAI-1 task-status, blocker, handoff, memory-proposal, and final-report packets carry portable evidence. Runtime output is not accepted memory until reviewed and written back.

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.

Portable project memory for humans and AI agents

AGENTS.md coordinates the handoff

.uai/readme.human tells people what to clarify

.uai files split durable knowledge

Required for Project Handoff and code-bearing packages: standards, architecture, and next prompt

Memory-maintenance protects the load path

@uai[] tells the next AI what to load

Long history stays outside the startup path

Runtime separate from memory

Validator-backed proof path

Mandatory intake and protected authority#

What This Is / What This Is Not#

Hot Context, Cold Memory#

AI Dreaming Memory Frameworks#

Production Deployment Memory Sorting#

How It Fits With OpenAI, Codex, Skills, MCP, And Agent Runtimes#

OpenAI Runtime Orchestration Vs Project Handoff#

Minimum Handoff Bundle#

Active File Intake#

OpenAI-Compatible By Design#

Workflow Diagram#

Human Approval And Trust Model#

Verification Plan#

Why Project Handoff Still Matters#

Compatibility Roadmap#

Live Starter Bundle#

Project Handoff#

Plain-Language Summary#

Current Support Boundary#

Related Records#

Long-running work#

.uaix Package Format#

Agent Communication Operating Model#

Mandatory intake and protected authority

What This Is / What This Is Not

Hot Context, Cold Memory

AI Dreaming Memory Frameworks

Production Deployment Memory Sorting

How It Fits With OpenAI, Codex, Skills, MCP, And Agent Runtimes

OpenAI Runtime Orchestration Vs Project Handoff

Minimum Handoff Bundle

Active File Intake

OpenAI-Compatible By Design

Workflow Diagram

Human Approval And Trust Model

Verification Plan

Why Project Handoff Still Matters

Compatibility Roadmap

Live Starter Bundle

Plain-Language Summary

Current Support Boundary

Related Records

Long-running work

.uaix Package Format

Agent Communication Operating Model