UAIX Alignment Review Of The ` Uaix` Draft

Your instinct about avoiding **“recommended”** and **“optional”** matches the way the current UAIX required-file guidance is structured. The stronger UAIX pattern is not just “make more things required”; it is a **clo...

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/raw-system-archives-uaix-agent-file-handoff-processed-2026-06-14-uaix-pa-bcfa4e5e/
Source reference	raw/system-archives/uaix/agent-file-handoff/processed-2026-06-14-uaix-package-format/Improvement/UAIX Alignment Review of the .uaix Draft.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-14T19:14:53.7761034Z
Content hash	sha256:bcfa4e5e14fbd5696613d764d67b660658c9a7ba2afac2572de5fc68215ab6f6
Import status	new
Raw source layer	data/sources/uaix/raw-system-archives-uaix-agent-file-handoff-processed-2026-06-14-uaix-package-format-improvement-bcfa4e5e14fb.md
Normalized source layer	data/normalized/uaix/raw-system-archives-uaix-agent-file-handoff-processed-2026-06-14-uaix-package-format-improvement-bcfa4e5e14fb.txt

Current File Content

Structure Preview

• UAIX Alignment Review of the .uaix Draft
• Executive assessment
• File-set and package-family mismatches
• Long-memory and archive model mismatches
• Security, authority, and import boundary gaps
• Packaging and support-claim mismatches
• Rewrite priorities

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 16234
• Preview characters: 11608

# UAIX Alignment Review of the `.uaix` Draft

## Executive assessment

Your instinct about avoiding **“recommended”** and **“optional”** matches the way the current UAIX required-file guidance is structured. The stronger UAIX pattern is not just “make more things required”; it is a **closed required-set model** that classifies files as **universal required**, **profile-required**, **content-triggered required**, **configuration-specific required**, or **out of scope**. The public `.uai` file guidance and the current wizard both use that family/profile/capability model rather than a flat “required vs optional” split. citeturn25view1turn25view2turn6view0

Because of that, the biggest problem in the draft is broader than wording. The draft turns UAIX into a small fixed container with a thin minimum file list, while current UAIX guidance treats package contents as a **declared, scope-sensitive file set** derived from bundle family, code-bearing status, long-memory configuration, file-handoff status, and other content facts. In its current form, the draft does not follow that model. citeturn16view1turn25view2turn27view2

A few parts of the draft do align with current UAIX direction: the local-first ZIP packaging idea, the insistence that a package be transferable without hosted services, and the statement that memory is not authority all fit the public UAIX posture. UAIX repeatedly describes AI Memory as a local, file-based, reviewable packet, and the Memory Firewall explicitly says imported memory is not permission to execute. citeturn7view1turn11view5turn16view1

## File-set and package-family mismatches

The single largest structural mismatch is the **minimum file set**. Your draft says a minimal `.uaix` package only needs a manifest plus `.uai/startup-packet.uai`, `.uai/system-profile.uai`, and `.uai/receiver-brief.uai`. Current UAIX guidance says every **launch-baseline** memory or handoff package requires `.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`. Those are not extras; they are the universal baseline. citeturn6view0turn6view3turn20view0turn25view1

That means your current “Recommended Files” section is misaligned in a deeper way than just vocabulary. In UAIX, `totem.uai`, `taboo.uai`, and `talisman.uai` are **default active instruction anchors** that agents must read and obey, and they must not be mutated except with **exact human artifact-and-operation authorization**. In your draft, those anchors are portrayed as files that “may be included” and were placed in the non-required bucket. That is a direct conflict with current public UAIX guidance. citeturn11view2turn12view4turn20view0

The draft also under-specifies **Project Handoff** and **code-bearing** scopes. The UAIX file guide marks `.uai/startup-packet.uai`, `.uai/system-profile.uai`, and `.uai/receiver-brief.uai` as **Required for Project Handoff packages**, while project/developer and code-bearing assistant packages also require `.uai/coding-standards.uai`, `.uai/architecture.uai`, and `.uai/next-recursive-prompt.uai`. Your draft mentions some of these files only as non-required material, instead of making them required when the package declares code, automation, executable workflows, or code-like artifacts. citeturn5view4turn5view5turn5view6turn7view3turn20view0

There is another important omission: the public wizard now treats **non-project assistant packages** as their own declared family. Those packages use assistant-specific files such as **assistant profile**, **relationship boundary**, **privacy boundary**, **user preferences**, and **memory-update rules**. Since your own examples include `HelpfulAssistant.uaix`, `PlaywrightExpert.uaix`, and `ShakespeareNovelist.uaix`, the draft is implicitly describing assistant-style packages, but it does not model their assistant-family required files at all. citeturn16view0turn20view0turn20view1turn20view3

The wizard also goes beyond family-based requirements and uses **content-triggered package facts**. Current UAIX package planning can make files required based on whether a package declares tool permissions, contact memory, calendar and scheduling memory, communication-style memory, tasks and commitments, routines and preferences, safety/support boundary memory, source notes, or public-facing behavior. Your draft has no mechanism for those triggers, so it cannot reproduce the current UAIX required-set logic for real assistant or office-style packages. citeturn25view2

## Long-memory and archive model mismatches

The draft’s long-memory model does not follow current UAIX layering. Public UAIX guidance treats **LLM Wiki** as a **deep-memory configuration path**, not a baseline part of every package. When a project uses that path, `.uai/long-term-memory.uai` becomes the active pointer file required for the long-memory configuration, but the wiki itself remains **background memory until reviewed and promoted** into accepted package surfaces. Your draft instead makes `.uai/wiki/docs/` the default expected long-term memory location inside the package and talks about it almost like a built-in source-of-truth layer. That blurs UAIX’s hot/cold boundary. citeturn21view0turn21view1turn27view2turn27view4

Current UAIX guidance is much more specific about what a long-memory path must name. When a package is shaped for an LLM Wiki, UAIX expects the package to record the approved **wiki root, index, log, steward, promotion targets, evidence log, and source boundary**. The guidance also says a new wiki root normally starts with a **read-only `raw/` layer** plus reviewed `wiki/index.md` and `wiki/log.md`. Your draft’s `portableWikiRoots` and `longTermMemory.defaultPath` fields are too thin to carry that UAIX routing model. citeturn21view0turn21view1turn8search2

The same issue appears in the shared-wiki section. UAIX says that when multiple source sites share one long-memory layer, records must preserve **source path, destination path, disposition, checksum, review state, promotion status, and owning site namespace**, and shared roots must keep ownership boundaries distinct instead of flattening all source material into one generic folder. A simple `"shared wiki docs folder used by multiple profiles"` is not enough to match that guidance. citeturn21view1

Your archive/content-type rules are also too restrictive for current UAIX practice. The draft says recommended allowed extensions are `.uai`, `.json`, `.md`, and `.txt`, but current UAIX file-handoff guidance explicitly operates on **PDFs, screenshots, exports, ZIPs, spreadsheets, and other loose files** as reviewable source/input material. That matters because your own draft describes `archives/` as “raw or source evidence.” If archives are supposed to preserve real source evidence, then a text-only allowlist does not match the way UAIX currently treats intake and preserved source material. citeturn26view0turn26view1turn26view2turn26view4

## Security, authority, and import boundary gaps

The security model in the draft is directionally right, but it is still underpowered compared with current UAIX guidance. The UAIX Memory Firewall says imported packets are **quarantined public data** until validation and local policy accept them; a valid packet is not trusted memory, safe code, or permission to execute. It also says startup packets must be **schema-validated before adoption**, and ambiguous authority, missing provenance, missing integrity, or conflicting memory must produce **no-op plus human review**. Your draft talks about rejecting bad ZIPs, but it does not establish the full quarantine-first promotion model. citeturn11view1turn11view2

Related to that, the draft never makes room for the UAIX-required **no-op** model. Public schemas require no-op-related fields repeatedly: the startup packet requires `no_op_triggers` and `validation_targets`, the receiver brief requires `no_op_triggers` and `escalation_triggers`, the memory-firewall policy requires `quarantine_default`, `adoption_requirements`, `blocked_requests`, and `human_review_required`, and the authority boundary profile requires `not_authorized_for` and `no_op_triggers`. Your draft’s manifest and import rules do not carry those concepts, which means it cannot express current UAIX boundary behavior. citeturn19view0turn19view2turn22search6

The anchor-mutation wording is also too loose. UAIX does not say “explicit user approval” in a generic sense; the current anchor guidance uses the stricter formula **exact human artifact-and-operation authorization**. That difference matters because UAIX’s Talisman guidance is designed specifically to block vague, inferred, or conversationally widened permission when `totem.uai`, `taboo.uai`, or `talisman.uai` are in play. citeturn12view0turn12view4turn20view3

Your `capabilities` object is another mismatch. Current UAIX keeps **runtime execution, tool calls, approvals, live traces, and session memory** in the harness/control layer, while UAI/UAIX preserves the reviewed record and boundary declarations. That means booleans like `mayEnableNetwork` or `mayEnableTools` are fine as descriptive metadata, but they are not the strongest UAIX mechanism. The public UAIX pattern is closer to **authority-boundary records, blocked actions, no-op triggers, required human approval, and evidence requirements** than to a flat power switch inside a package manifest. citeturn23view0turn22search6turn28view0

## Packaging and support-claim mismatches

The manifest model needs rework if the goal is alignment with the current public record. UAIX clearly does use manifests, but the current public packaging surface emphasizes a **generated manifest inside the ZIP**, a **manifest overlay JSON**, and machine-readable exports such as `.uai/exports/manifest.json`. The AI Memory read path also expects the agent to read the manifest and front-door files before acting, and the wizard’s session-start guidance points directly to `.uai/exports/manifest.json`. Your draft invents a new mandatory `.uai/manifest.uaix.json` path and a schema URL without tying it back to the current public schema/registry/validator chain. That makes it feel like a new proposal rather than a faithful restatement of current UAIX packaging. citeturn28view0turn18view0turn18view2turn18view4

If the draft is supposed to cover **project or repository handoff**, it also omits the current UAIX **front door**. Project Handoff uses `AGENTS.md` as the durable front door and `readme.human` as the human briefing surface, and its load path starts there before typed `.uai` records are read. The draft never says whether `.uaix` is assistant-only desktop packaging or a full Project Handoff carrier. If it is the latter, the omission is a real mismatch. If it is the former, that narrowing needs to be stated explicitly. citeturn15view2turn15view3turn15view4

The **Desktop Load Model** section also mixes client-runtime behavior into what looks like a UAIX core spec. Public UAIX guidance consistently separates runtime concerns from portable memory/evidence. Harnesses own session execution, tool calls, approvals, retries, and live runtime memory; UAIX keeps the reviewed handoff and evidence layer. So OS-specific expansion paths, session JSON layouts, and multi-instance runtime rules are best treated as **implementation guidance** for a client, not as core UAIX semantic requirements. citeturn23view0turn28view0

Why This File Exists

This is a memory-system evidence file from uaix.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: UAIX Alignment Review of the .uaix Draft; Executive assessment; File-set and package-family mismatches; Long-memory and archive model mismatches; Security, authority, and import boundary gaps; Packaging and support-claim mismatches; Rewrite priorities. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-911 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Alignment Review Of The ` Uaix` Draft",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/raw-system-archives-uaix-agent-file-handoff-processed-2026-06-14-uaix-pa-bcfa4e5e/",
    "source_reference":  "raw/system-archives/uaix/agent-file-handoff/processed-2026-06-14-uaix-package-format/Improvement/UAIX Alignment Review of the .uaix Draft.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:bcfa4e5e14fbd5696613d764d67b660658c9a7ba2afac2572de5fc68215ab6f6",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-14T19:14:53.7761034Z",
    "import_status":  "new",
    "duplicate_group_id":  "sfg-911",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}