Claim Boundary Register

This page records what AIWikis.org may safely claim, what must be routed to UAIX.org, LLMWikis.org, Protocol5.com, ɩ.com / JustAnIota.com, or Neurokinetic.com, Neurocumulus.com, and what remains blocked.

Use this register before writing public copy, package notes, roadmap language, or AI handoff summaries.

Claim Classes

Class	Meaning
Current AIWikis claim	AIWikis can say this about its own local implementation or documentation.
Source-routed claim	AIWikis can summarize, but the source site owns the truth.
Dogfood evidence	AIWikis observed or implemented this locally, but it is not certification or endorsement.
Planned or future	The idea may appear in a roadmap, but not as current support.
Blocked claim	AIWikis must not say this unless source evidence changes.

Safe Current Claims

Claim	Class	Required Wording
AIWikis documents and demonstrates source-governed AI memory systems.	Current AIWikis claim	Tie it to reviewed pages, generated source-file pages, reports, and package evidence.
AIWikis preserves already-dispositioned UAIX, LLMWikis, Protocol5, ɩ.com / JustAnIota.com, and AIWikis archive or source memory when explicitly reviewed.	Current AIWikis claim	Say it is long-term memory, not source-site authority.
AIWikis has reviewed source memory guides for UAIX.org, LLMWikis.org, Protocol5.com, and ɩ.com / JustAnIota.com.	Current AIWikis claim	Say the guides preserve and explain, not replace.
AIWikis has a reviewed source memory guide for Neurokinetic.com setup memory.	Current AIWikis claim	Say the guide preserves setup and routing memory, not source authority or production deployment proof.
AIWikis has a reviewed source memory guide for Neurocumulus.com setup memory.	Current AIWikis claim	Say the guide preserves setup, theme repair, and routing memory, not source authority or production deployment proof.
AIWikis has reviewed source memory guides for IBSE.org and SoftwareCommunity.org setup memory.	Current AIWikis claim	Say the guides preserve setup and routing memory, not source authority, runtime proof, or production deployment proof.
AIWikis has a reviewed source memory guide for 2IX.org registry and package setup memory.	Current AIWikis claim	Say the guide preserves setup, registry seed, and package-routing memory, not source authority, live registry proof, DNS proof, or production deployment proof.
AIWikis has a Cross-Site Memory Atlas and Source Memory Operations Playbook.	Current AIWikis claim	Say they route claims, artifacts, and maintenance work.
AIWikis has a Source-Site Outcome Routing rule.	Current AIWikis claim	Say it explains why source-site staged work does not automatically become AIWikis public truth.
AIWikis preserves original processed source-site reports when explicitly accepted for long memory.	Current AIWikis claim	Point to the raw transfer manifest, file counts, checksums, and public-safe ledger summary; say the copies are provenance, not source-site authority.
AIWikis preserved a 2026-05-03 UAIX recent-work digest.	Current AIWikis claim	Say it copied 23 current-source and processed-intake files into long memory with checksums; UAIX.org remains canonical for current support.
AIWikis preserved a 2026-05-03 LlmWikis recent-work digest.	Current AIWikis claim	Say it copied 25 current-source and processed-input files into long memory with checksums; LLMWikis.org remains the handbook source for current guidance.
AIWikis generates transparent source-file pages from local source workspaces and package mirrors.	Current AIWikis claim	Say public pages redact local absolute paths and generated pages are evidence views.
AIWikis generates a local Project Handoff export.	Dogfood evidence	Say it is local release evidence, not hosted UAIX generator support.
AIWikis packages reviewed Markdown into aiwikis-core/data/pages.	Current AIWikis claim	Say deployment still requires human/operator action.

Source-Routed Claims

Claim	Source Owner	AIWikis Must Say
UAI-1 is the current public exchange contract.	UAIX.org	UAIX.org remains canonical.
AI Memory is the broad portable memory framing.	UAIX.org	AIWikis documents UAIX evidence and dogfood use.
Project Handoff is the transfer-of-ownership configuration.	UAIX.org	AIWikis applies the pattern locally.
Agent File Handoff is the dropped-file intake pattern.	UAIX.org	AIWikis dogfoods the buckets and ledger.
The AI Memory Package Wizard produces generated memory operating files.	UAIX.org	AIWikis tracks outputs and source evidence; UAIX owns the wizard.
The AI Memory Package Wizard exposes Base, Agent File Handoff, LLM Wiki, and combined setup URLs.	UAIX.org	AIWikis can cite the 2026-05-03 digest, but current behavior must be checked against UAIX before reuse.
LLM Wiki setup asks for the wiki root, index, log/evidence path, and promotion owner before using wiki memory.	UAIX.org	AIWikis records this as optional UAIX package-tailoring guidance, not a UAI requirement or sync service.
LLM Wiki structure, metadata, trust labels, governance, and source policy come from LLMWikis.org.	LLMWikis.org	AIWikis demonstrates the pattern and links to the handbook.
LLM Wiki agentic orchestration, task packet, and support escalation guidance comes from LLMWikis.org.	LLMWikis.org	AIWikis can cite the 2026-05-03 digest, but current behavior must be checked against LLMWikis before reuse.
llm-wiki-starter-bundle-v2.7.0.zip is published by LLMWikis.org.	LLMWikis.org	AIWikis consumes or references it; it does not own it.
uai1-project-handoff-v2.7.0.zip is published by UAIX.org.	UAIX.org	AIWikis may mirror it only as UAIX-owned dogfood install evidence.
Protocol5.com is the parent brand and UAI .NET implementation package source.	Protocol5.com	AIWikis preserves package and route evidence; Protocol5 owns implementation distribution.
Protocol5 UAI .NET packages are implementation artifacts, not standards authority.	Protocol5.com for packages; UAIX.org for standards	AIWikis must route UAI-1 standards claims back to UAIX.org.
ɩ.com is the visible JustAnIota brand and JustAnIota.com is the canonical host.	ɩ.com / JustAnIota.com	AIWikis preserves public-site, compact-message tooling, source-memory, and intake-processing evidence under the JustAnIota source system.
ɩ.com / xn--8na.com redirects into the canonical JustAnIota.com package; there is no separate short-domain WordPress codebase after 2026-05-05.	JustAnIota.com	AIWikis preserves the source-site outcome and raw-memory manifest, but the source site remains authoritative for production host configuration.
JustAnIota compact-message tools, keyless JSON/HTML extraction, logo, and sister-theme work are implementation evidence.	ɩ.com / JustAnIota.com for implementation; UAIX.org for UAI-1 standards	AIWikis must route UAI-1 standards, validator, conformance, and governance claims back to UAIX.org.
Neurokinetic.com owns its WordPress site, UAI/LLM Wiki setup, handoff state, theme, and deployment package evidence.	Neurokinetic.com	AIWikis preserves setup memory and routing guidance, but current behavior and production state must be checked against Neurokinetic source files and manifests.
The Neurokinetic setup links to the UAIX AI Memory Package Wizard and LLMWikis LLM Wiki Setup Wizard.	Neurokinetic.com for local use; UAIX.org and LLMWikis.org for upstream wizard behavior	AIWikis can cite the Neurokinetic setup record, but current wizard behavior must be checked against UAIX and LLMWikis before repeating live-support wording.
Neurocumulus.com owns its WordPress site, UAI/LLM Wiki setup, handoff state, theme repair, and deployment package evidence.	Neurocumulus.com	AIWikis preserves setup memory and routing guidance, but current behavior and production state must be checked against Neurocumulus source files and manifests.
The Neurocumulus setup links to the UAIX AI Memory Package Wizard and LLMWikis LLM Wiki Setup Wizard.	Neurocumulus.com for local use; UAIX.org and LLMWikis.org for upstream wizard behavior	AIWikis can cite the Neurocumulus setup record, but current wizard behavior must be checked against UAIX and LLMWikis before repeating live-support wording.
IBSE.org owns its project claims and future implementation artifacts.	IBSE.org	AIWikis preserves setup memory and routing guidance, but current implementation state must be checked against the source root named by the human.
SoftwareCommunity.org owns its WordPress site, UAI/LLM Wiki setup, handoff state, theme, organizer workflows, and deployment evidence.	SoftwareCommunity.org	AIWikis preserves setup memory and routing guidance, but current behavior and production state must be checked against SoftwareCommunity source files and manifests.
2IX.org owns its project handoff site, Participants Database registry, package-upload workflow, and deployment evidence.	2IX.org	AIWikis preserves setup memory and routing guidance, but current registry rows, plugin activation, and production state must be checked against 2IX source files and manifests.

Dogfood Evidence Claims

Evidence	Safe Claim	Unsafe Overreach
Source sync indexed current source files.	AIWikis has current local evidence for those files.	AIWikis is the canonical source for those files.
Package build succeeded.	Local package artifacts were built and smoke-tested.	The live site is deployed or production-verified.
Smoke test passed.	Local checks passed with recorded skips.	The system is certified or externally validated.
Handoff export generated.	Local reviewed wiki memory can feed a compact export.	UAIX certifies the export or hosts a generator.
Archive files were preserved.	AIWikis holds long-term memory after source-site disposition.	The archive copy overrides current source-site pages.
Original processed reports were copied with a manifest.	AIWikis can prove long-memory preservation with file counts and SHA-256 hashes.	Summaries, staged drafts, or raw copies are public truth without review.
A source site created staged drafts.	AIWikis can summarize the outcome after explicit routing.	The staged drafts are already public truth or live AIWikis changes.
UAIX recent work was copied into AIWikis raw memory.	AIWikis can say it preserved provenance for recent UAIX work.	AIWikis is the current UAIX wizard, roadmap, validator, package, or support authority.
LlmWikis recent work was copied into AIWikis raw memory.	AIWikis can say it preserved provenance for recent LlmWikis work.	AIWikis is the current LLMWikis handbook, starter-bundle, agentic-support, or managed-service authority.
JustAnIota intake and current-source evidence was copied into AIWikis source memory.	AIWikis can say it preserved provenance for JustAnIota public-site, compact-message tooling, and File Handoff plus LLM Wiki recovery work.	AIWikis is the JustAnIota source authority, or JustAnIota is the UAI-1 standards authority.
Neurokinetic setup memory was added to AIWikis.	AIWikis can say it preserved setup, routing, and deployment-boundary memory for Neurokinetic.com.	AIWikis is the Neurokinetic source authority, or the local setup proves production deployment or clinical/scientific support.
Neurocumulus setup memory was added to AIWikis.	AIWikis can say it preserved setup, theme repair, routing, and deployment-boundary memory for Neurocumulus.com.	AIWikis is the Neurocumulus source authority, or the local setup proves production deployment, hosted sync, certification, or live-site behavior.
IBSE setup memory was added to AIWikis.	AIWikis can say it preserved setup, routing, and source-root boundary memory for IBSE.org.	AIWikis is the IBSE source authority, or the local scaffold proves a full runtime, DNS control, or production deployment.
SoftwareCommunity setup memory was added to AIWikis.	AIWikis can say it preserved setup, routing, and workflow-boundary memory for SoftwareCommunity.org.	AIWikis is the SoftwareCommunity source authority, or the local setup proves production deployment or current live-site behavior.
2IX registry and package memory was added to AIWikis.	AIWikis can say it preserved setup, routing, registry-seed, and upload-package memory for 2IX.org.	AIWikis is the 2IX source authority, or the local setup proves live registry completeness, DNS control, production deployment, or current live-site behavior.

Blocked Claims

AIWikis must not currently claim:

• UAIX certification, endorsement, conformance approval, or official validation.
• Hosted .uai upload/import validation.
• Automatic repository writes.
• Automatic LLM Wiki synchronization.
• SDK or CLI support.
• Public hosted package generator support.
• WordPress admin installation on behalf of the user.
• Live production deployment from the local workspace.
• DNS control.
• Source-site authority for UAIX.org or LLMWikis.org.
• Source-site authority for Protocol5.com.
• Source-site authority for ɩ.com / JustAnIota.com.
• Source-site authority for Neurokinetic.com.
• Source-site authority for Neurocumulus.com.
• Source-site authority for IBSE.org.
• Source-site authority for SoftwareCommunity.org.
• Source-site authority for 2IX.org.
• Automatic AIWikis publication from source-site Improvement processing.
• Treating summaries or staged artifacts as proof that raw original reports were preserved.
• Staged LLMWikis drafts as reviewed public handbook truth before LLMWikis promotes them.
• LLMWikis agentic guidance as public MCP, A2A, write API, trace exporter, live evaluation, managed runtime, managed service, SDK, CLI, certification, endorsement, automatic ingestion, automatic publication, or deployment support.
• Protocol5.com as UAI-1 standards, validator, registry, roadmap, governance, certification, or conformance authority.
• Protocol5 package existence as certification, endorsement, conformance approval, or production deployment.
• JustAnIota as UAI-1 standards, validator, registry, roadmap, governance, certification, or conformance authority.
• JustAnIota compact-message tools, keyless JSON, HTML extraction, Unicode/PUA experiments, or logo/theme work as certification, endorsement, conformance approval, semantic authority, anonymization proof, or production deployment.
• Neurokinetic.com setup, theme, or memory routing as clinical support, diagnostic support, scientific settlement, certification, endorsement, conformance approval, automatic publication, or production deployment.
• Neurocumulus.com setup, theme repair, or memory routing as certification, endorsement, conformance approval, automatic publication, automatic repository writes, automatic LLM Wiki sync, hosted importer support, or production deployment.
• IBSE.org setup, handoff scaffold, or memory routing as full-runtime proof, DNS proof, certification, endorsement, automatic publication, or production deployment.
• SoftwareCommunity.org setup, theme, or memory routing as certification, endorsement, conformance approval, automatic publication, or production deployment.
• 2IX.org setup, registry seed, package workflow, or memory routing as live registry proof, DNS proof, certification, endorsement, automatic publication, or production deployment.
• Routine syncing or public packaging of generated Protocol5 Prime/Fibonacci numeric route trees.
• Public safety of raw archive material before review.
• LLMWikis endorsement of AIWikis-specific raw/, wiki/, config/, graph, or confidence metadata choices.
• UAIX ownership of AIWikis local Deep Cognitive Archive extensions.

Planned Language

When a future idea is useful but unsupported, use this shape:

Planned or candidate work: [idea]. Current support: [what exists now]. Boundary: [what AIWikis or the source site does not yet provide].

Do not say "coming soon" unless there is a public source roadmap and a clear support path.

Risky Words

These words require evidence and usually need source-site support:

• certify
• validate
• endorse
• official
• automatic
• hosted
• importer
• sync
• SDK
• CLI
• production
• deploy
• compliance
• guarantee

Use them only when the supporting source and current boundary are explicit.

AI-Agent Rule

If a requested claim appears in the blocked list, the agent should refuse the claim politely, explain the current supported evidence, and route the user to the source roadmap or AIWikis roadmap. The answer should not soften a blocked claim into vague marketing language.

Good memory is not just remembering more. It is remembering where truth stops.