UAIX Decisions Log

UAIX Decisions Log is a uai-system source file exposed by AIWikis.org with provenance, current content, and generated explanation.

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/raw-system-archives-uaix-deployment-memory-reorg-2026-05-03-uai-decision-05e593d8/
Source reference	raw/system-archives/uaix/deployment-memory-reorg/2026-05-03/.uai/decisions.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-03T15:10:07.5717455Z
Content hash	sha256:05e593d8297aa520d6046fb0d04ff419900e5dbf4fc8450c770bb03b7db9c9f7
Import status	unchanged
Raw source layer	data/sources/uaix/raw-system-archives-uaix-deployment-memory-reorg-2026-05-03-uai-decisions-uai-05e593d8297a.uai
Normalized source layer	data/normalized/uaix/raw-system-archives-uaix-deployment-memory-reorg-2026-05-03-uai-decisions-uai-05e593d8297a.txt

Current File Content

Structure Preview

• UAIX Decisions Log
• [2026-05-03] Production deployment builds trigger memory sorting; dev/test builds do not
• [2026-05-03] Baseline all deployment ZIPs before using affected-version deltas
• [2026-05-02] Publish agentic harness strategy as a bounded UAI guide
• [2026-05-02] Add a roadmap work documentation ledger
• [2026-05-02] Add a today-focus path to roadmap authority work
• [2026-05-02] Publish support-claim checks with the roadmap
• [2026-05-02] Use roadmap work queue and promotion gates for support language
• [2026-05-01] Use AIWikis as UAIX cold memory, not UAIX authority
• [2026-05-01] Teach the hot/cold memory split publicly and dogfood it locally
• [2026-05-01] Keep coding-agent integrations as thin pointers to one Project Handoff bundle
• [2026-05-01] Position Project Handoff as portable project memory
• [2026-04-30] Keep the AI Memory Package Wizard as local package planning
• [2026-04-30] Use AIWikis outcome documentation for explicit archive consolidation feedback
• [2026-04-27] Keep Agent File Handoff as chat-start local intake
• [2026-04-26] Keep UAIX.org as UAI-1 authority
• [2026-04-25] Dogfood root AGENTS.md plus .uai in the repo itself

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: 17033
• Preview characters: 11968

---
uaix: "1.0"
type: decisions
title: "UAIX Decisions Log"
created: "2026-04-25"
updated: "2026-05-03"
status: active
author: "UAIX maintainers"
version: 30
---

# UAIX Decisions Log

## [2026-05-03] Production deployment builds trigger memory sorting; dev/test builds do not

**Decision:** Treat production deployment builds and release packages as memory-management checkpoints. Before calling a production deployment complete, agents must sort the selected package path into hot memory and cold memory. Hot memory keeps current deployed truth, versions, changed files, checks, blockers, owners, and next actions. Cold memory receives bulky history, old reports, raw sources, stale plans, and background or rejected rationale when an AIWikis, LLM Wiki, or archive path exists with transfer evidence.

**Why:** Memory organization is valuable at release time because the release creates durable project truth and evidence. Running the same pass on every development build or test run would add friction and could create noisy memory churn.

**Effect:** AGENTS.md, readme.human, `.uai` operations and test guidance, deployment docs, wizard-generated instructions, Project Handoff, Agent File Handoff, and LLM Wiki guidance should describe memory sorting as a production deployment/release-build step only.

**Boundary:** Ordinary dev builds, local test builds, local package experiments, and non-release smoke checks do not trigger this pass unless the human explicitly marks the build as release-bound or a release candidate. This does not create automatic LLM Wiki sync, automatic repository writes, hosted import validation, SDK, CLI, certification, endorsement, or public conformance evidence.

## [2026-05-03] Baseline all deployment ZIPs before using affected-version deltas

**Decision:** The first deployment ZIP round after adopting cross-site deployment versioning must be treated as a baseline. Every deployable ZIP across UAIX, LlmWikis, AIWikis, and Protocol5/public distribution surfaces must carry the same human-approved system-wide version in the filename before later affected-version rules apply.

**Why:** The first attempted round showed the rule was incomplete: only three AIWikis ZIPs received `-v0.1.3` names, while UAIX, LlmWikis, and mirrored handoff ZIPs remained unversioned. Without a shared baseline, the later "only changed packages advance" rule cannot tell humans what was deployed or which packages still need upload.

**Effect:** Deployment guidance now distinguishes the one-time baseline from later affected-version deltas, and `scripts/test-cross-site-deployment-zip-versions.ps1` checks publish folders for unversioned ZIPs or wrong version tokens before upload.

**Boundary:** This is package/deployment evidence only. It does not change UAI-1 support, create certification or endorsement, make Protocol5.com a standards authority, or require unrelated future package bumps after the baseline exists.

## [2026-05-02] Publish agentic harness strategy as a bounded UAI guide

**Decision:** UAIX should publish `/en-us/guides/agentic-harnesses-uai/` as a practical guide for separating agentic harness execution from UAI evidence, AI Memory, Project Handoff, conformance, and support-claim boundaries.

**Why:** Agentic harness strategy is a useful entry point, but raw market-report language can easily overclaim runtime, adapter, SDK, CLI, certification, or vendor support. A bounded guide lets readers understand where UAI fits without turning UAIX into a runtime or publishing unverified market claims.

**Effect:** The public guide, guide landing page, navigation, discovery manifests, catalog, tests, zh-CN page override, and handoff docs now state the layer split: harnesses execute; MCP/A2A/runtime tools coordinate and trace; UAI preserves reviewed portable evidence, validator/conformance material, AI Memory, and Project Handoff records that must survive the run.

**Boundary:** The guide does not create an agent runtime, scheduler, hosted importer, official MCP/A2A/OpenAI/vendor adapter, trace exporter, SDK, CLI, certification, endorsement, automatic repository write, automatic LLM Wiki sync, or UAI-1 conformance claim for repo-local handoff files.

## [2026-05-02] Add a roadmap work documentation ledger

**Decision:** The public Roadmap and machine-readable roadmap should explicitly document where roadmap work is recorded, what counts as proof, how source leads are promoted, and how future agents pick up the work.

**Why:** UAIX is more authoritative when roadmap work is not hidden in private chat, local archive folders, or unpromoted reports. Readers and future agents need one public ledger that connects the page, REST payload, canonical roadmap doc, tests, changelog or release trail, and compact handoff state.

**Effect:** `/en-us/roadmap/`, `/wp-json/uaix/v1/roadmap`, `docs/roadmap.md`, tests, and handoff state now carry a roadmap work documentation ledger alongside the today-focus path, work queue, evidence promotion gates, and support-claim checks.

**Boundary:** The ledger is a documentation and verification rule. It does not create hosted upload/import validation, automatic repository writes, automatic LLM Wiki sync, official adapters, trace exporters, SDKs, CLIs, certification, endorsement, compliance, managed AI Memory package records, runtime ownership, or UAI-1 conformance evidence by itself.

## [2026-05-02] Add a today-focus path to roadmap authority work

**Decision:** The public Roadmap and machine-readable roadmap should start from a practical today-focus path before the longer queue, gates, and support checks.

**Why:** UAIX is more authoritative when a reader can immediately see what to do today: orient on UAI-1 authority, create one proof run, use the AI Memory Package Wizard within current support, and keep agentic-system integration language behind evidence gates.

**Effect:** `/en-us/roadmap/`, `/wp-json/uaix/v1/roadmap`, `docs/roadmap.md`, tests, and handoff state now expose today-focus guidance for authority orientation, first proof runs, AI Memory package work, and planned agentic-system evidence work.

**Boundary:** The today-focus path does not create hosted upload/import validation, automatic repository writes, automatic LLM Wiki sync, official adapters, trace exporters, SDKs, CLIs, certification, endorsement, compliance, managed AI Memory package records, runtime ownership, or UAI-1 conformance evidence by itself.

## [2026-05-02] Publish support-claim checks with the roadmap

**Decision:** The public Roadmap and machine-readable roadmap should include explicit support-claim checks, not only status labels and promotion gates.

**Why:** Readers and future agents need a repeatable way to decide whether a phrase is safe current-support language, planned work, research-track direction, or unsupported overclaiming.

**Effect:** `/en-us/roadmap/`, `/wp-json/uaix/v1/roadmap`, `docs/roadmap.md`, tests, and handoff state now check current support, AI Memory package scope, adapter/runtime scope, and conformance language against public pages, machine artifacts, reproducible evidence, implementation or package proof, and release trail.

**Boundary:** The checklist does not create managed AI Memory packages, hosted import validation, automatic repository writes, automatic LLM Wiki sync, official adapters, trace exporters, SDKs, CLIs, certification, endorsement, compliance, or ecosystem-wide support.

## [2026-05-02] Use roadmap work queue and promotion gates for support language

**Decision:** UAIX roadmap work should be visible as a current work queue and should clear named evidence promotion gates before it becomes current support language.

**Why:** The recent roadmap and agentic-system strategy inputs are useful only if readers can see what work is next without mistaking adapter, exporter, serializer, validation, redaction, SDK, CLI, certification, or sync ideas for shipped support.

**Effect:** `/en-us/roadmap/`, `/wp-json/uaix/v1/roadmap`, `docs/roadmap.md`, homepage task paths, tests, and handoff state now point to the same queue: deploy current artifacts, prove wizard serializer parity, plan local validation/redaction lint, design trace-to-handoff fixtures, and evaluate reference adapters only after evidence exists.

**Boundary:** The queue and gates are planning records. They do not create hosted upload/import validation, automatic repository writes, automatic LLM Wiki sync, official adapters, trace exporters, SDKs, CLIs, certification, endorsement, UAI-1 conformance evidence, or runtime orchestration support.

## [2026-05-01] Use AIWikis as UAIX cold memory, not UAIX authority

**Decision:** UAIX keeps routine agent context concise and moves bulky research, proposal history, roadmap background, and pre-slim handoff snapshots into AIWikis long-term memory.

**Why:** The loaded handoff bundle had accumulated too much historical detail. That made routine agent startup expensive and encouraged future agents to reread old proposal text instead of current operating truth.

**Effect:** AIWikis now preserves 23 selected UAIX files under `raw/system-archives/uaix/internal-memory-reorg/2026-05-01/` with transfer evidence in `raw/system-archives/2026-05-01-uaix-internal-memory-reorg.json`. UAIX `.uai/progress.uai`, `.uai/decisions.uai`, and `.uai/handoff-pattern.uai` now carry compact active truth and pointers rather than long history.

**Boundary:** AIWikis memory is not active UAIX truth until promoted back into UAIX `.uai`, current docs, code, public pages, machine artifacts, tests, release notes, or roadmap state. The transfer does not create automatic sync, hosted import validation, repository writes, SDK, CLI, certification, endorsement, official vendor support, or validator-backed `.uai` conformance evidence.

## [2026-05-01] Teach the hot/cold memory split publicly and dogfood it locally

**Decision:** UAIX public AI Memory and Project Handoff guidance should state the context-budget rule directly: hot packets carry current operating truth; LLM Wiki or AIWikis-style cold memory carries long history, source summaries, old research, and pre-slim snapshots.

**Why:** The UAIX and LlmWikis handoff bundles both accumulated too much historical detail. The sites should teach how to prevent that buildup and then follow the same rule internally.

**Effect:** UAIX public copy now includes `/en-us/guides/project-handoff-context-budget/` and tells readers to preserve old hot-context snapshots with manifests, hashes, summaries, and logs before slimming active files. Reviewed facts can be promoted back into AI Memory, Project Handoff, docs, code, tests, release notes, roadmap state, or machine artifacts.

**Boundary:** The guidance does not create automatic LLM Wiki sync, hosted import validation, repository writes, SDK, CLI, certification, endorsement, official vendor support, or validator-backed conformance evidence.

## [2026-05-01] Keep coding-agent integrations as thin pointers to one Project Handoff bundle

**Decision:** UAIX supports cross-tool coding-agent pickup through one local Project Handoff bundle: root `AGENTS.md`, root `readme.human`, typed `.uai` records, active file intake, and targeted checks. Tool-specific files stay thin pointers.

**Why:** Codex, Claude Code, Cursor, GitHub Copilot, Gemini Code Assist, local agents, vendors, and humans all need current repo truth without duplicating instruction files or depending on repeated live URL reading.

**Effect:** UAIX publishes `/en-us/guides/project-handoff-coding-agents/`; local pointers include `CLAUDE.md`, `GEMINI.md`, `.cursor/rules/uaix-handoff.mdc`, and `.github/copilot-instructions.md`; `.agents/skills/uaix-handoff/` repeats the Codex pickup workflow.

**Boundary:** These are compatibility patterns and local workflow aids, not official adapters, SDKs, CLIs, hosted import validators, automatic repository writers, vendor certifications, endorsements, or UAI-1 conformance evidence.

Why This File Exists

This is a UAI AI Memory handoff 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 .uai file is a compact decisions packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: UAIX Decisions Log; [2026-05-03] Production deployment builds trigger memory sorting; dev/test builds do not; [2026-05-03] Baseline all deployment ZIPs before using affected-version deltas; [2026-05-02] Publish agentic harness strategy as a bounded UAI guide; [2026-05-02] Add a roadmap work documentation ledger; [2026-05-02] Add a today-focus path to roadmap authority work; [2026-05-02] Publish support-claim checks with the roadmap; [2026-05-02] Use roadmap work queue and promotion gates for support language. 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-034 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Decisions Log",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/raw-system-archives-uaix-deployment-memory-reorg-2026-05-03-uai-decision-05e593d8/",
    "source_reference":  "raw/system-archives/uaix/deployment-memory-reorg/2026-05-03/.uai/decisions.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:05e593d8297aa520d6046fb0d04ff419900e5dbf4fc8450c770bb03b7db9c9f7",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-03T15:10:07.5717455Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-034",
    "duplicate_role":  "primary",
    "related_files":  [

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