Memory Coverage And Claim Boundaries

--- title: "Memory Coverage And Claim Boundaries" description: "AIWikis now treats coverage and claim safety as first-class memory." slug: "files/aiwikis/wiki-concepts-memory-coverage-and-claim-boundaries-md-4e41f49b" status: "working-draft" trust_level: "generated-evidence" source_status: "current-source-file" content_type: "source-file" generated_by: "tools/sync-source-files.ps1" last_reprocessed: "2026-04-30" source_site: "aiwikis.org" source_url: "https://aiwikis.org/" canonical_url: "https://aiwikis.org/files/aiwikis/wiki-concepts-memory-coverage-and-claim-boundaries-md-4e41f49b/" canonical: "https://aiwikis.org/files/aiwikis/wiki-concepts-memory-coverage-and-claim-boundaries-md-4e41f49b/" source_reference: "wiki/concepts/memory-coverage-and-claim-boundaries.md" file_type: "md" content_category: "llm-wiki" content_hash: "sha256:4e41f49be7d377098ff622e4555c25198acfb678080b1810df3dd85bfad4e728" last_fetched: "2026-04-30T22:07:25.2671233Z" last_changed: "2026-04-30T22:07:00.0082300Z" import_status: "new" duplicate_group_id: "sfg-051" generated_explanation: true explanation_last_generated: "2026-04-30T22:07:25.2671233Z" source_domains:

tags:

related_files:

---

"aiwikis.org"
"ai-memory"
"provenance"
"aiwikis"
"llm-wiki"
""

Memory Coverage And Claim Boundaries

AIWikis now treats coverage and claim safety as first-class memory.

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/files/aiwikis/wiki-concepts-memory-coverage-and-claim-boundaries-md-4e41f49b/
Source reference	`wiki/concepts/memory-coverage-and-claim-boundaries.md`
File type	`md`
Content category	`llm-wiki`
Last fetched	`2026-04-30T22:07:25.2671233Z`
Last changed	`2026-04-30T22:07:00.0082300Z`
Content hash	`sha256:4e41f49be7d377098ff622e4555c25198acfb678080b1810df3dd85bfad4e728`
Import status	`new`
Raw source layer	`data/sources/aiwikis/wiki-concepts-memory-coverage-and-claim-boundaries-md-4e41f49be7d3.md`
Normalized source layer	`data/normalized/aiwikis/wiki-concepts-memory-coverage-and-claim-boundaries-md-4e41f49be7d3.txt`

Current File Content

Structure Preview

Memory Coverage And Claim Boundaries
Root Problem
Fix
Operating Rule
Non-Claims
Related Nodes

Raw Version

---
uai_id: "9dfe3a68-572d-4f94-bf9c-a750ae49f3a2"
type: "concept"
owner: "AIWikis maintainers"
status: "reviewed"
source_status: "local synthesis from reviewed coverage and claim-safety public pages"
sensitivity: "public-safe source-side memory"
agent_use: "load before making broad claims from AIWikis memory or when changing coverage, support-boundary, roadmap, package, or handoff language"
lineage:
  - "content/pages/029-memory-coverage-matrix.md"
  - "content/pages/029-claim-boundary-register.md"
  - "content/pages/027-cross-site-memory-atlas.md"
  - "content/pages/028-source-memory-operations-playbook.md"
  - ".uai/decisions.uai"
source_trace:
  - "docs/lessons-learned.md"
  - "docs/recommendation-adjustments.md"
  - "tools/smoke-test.ps1"
confidence: 0.86
confidence_label: "reviewed-local"
last_linted: "2026-04-30T21:25:00Z"
handoff_export: "include"
aliases:
  - "Memory Coverage Matrix"
  - "Claim Boundary Register"
  - "Coverage Is Not Authority"
---

# Memory Coverage And Claim Boundaries

AIWikis now treats coverage and claim safety as first-class memory.

The important distinction is this: AIWikis can remember a source domain deeply without becoming the source authority for that domain.

## Root Problem

A strong memory site creates a subtle risk. If it preserves enough detail, future agents may start treating the memory copy as the authoritative source.

That risk is highest when:

- AIWikis has generated file pages for a source system.
- AIWikis has package evidence for a source-owned artifact.
- AIWikis has archived old source-site reports.
- AIWikis has dogfood checks that passed locally.
- A user asks for a confident answer from AIWikis instead of from the source site.

## Fix

AIWikis now has two explicit registers:

- `content/pages/029-memory-coverage-matrix.md` maps domains to source owners, AIWikis surfaces, coverage state, and update triggers.
- `content/pages/029-claim-boundary-register.md` classifies claims as current AIWikis claims, source-routed claims, dogfood evidence, planned/future language, or blocked claims.

Together they tell future agents whether AIWikis has enough local evidence and whether that evidence is allowed to become a public claim.

## Operating Rule

Before making a broad claim, answer:

1. Is the domain covered, partially covered, source-only, or blocked?
2. Who owns the source truth?
3. Is this a current AIWikis claim, source-routed claim, dogfood evidence, planned idea, or blocked claim?
4. Which route or report proves the evidence?
5. Which wording keeps authority in the right place?

If the answer is blocked, do not soften the claim into marketing language.

## Non-Claims

Coverage does not create certification, endorsement, conformance, hosted validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, production deployment, package validation, or source-site authority.

## Related Nodes

- [[cross-site-memory-operations]]
- [[system-memory-archive]]
- [[deep-cognitive-archive]]
- [[uai-handoff-export-loop]]
- [[intake-outcome-ledger]]
- [[../index]]

Why This File Exists

This is a LLM Wiki memory file from aiwikis.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 belongs to the source-side wiki layer. It preserves a focused concept, source proxy, graph record, or operating rule so the public site can cite reviewed conclusions without flattening every reason into a single long page.

Structure

The file is structured around these visible headings: Memory Coverage And Claim Boundaries; Root Problem; Fix; Operating Rule; Non-Claims; Related Nodes. 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.

Provenance And History

Current observation: 2026-04-30T22:07:25.2671233Z
Source origin: current-source-workspace
Retrieval method: local-source-workspace
Duplicate group: sfg-051 (primary)
Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Memory Coverage And Claim Boundaries",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/wiki-concepts-memory-coverage-and-claim-boundaries-md-4e41f49b/",
    "source_reference":  "wiki/concepts/memory-coverage-and-claim-boundaries.md",
    "file_type":  "md",
    "content_category":  "llm-wiki",
    "content_hash":  "sha256:4e41f49be7d377098ff622e4555c25198acfb678080b1810df3dd85bfad4e728",
    "last_fetched":  "2026-04-30T22:07:25.2671233Z",
    "last_changed":  "2026-04-30T22:07:00.0082300Z",
    "import_status":  "new",
    "duplicate_group_id":  "sfg-051",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-04-30T22:07:25.2671233Z"
}

Memory Coverage And Claim Boundaries

Memory Coverage And Claim Boundaries

Metadata

Current File Content

Structure Preview

Raw Version

Why This File Exists

Role

Structure

Prompt-Size And Retrieval Benefit

How To Use It

Update Requirements

Related Pages

Provenance And History

Machine-Readable Metadata