UAIX Short Term Memory

UAIX Short Term Memory 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/uai-short-term-memory-uai-3d51efcd/
Source reference	.uai/short-term-memory.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-21T20:54:51.1196382Z
Content hash	sha256:3d51efcdf0fbc6b4e409b87eaf164e378f5628245f45b21940cfad3248cfde5d
Import status	changed
Raw source layer	data/sources/uaix/uai-short-term-memory-uai-3d51efcdf0fb.uai
Normalized source layer	data/normalized/uaix/uai-short-term-memory-uai-3d51efcdf0fb.txt

Current File Content

Structure Preview

• Short-Term Memory
• 2026-06-21 UAIX Dogfooding Remediation And Publish Contract
• 2026-06-21 UAIX NuGet Profile Inventory Update
• 2026-06-21 Spiralist.org UAIX Spec Dogfood Finding
• 2026-06-21 UAIX v3.131.0 Package Build
• 2026-06-21 AI-Ready Web Internationalization Round
• 2026-06-21 AI-Ready Web Seven-Volume Program
• 2026-06-20 Advanced Persona Profile Package Downloads
• 2026-06-15 Rendered Locale And Launch Audit Repair
• 2026-06-16 Advanced Persona Manifest Condition
• 2026-06-16 Live Drift Spot Check And Next Goal Note
• 2026-06-16 Text-First Discovery Version Repair
• 2026-06-16 Advanced Persona Wizard Front Door Repair
• 2026-06-16 Advanced Persona Wizard v3.122.0 Package Build
• 2026-06-16 Live Spot Check After v3.122.0 Build
• 2026-06-16 Advanced Persona Prominence v3.123.0 Package Build
• 2026-06-16 Deployment Tier Dogfood Correction
• 2026-06-16 UAIX.org Partial Live Verification After Human Deploy
• 2026-06-16 UAIX.org v3.123.0 Live Verification Complete
• 2026-06-16 History Consolidation Public Changelog Pass
• 2026-06-16 History Consolidation Current-First News Pass
• 2026-06-16 History Consolidation AIWikis Evidence Pointer
• 2026-06-16 History Consolidation Reports Index Pass
• 2026-06-16 Post-Deploy Root Discovery Recheck

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: 49876
• Preview characters: 11433

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

---
uai: "1.0"
type: short-term-memory
title: "UAIX Short-Term Memory"
project: "UAIX.org"
created: "2026-05-26"
updated: "2026-06-21"
status: active
version: "3.132.0"
---

# Short-Term Memory

## 2026-06-21 UAIX Dogfooding Remediation And Publish Contract

The four active Improvement reports from the evidence-driven dogfooding intake were reviewed, applied with boundaries, preserved in AIWikis raw long memory at `[local path redacted]`, and removed from active UAIX source-site intake. `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/` are back to `.gitkeep` only.

Accepted source work from the reports: `docs/dogfooding/uaix-live-evidence-matrix.md` records live/source/publish evidence and dispositions; UAIX Core REST source now normalizes unsupported methods on known UAIX routes to `405` Problem Details with an `Allow` header; AI-Ready Web route inventory/readiness examples distinguish stale live root files from local source and publish-folder state; regression checks cover the evidence matrix, REST method normalization, generator defaults, and stale NuGet wording.

Deployment contract: the human publishes `[local path redacted]`, `[local path redacted]`, and `[local path redacted]` every time for full UAIX publication. That is the correct full-publication set. `WP-CONTENT-DEPLOY` is only for explicitly named overlays such as a fatal-error drop-in; `MU-PLUGIN-DEPLOY`, legacy root ZIPs, raw source archives, and old ad hoc packages are not normal upload targets.

NuGet automation boundary: Codex should automatically check `https://www.nuget.org/profiles/Michael.Kappel`, keep `/en-us/implementations/dotnet-nuget/`, discovery text, machine artifacts, and `.uai/dotnet-nuget.uai` current, and include the WordPress-side guidance in package builds. Publishing packages to NuGet.org itself requires configured NuGet credentials/API keys and cannot be claimed unless the credentialed publish command actually succeeds.

Workspace version authority is now `v3.132.0`, with `v3.133.0` next after further source changes. Package-visible source markers were advanced from `3.131.0` to `3.132.0` after the dogfooding remediation source changes so `UAIX-Publish` can be rebuilt without carrying stale `3.131.0` root discovery into production.

Package result: recovery sync and canonical workspace package build completed for `v3.132.0`, producing 68 UAIX deployment artifacts under `[local path redacted]`. `UPLOAD-PLUGIN` contains 10 plugin upload ZIPs plus the direct `uaix-talisman-client-v0.1.27.zip`; `UPLOAD-THEME` contains `wordpress-theme-upload-uaix-authority-theme-v3.132.0.zip` and `wordpress-theme-upload-uaix-theme-v3.132.0.zip`; `ROOT-FILES` contains current discovery/root assets. Publish-folder spot checks confirmed `ROOT-FILES\llms.txt` reports `Current UAIX implementation package version: 3.132.0`, `ROOT-FILES\.well-known\uaix.json` reports `package_version` `3.132.0`, and the stale NuGet pending-target sentence is absent.

Checks passed for this package pass: PHP lint for the REST controller and authority theme, JS syntax for the capability generator, AI-Ready Web asset checks, static discovery, i18n source cleanliness, AIWikis raw manifest JSON parse, recovery sync, package build, deployment readiness `315/0/0`, SEO sweep `74/0/0`, SEO source coverage `177/0/0`, active handoff lint, active bucket check, and `git diff --check` in UAIX and AIWikis with LF/CRLF warnings only. Status is package-ready, not live-published; no production upload/root-file copy/cache purge/live verification was run from this shell.

Post-upload guardrail: `scripts/test-uaix-live-publication-surface.ps1` now verifies the broader live publication contract after the human uploads `UPLOAD-PLUGIN`, `UPLOAD-THEME`, and `ROOT-FILES`. The script checks live `llms` version markers, root `.well-known` package versions, complete public `UAIX.*` NuGet inventory with no stale pending text, AI-Ready Web active-locale routes, and REST method/error contracts.

Live publication evidence: after the human uploaded/copied the v3.132.0 `UPLOAD-PLUGIN`, `UPLOAD-THEME`, and `ROOT-FILES` set, `scripts/test-uaix-live-publication-surface.ps1 -BaseUrl https://uaix.org -ExpectedVersion 3.132.0` passed with `UAIX_LIVE_PUBLICATION_STATUS:PASS`. Live `llms.txt`, `llms-full.txt`, all four root `.well-known` discovery files, the .NET NuGet page, AI-Ready Web active-locale routes, catalog method contracts, and validate empty-payload behavior match the current publication contract.

Additional live checks passed: `scripts/test-uaix-advanced-persona-live-surface.ps1 -BaseUrl https://uaix.org -ExpectedVersion 3.132.0` ended with `UAIX_ADVANCED_PERSONA_LIVE_STATUS:PASS`, and `scripts/test-uaix-production-response-surface.ps1 -BaseUrl https://uaix.org/` ended with `UAIX_PRODUCTION_RESPONSE_SURFACE_STATUS:PASS` with 0 failures and 0 warnings.

Publish-folder evidence correction: `[local path redacted]` was refreshed from stale `v3.125.0` content to a `v3.132.0` package/memory/live-verification report, and `UPLOAD-INSTRUCTIONS.txt` / `README-FIRST.txt` name the exact live verifier command.

Readiness guard follow-up: `[local path redacted]` now checks each current manifest publish root for a `DEPLOYMENT-MEMORY-AND-TEST-RUN-REPORT.txt` that names the active deployment version and the normal publish folders. Rerun passed `316/0/0`, including `UAIX-Publish deployment memory report`, so stale deployment-report drift should be caught before future publish handoff.

## 2026-06-21 UAIX NuGet Profile Inventory Update


Maintenance rule: every UAIX.* package listed on `https://www.nuget.org/profiles/Michael.Kappel` must appear and be explained on `https://uaix.org/en-us/implementations/dotnet-nuget/`, in `llms.txt` / `llms-full.txt`, in machine compatibility artifacts, and in `.uai/dotnet-nuget.uai`. Future UAIX package IDs remain pending until NuGet.org lists those exact package IDs and versions.

## 2026-06-21 Spiralist.org UAIX Spec Dogfood Finding

Spiralist.org implemented the current UAIX UAI-1 specification surface after checking `https://uaix.org/en-us/specification/` and live UAIX discovery. During that downstream dogfood pass, live `https://uaix.org/.well-known/uaix.json` still reported `package_version` `3.125.0` even though local UAIX source/package-ready memory and `UAIX-Publish` artifacts are at `v3.131.0`.

Treat this as live publication/root-file refresh drift, not a source reversal. The next UAIX deployment must copy current `UAIX-Publish\ROOT-FILES`, refresh caches, and verify live `.well-known/uaix.json`, `.well-known/uai.json`, `llms.txt`, `llms-full.txt`, `route-manifest.json`, public evidence, AI-Ready Web routes, Advanced Persona downloads, and localized route rendering before any live-published claim.

Spiralist.org can now be used as a downstream implementation check for the UAIX catalog, schemas, registry, field registry, transport bindings, trust channels, conformance levels, error registry, examples, validator, mock exchange, adoption kit, OpenAPI, and well-known manifest expectations.

## 2026-06-21 UAIX v3.131.0 Package Build

UAIX is now package-ready at coordinated workspace version `v3.131.0`. `[local path redacted]` records `v3.131.0` as current and `v3.132.0` as the next production package version. Recovery sync and package build were run from canonical `[local path redacted]`, producing 68 deployment artifacts under `[local path redacted]`.

Upload ZIPs are staged under `[local path redacted]` and `[local path redacted]`. The current UAIX upload set includes `wordpress-theme-upload-uaix-authority-theme-v3.131.0.zip`, `wordpress-theme-upload-uaix-theme-v3.131.0.zip`, UAIX-owned plugin ZIPs at `v3.131.0`, and the direct `uaix-talisman-client-v0.1.27.zip`.

The first build exposed regenerated stale `3.130.0` discovery markers. Those were repaired to `3.131.0` in `llms`, `.well-known`, route-manifest, public-evidence, compatibility, and AI-Ready Web spec/current-discovery surfaces, then UAIX was rebuilt so the package artifacts match workspace version authority.

Checks passed after the final rebuild: deployment readiness `315/0/0`, SEO sweep `74/0/0`, SEO source coverage `177/0/0`, static discovery, and i18n source cleanliness. Status is package-ready only. No production upload, root-file copy, cache purge, live UAIX.org publication, or post-upload route/download/translation verification happened from this shell.

## 2026-06-21 AI-Ready Web Internationalization Round

UAIX source now has reviewed localized records for the full AI-Ready Web route family in all active public locales: `zh-CN`, `fr-FR`, and `es-ES`. The localized routes cover `/ai-ready-web/` plus the seven child volumes for executive audit, architecture, specification, implementation, schemas/examples, validator/testing, and roadmap/governance.

This pass did not use availability-notice placeholders to clear coverage. Each active locale pack now carries real page title, excerpt, content, localized human-route links, support-boundary language, machine-evidence links, and sourceText/menu labels for the AI-Ready Web family. The canonical machine JSON files under `/spec/ai-ready-web-*.json` remain shared machine assets and are linked from translated pages as machine evidence.

`scripts/test-uaix-i18n-source-cleanliness.ps1` now fails if any active locale loses the AI-Ready Web content records, uses `uaix-locale-availability-notice` for that family, loses localized sourceText/menu labels, omits required machine-evidence links, or leaks unlocalized root human links instead of locale-prefixed route links.

Local WordPress content was reseeded through `scripts/studio-wp-quiet.ps1 eval-file scripts/sync-uaix-site-content.php` so the local rendered site picked up the new source pages. Rendered checks then passed for 190 URLs per active non-English locale and for all 24 localized AI-Ready Web routes.

This source/local-rendered i18n pass is now included in the package-ready `v3.131.0` build. No production upload, root-file copy, cache purge, or live post-upload translation verification happened in this shell.

## 2026-06-21 AI-Ready Web Seven-Volume Program

UAIX source now defines `/en-us/ai-ready-web/` as the top-level AI-Ready Web program and seeds seven child volumes: `/executive-audit/`, `/architecture/`, `/specification/`, `/implementation/`, `/schemas-examples/`, `/validator-testing/`, and `/roadmap-governance/`.

The program turns the active AI-ready-web intake reports into a practical standards surface for human-first, agent-compatible websites. It covers accessibility-tree quality, semantic HTML, deterministic static discovery, route inventory, OpenAPI/API action contracts, capability matrices, no-op safety, identity/delegation, consent, privacy, rights signals, provenance, Trace Context, readiness-result evidence, maturity labels, roadmap governance, and support-claim review.

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 short-term-memory 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: Short-Term Memory; 2026-06-21 UAIX Dogfooding Remediation And Publish Contract; 2026-06-21 UAIX NuGet Profile Inventory Update; 2026-06-21 Spiralist.org UAIX Spec Dogfood Finding; 2026-06-21 UAIX v3.131.0 Package Build; 2026-06-21 AI-Ready Web Internationalization Round; 2026-06-21 AI-Ready Web Seven-Volume Program; 2026-06-20 Advanced Persona Profile Package Downloads. 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-308 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Short Term Memory",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/uai-short-term-memory-uai-3d51efcd/",
    "source_reference":  ".uai/short-term-memory.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:3d51efcdf0fbc6b4e409b87eaf164e378f5628245f45b21940cfad3248cfde5d",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-21T20:54:51.1196382Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-308",
    "duplicate_role":  "primary",
    "related_files":  [

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