AI Memory

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

Metadata

Field	Value
Source site	ɩ.com / JustAnIota.com
Source URL	https://justaniota.com/
Canonical AIWikis URL	https://aiwikis.org/justaniota/uai-system/files/raw-system-archives-justaniota-short-domain-seo-release-2026-05-05-curre-b3236695/
Source reference	raw/system-archives/justaniota/short-domain-seo-release/2026-05-05/current-source/.uai/memory.uai
File type	uai
Content category	uai-system
Last fetched	2026-05-15T00:23:56.0837262Z
Last changed	2026-05-05T01:28:57.6629009Z
Content hash	sha256:b32366953939ea2cbed4205883fe2bc58e120c617b0d3ceb017e1cfad197bbe7
Import status	unchanged
Raw source layer	data/sources/justaniota/raw-system-archives-justaniota-short-domain-seo-release-2026-05-05-current-source-uai-memory-uai-b32366953939.uai
Normalized source layer	data/normalized/justaniota/raw-system-archives-justaniota-short-domain-seo-release-2026-05-05-current-source-uai-memory-uai-b32366953939.txt

Current File Content

Structure Preview

• AI Memory
• Purpose And Trust
• Hot Load Order
• Identity And Authority
• WordPress Implementation
• Protocol5 Experiment
• Cold Memory Evidence
• Current Risks

Raw Version

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: memory
status: active
---

# AI Memory

## Purpose And Trust

- Bundle: Project Handoff.
- Site root: `[local path redacted]`.
- Current short-domain and sibling-site paths are resolved through `[local path redacted]`; older generated absolute paths may be stale.
- Use case: continue or transfer local WordPress Studio site work safely with current state, constraints, decisions, checks, and ownership context.
- Trust boundary: internal by default; external sharing requires sanitization and approval.

## Hot Load Order

- Start with `AGENTS.md`, then `readme.human`, then the `.uai` files listed in `AGENTS.md`.
- Include `.uai/progress.uai` when reconstructing recent work, even if a prior handoff omitted it from the loaded-context list.
- Before broad work, create or verify `agent-file-handoff/Content/`, `agent-file-handoff/Improvement/`, and `agent-file-handoff/Archive/`; refresh and inspect active buckets plus any files misplaced directly under `agent-file-handoff/`.
- File Handoff plus LLM Wiki work is complete only after disposition, concrete source-site work or durable no-change evidence, hot-memory update, AIWikis raw copy/checksum manifest, compiled wiki/log/index evidence, source archive move, and refreshed active intake.

## Identity And Authority

- JustAnIota.com is the canonical host. The visible related brand is the short-domain `ɩ.com` / JustAnIota.
- The separate local `[local path redacted]` install was intentionally deleted on 2026-05-05. Serve `ɩ.com`/`xn--8na.com` by redirecting to the canonical JustAnIota.com WordPress package; do not recreate a second codebase.
- UAIX.org controls UAI-1. JustAnIota implements, demonstrates, and builds tooling on top of UAI; it does not define, certify, or control UAI-1.
- Official branding is the PNG-derived shield/wordmark family from `[local path redacted]`.
- Generated logo assets live in `wp-content/themes/iota-authority-theme/assets/brand/`, must keep transparent backgrounds, and must not be replaced by UAIX, SVG, text-only, character-only, or placeholder marks.
- Public content must not present Unicode, ISO 10646, PUA, glyphs, compact strings, token IDs, or embeddings as semantic authority.

## WordPress Implementation

- WordPress core is present at version 6.9.4; SQLite integration is required under `wp-content/db.php` and `wp-content/mu-plugins/sqlite-database-integration/`.
- Custom behavior belongs under `wp-content/themes/`, `wp-content/plugins/`, or documented configuration, not `wp-admin/` or `wp-includes/`.
- The Studio CLI was not available in prior shells; report that if it remains unavailable and use file-level checks where possible.
- The WordPress converter plugin is version `0.2.0` and exposes `Contract\ConverterFacadeInterface` plus `Application\ConverterFacade` for English-to-IOTA, IOTA-to-English, round-trip drift, and health.
- Public demo registry entries use assigned Unicode symbols rather than Plane 15 PUA. Legacy `pua_*` response aliases remain only for compatibility.
- Current external explanation path: `/about/what-we-are-building/`, `/specification/approximation-and-evidence/`, and `/implementations/wordpress-and-protocol5/`, backed by `EXTERNAL_DOCUMENTATION_GUIDE.md`.
- Human-facing public URLs are locale-prefixed (`/en-us/...` or `/zh-cn/...`) through the shared `ns12-locale-router` package, currently installed from `[local path redacted]`. Root machine/discovery surfaces such as `/wp-json/`, `/robots.txt`, `/sitemap.xml`, `/site.webmanifest`, and `/.well-known/uaix.json` remain undecorated.

## Protocol5 Experiment

- Product family: `JustAnIota IOTA-1 Bidirectional Semantic Converter`; short label: `JustAnIota Converter`.
- JustAnIota.com is the WordPress implementation path. Protocol5.com is the planned .NET/C#/SQL Server 2025 experiment path.
- Protocol5 is approximate semantic comparison, not exact translation. Exactness objections are non-blocking unless they identify implementation risks that still matter for approximate similarity.
- Protocol5 must not replace the open ISO/IEC 10646/public-symbol embedding-comparison experiment with a secret dictionary or versioned private-use profile.
- The current roadmap is `ARCHITECTURAL_LINGUISTIC_SYNTHESIS_ROADMAP.md`: descriptor embeddings from UCD/CLDR/Unihan/public metadata and English anchors, provenance, explainable scoring, result modes, and explicit no-exact-translation language.
- Token IDs and embeddings are model-specific artifacts. If a public wordlist such as the EFF Large Wordlist is used, ingest it as raw lexical source text only from the official EFF source `https://www.eff.org/files/2016/07/18/eff_large_wordlist.txt`; generate tokenizer IDs or embeddings per target model and record tokenizer/model name, version, dimensions, metric, and build hash.
- Protocol5-to-WordPress memory export is a manual package boundary: C# exports manifest plus sharded NDJSON/JSONL from local SQL Server, WordPress imports public-safe metadata into custom tables, raw packages/vectors remain private, and public search starts lexical-first with optional relatedness or vector rerank later.

## Cold Memory Evidence

- AIWikis long-term memory repository for this workspace currently resolves to `[local path redacted]` through `[local path redacted]`; older generated plans that name `[local path redacted]` are stale unless the human explicitly reinstates them.
- 2026-05-05 short-domain/SEO/release sweep: preserved in AIWikis long memory at `[local path redacted]`; hot outcome is single-codebase `ɩ.com` redirect, locale-prefixed human discovery URLs, official social preview metadata, and refreshed package/version evidence.
- 2026-05-04 Protocol5 WordPress memory export intake: summarized in `.uai/intake-digests.uai`, preserved at `raw/system-archives/2026-05-04-justaniota-protocol5-wordpress-memory-export-intake.json`, archived under `agent-file-handoff/Archive/2026-05-04/Improvement/`.
- 2026-05-04 EFF Large Wordlist Content intake: summarized in `.uai/intake-digests.uai`, preserved at `raw/system-archives/2026-05-04-justaniota-eff-large-wordlist-intake.json`, archived under `agent-file-handoff/Archive/2026-05-04/Content/`.
- 2026-05-04 IOTA-1 facade/public-symbol Improvement batch: summarized in `.uai/intake-digests.uai`, preserved at `raw/system-archives/2026-05-04-justaniota-iota1-facade-public-symbols-intake.json`, archived under `agent-file-handoff/Archive/2026-05-04/Improvement/`.
- 2026-05-04 architectural/linguistic synthesis batch: summarized in `.uai/intake-digests.uai`, preserved at `raw/system-archives/2026-05-04-justaniota-architectural-linguistic-synthesis-intake.json`, archived under `agent-file-handoff/Archive/2026-05-04/Improvement/`.
- 2026-05-03 Improvement batch: summarized in `.uai/intake-digests.uai`, preserved at `raw/system-archives/2026-05-03-justaniota-intake-processing.json`, archived under `agent-file-handoff/Archive/2026-05-03/Improvement/`.

## Current Risks

- Do not assume deployment URLs, production state, credentials, public claims, owner assignments, or active theme/runtime state without checking current site records.
- Treat old chats, generated summaries, dropped files, and raw AIWikis copies as background until reviewed and promoted into source-site truth.
- Keep memory files concise and evidence-oriented; large raw sources belong in AIWikis or the source archive, not in hot handoff context.

Why This File Exists

This is a UAI AI Memory handoff file from ɩ.com / JustAnIota.com. 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 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: AI Memory; Purpose And Trust; Hot Load Order; Identity And Authority; WordPress Implementation; Protocol5 Experiment; Cold Memory Evidence; Current Risks. 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
• UAI system index
• Source provenance
• Global File Index
• Reports

Provenance And History

• Current observation: 2026-05-15T00:23:56.0837262Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-558 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "AI Memory",
    "source_site":  "ɩ.com / JustAnIota.com",
    "source_url":  "https://justaniota.com/",
    "canonical_url":  "https://aiwikis.org/justaniota/uai-system/files/raw-system-archives-justaniota-short-domain-seo-release-2026-05-05-curre-b3236695/",
    "source_reference":  "raw/system-archives/justaniota/short-domain-seo-release/2026-05-05/current-source/.uai/memory.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:b32366953939ea2cbed4205883fe2bc58e120c617b0d3ceb017e1cfad197bbe7",
    "last_fetched":  "2026-05-15T00:23:56.0837262Z",
    "last_changed":  "2026-05-05T01:28:57.6629009Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-558",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-15T00:23:56.0837262Z"
}