Version localizada en revision
Esta pagina aun no esta disponible como norma localizada revisada. Use la fuente inglesa autoritativa para lenguaje normativo, interpretacion de esquemas, obligaciones de implementacion y limites de soporte.
Cómo usar esta página
Use this file detail page to confirm the exact required scope, review requirement, no-op trigger, and related .uai records before relying on the file in a package.
Required File Sets
Every .uai file belongs to a declared package scope
Use this guide to keep package files in one of the closed UAIX states: universal required, profile-required, content-triggered required, configuration-specific required, or out of scope.
Universal
Memory-maintenance travels first
.uai/memory-maintenance.uai, .uai/identity.uai, .uai/world-context.uai, .uai/totem.uai, .uai/taboo.uai, .uai/talisman.uai, and .uai/short-term-memory.uai are required for every launch-baseline UAIX memory or handoff package. Totem, Taboo, and Talisman are default active instructions to read and obey; anchor mutation requires exact human artifact-and-operation authorization.
Perfil
Declared package type controls the rest
Project Handoff, Agent File Handoff, Long-Term Memory, LLM Wiki, and release-bound packages each carry their own required file set.
No-code assistants
Coding standards stay out of scope until code-like work exists
.uai/coding-standards.uai, .uai/architecture.uai, and .uai/next-recursive-prompt.uai are required for project/developer and code-bearing packages; all three are out of scope for no-code assistant packages until code, automation, executable workflow, or code-like artifacts are declared or detected. For agents with no code, automation, executable workflow, or code-like artifacts, architecture.uai and next-recursive-prompt.uai are out of scope. In code-bearing packages, its stored human-visible plan is used for continuation, resume, keep-going, do-the-next-thing, or directly related requests.
Package memory path
Asistente de paquete de memoria de IAGenerate supported file sets from the canonical source rules.memory-maintenance.uaiUniversal lifecycle, protected-path, and memory-write safety policy.next-recursive-prompt.uaiCode-scope continuation prompt and derived hot-memory writeback policy.Traspaso de proyectoProject-startup package profile and read order.Traspaso de archivos de agenteLocal file intake, disposition, archive, and proof-of-use path.AGENTS.md SpecificationFront-door project guidance and local memory discovery.
universal required | profile-required | content-triggered required | configuration-specific required | out of scopeValidators and agents should rely only on files required for the declared package scope and ignore out-of-scope files as absent.