LLM Wiki Memory Plan

Generated by the UAI AI Memory Package Wizard.

Metadata

Field	Value
Source site	JustAnIota short domain / JustAnIota.com
Source URL	https://justaniota.com/
Canonical AIWikis URL	https://aiwikis.org/justaniota/files/raw-system-archives-justaniota-short-domain-seo-release-2026-05-05-curre-2e690a00/
Source reference	raw/system-archives/justaniota/short-domain-seo-release/2026-05-05/current-source/LLM_WIKI_MEMORY_PLAN.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-04T23:35:36.1296270Z
Content hash	sha256:2e690a00eaf6a663a15989c25b585f34bb6cff70b664d9dec607a247d86e70a8
Import status	unchanged
Raw source layer	data/sources/justaniota/raw-system-archives-justaniota-short-domain-seo-release-2026-05-05-current-source-llm-wiki-memor-2e690a00eaf6.md
Normalized source layer	data/normalized/justaniota/raw-system-archives-justaniota-short-domain-seo-release-2026-05-05-current-source-llm-wiki-memor-2e690a00eaf6.txt

Current File Content

Structure Preview

• LLM Wiki Memory Plan
• Selected Package
• Receiver Questions
• Operating Boundary
• Source Boundary
• Suggested Wiki Topography
• What This Saves Along The Way
• Memory Routing Matrix
• When To Update Long-Term Memory
• Required Transfer Evidence
• Promotion Gates
• Stale Or Conflicting Wiki Memory
• What Not To Do
• Promotion Rule

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.

# LLM Wiki Memory Plan

Generated by the UAI AI Memory Package Wizard.

Place this file at the root of the generated package or beside the canonical starter files. It is a planning file for humans and agents; it is not an automatic LLM Wiki sync instruction.

## Selected Package

- Package: JustAnIota.com AI Memory Handoff
- Package slug: justaniota-com-ai-memory-handoff
- Bundle: Project Handoff (project-handoff)
- LLM Wiki system: AIWikis.org
- LLM Wiki strategy: Existing Reviewed Wiki
- Wiki root path: https://aiwikis.org/
- Local wiki repository path: [local path redacted]
- Wiki index path: wiki/README.md
- Local wiki index path: [local path redacted]
- Entity page pattern: wiki/{topic}.md
- Episodic log pattern: memory/{YYYY-MM-DD}.md
- Memory steward: Project owner or memory steward
- Source collection: Reviewed wiki pages, source summaries, and accepted project notes
- Update policy: after-disposition
- Archive target pattern: raw/system-archives/{project}/
- Evidence log path: LLM_WIKI_TRANSFER_LOG.md
- Promotion targets: AGENTS.md, .uai files, canonical docs, code, tests, release notes, roadmap/progress state, or machine artifacts
- Source authority policy: Repo Canonical First
- AI Memory update policy: After Reviewed Change
- Conflict resolution policy: Constraints And Owner
- Evidence ledger: .uai/progress.uai, CHANGELOG.md, issue, pull request, release note, or handoff acceptance note
- Learn more: https://aiwikis.org/

## Receiver Questions

Before using LLM Wiki memory, ask for or discover these facts from the human, repository, or accepted project docs:

- What is the LLM Wiki root URL or repository path?
- Where are the LLM Wiki index, log, raw source, and transfer evidence records?
- Who can promote reviewed wiki facts into AGENTS.md, .uai files, docs, code, tests, roadmap state, release notes, or machine artifacts?
- What source-boundary rule says when wiki memory stays background instead of becoming current project truth?

If the LLM Wiki location is not available, write `not available - reason` and continue with the UAI package only. Do not invent a wiki location, scrape unrelated sites, or treat unreviewed wiki memory as project truth.

For this workspace, `[local path redacted]` currently resolves AIWikis.org to `[local path redacted]`. Older generated copies named `[local path redacted]`; treat that as stale unless the human gives a newer explicit path. Verify the workspace router before writing long-memory evidence.

## Operating Boundary

- LLM Wiki support is optional. It is not required by any UAI specification or standard.
- This file may tell a future human or AI what to save into long-term memory.
- It does not permit automatic repository writes, WordPress writes, wiki writes, bidirectional sync, certification, endorsement, or support-claim expansion.
- Any promoted fact still needs the normal review path for its target surface.
- Repository files, AGENTS.md, .uai constraints, canonical docs, code, tests, and release notes outrank generated summaries and wiki memory.

## Source Boundary

Wiki memory is background until promoted into accepted project truth. Keep generated summaries, old chats, and source notes out of governing instructions until they are reviewed.

## Suggested Wiki Topography

- Root: https://aiwikis.org/
- Index: wiki/README.md
- Entity pages: wiki/{topic}.md
- Episodic logs: memory/{YYYY-MM-DD}.md
- UAI package files stay separate from the wiki until reviewed facts are promoted.

## What This Saves Along The Way

- Reviewed wiki pages, source summaries, and research trails used to create the portable packet.
- Original processed reports when the project expects long-memory preservation rather than only a public-safe summary.
- Active file dispositions, archive moves, transfer evidence, and follow-up owners.
- Promoted facts with the target AGENTS.md, .uai, doc, code, roadmap, release note, or machine artifact named.
- Release, changelog, validator, or audit evidence that changed the accepted project truth.
- Stale, uncertain, rejected, or background-only notes that should not become operating instructions yet.
- Conflict notes showing which source won, who reviewed the decision, and where evidence was recorded.

## Memory Routing Matrix

| Event | Save To LLM Wiki | Promote To AI Memory | Required Evidence |
|---|---|---|---|
| Active intake file disposition | Summary, risk, disposition, archive path | Only accepted facts and next actions | Source path, checksum, disposition, reviewer |
| Source-site report preservation | Original report copy plus reviewed summary/index pointers | Only reviewed conclusions | Source path, destination path, file count, checksum, disposition |
| Public release or changelog | Release summary and evidence links | Current support truth and changed routes | Changelog, tests, release or deployment evidence |
| Incident or audit close | Timeline, mitigations, owners, evidence references | Confirmed current state and follow-up | Closure note, owners, due dates, redaction status |
| Conflicting memory or source records | Conflict summary, losing source, winning source, reviewer | Only the reviewed winning fact | Source authority policy, owner decision, evidence ledger entry |
| Test, deploy, or rollback evidence | Command output summary, target, result, skipped checks, rollback status | Current verification or blocker status | Test logs, deploy notes, rollback plan, owner acceptance |
| Research or background note | Cited summary and uncertainty flags | Nothing until reviewed | Source links, reviewer, promotion decision |

## When To Update Long-Term Memory

Update AI Memory after a reviewed change alters accepted project truth, support boundaries, owners, tests, deployment, public routes, or machine artifacts.

- After an active intake file has been reviewed, given a disposition, and archived.
- After a public release, roadmap change, changelog entry, or support-boundary change becomes project truth.
- After an incident or audit closes with confirmed facts, owners, follow-up, and evidence links.
- After explicit human direction to consolidate already-dispositioned archive files into the named LLM Wiki.

In File Handoff plus LLM Wiki mode, do not treat this as only a copy job. A processed active intake file requires source-site work or a durable no-change/defer/block decision, hot-memory updates, long-memory transfer evidence, and then removal from active intake.

## Required Transfer Evidence

- Source project path.
- Final wiki memory path.
- File count and scope of preserved originals.
- SHA-256 checksum or equivalent identity evidence.
- Original disposition and reason.
- Actor and timestamp.
- Evidence that the wiki history, log, index, or graph was updated before removing the source archive copy.
- Evidence ledger update at .uai/progress.uai, CHANGELOG.md, issue, pull request, release note, or handoff acceptance note.

## Promotion Gates

- Accuracy checked against source material.
- Owner or reviewer named.
- Privacy, secrets, customer data, and licensing reviewed.
- Support, certification, security, legal, and endorsement claims checked against public evidence.
- Source authority and conflict-resolution policy applied: Repo Canonical First / Constraints And Owner.
- Target surface named: AGENTS.md, .uai files, canonical docs, code, tests, release notes, roadmap/progress state, or machine artifacts.
- Targeted checks or reason for skipping checks recorded.
- Rollback or recovery implication reviewed: Record And Revert With Approval.

## Stale Or Conflicting Wiki Memory

Resolve conflicts by applying current human instructions, hard constraints, repository rules, and the named owner or reviewer decision.

- If wiki memory conflicts with current AGENTS.md, .uai constraints, public evidence, code, release notes, or human instruction, do not promote it silently.
- Mark stale notes with {STALE_REVIEW_DATE}, {DECIDING_SOURCE}, {REVIEW_OWNER}, and {PROMOTION_DECISION}.
- Keep rejected or background-only notes in the wiki with uncertainty flags instead of turning them into operating instructions.

## What Not To Do

- Do not treat LLM Wiki memory as canonical project truth by itself.
- Do not let wiki memory override AGENTS.md, .uai constraints, current human instructions, repo rules, or public support boundaries.
- Do not automatically write into a repository, WordPress site, package, or public page from wiki memory.
- Do not treat summaries, staged outputs, or hot-context snapshots as proof that original processed reports were preserved.
- Do not remove source archives until transfer evidence and wiki discoverability are recorded.

## Promotion Rule

A long-memory fact becomes operational only after explicit review and promotion into AGENTS.md, .uai files, canonical docs, code, roadmap/progress state, release notes, or machine artifacts.

Why This File Exists

This is a memory-system evidence file from JustAnIota short domain / 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 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: LLM Wiki Memory Plan; Selected Package; Receiver Questions; Operating Boundary; Source Boundary; Suggested Wiki Topography; What This Saves Along The Way; Memory Routing Matrix. 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-240 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LLM Wiki Memory Plan",
    "source_site":  "JustAnIota short domain / JustAnIota.com",
    "source_url":  "https://justaniota.com/",
    "canonical_url":  "https://aiwikis.org/justaniota/files/raw-system-archives-justaniota-short-domain-seo-release-2026-05-05-curre-2e690a00/",
    "source_reference":  "raw/system-archives/justaniota/short-domain-seo-release/2026-05-05/current-source/LLM_WIKI_MEMORY_PLAN.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:2e690a00eaf6a663a15989c25b585f34bb6cff70b664d9dec607a247d86e70a8",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-04T23:35:36.1296270Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-240",
    "duplicate_role":  "primary",
    "related_files":  [

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