ErrorNotifier Source Memory Guide

ErrorNotifier.com is the source site for the ErrorNotifier WordPress Studio workspace, local AI Memory setup, LLM Wiki routing plan, Agent File Handoff intake, and future ErrorNotifier-specific implementation decisions.

AIWikis preserves ErrorNotifier source memory so humans and agents can recover the setup outcome, where durable memory should live, and which deployment and claim boundaries apply. AIWikis is not the ErrorNotifier.com source authority and does not prove production deployment.

What ErrorNotifier Owns

Area	Source Owner	AIWikis Role
Local WordPress Studio source site	ErrorNotifier.com	Preserve public-safe setup outcome and source-memory guide
Future custom theme, plugin, or product behavior	ErrorNotifier.com	Preserve routing rules and update triggers after review
UAI startup and handoff files	ErrorNotifier.com	Preserve local setup and active-memory rules
LLM Wiki memory plan	ErrorNotifier.com for source truth; AIWikis.org for long memory	Preserve reviewed source-memory nodes

Current 2026-05-16 Outcome

The ErrorNotifier.com setup pass created a local memory baseline:

• Replaced the default Studio AGENTS.md with workspace-aware Project Handoff instructions.
• Added local .uai files for short-term memory, long-term routing, file handoff, and intake index.
• Added agent-file-handoff/Content/, agent-file-handoff/Improvement/, and agent-file-handoff/Archive/.
• Added UAI Memory setup files and an LLM Wiki memory plan.
• Pointed Project Handoff and Agent File Handoff setup to the UAIX AI Memory Package Wizard.
• Pointed LLM Wiki long-memory planning to the LLMWikis Setup Wizard with AIWikis.org as the reviewed long-memory destination.
• Registered ErrorNotifier.com in AIWikis homepage, header, footer, browser registry, and source-side wiki memory.

No active dropped Content or Improvement reports were present during setup, so this pass has no raw source-report preservation manifest.

Current Implementation Boundary

The inspected source tree is a WordPress Studio runtime with bundled WordPress themes and bundled/default plugins only. No custom ErrorNotifier-owned theme, plugin, publish root, or deployment package workflow has been identified yet.

That means AIWikis can preserve the handoff and memory setup, but current product behavior, deployment state, DNS state, and live-site behavior still need source-site or production evidence before anyone repeats those claims.

Reading Path

Need	Start Here
Source-memory overview	wiki/errornotifier/index.md
Concept summary	wiki/concepts/errornotifier-source-memory.md
Setup log	wiki/logs/errornotifier-setup-2026-05-16.md
Local agent front door	ErrorNotifier/AGENTS.md
Local memory files	ErrorNotifier/.uai/
Local handoff buckets	ErrorNotifier/agent-file-handoff/

Update Triggers

Refresh this guide when:

• ErrorNotifier.com changes its custom theme, plugin, public positioning, handoff plan, .uai files, or deployment artifacts;
• active agent-file-handoff/Content/ or agent-file-handoff/Improvement/ files are processed;
• a new preservation manifest copies ErrorNotifier source reports into AIWikis raw memory;
• production deployment evidence is created;
• UAIX or LLMWikis setup guidance changes in a way that affects this site.

Do Not Claim

Do not claim that:

• AIWikis.org is the ErrorNotifier.com source authority.
• The 2026-05-16 setup proves production deployment, live public behavior, DNS control, or custom ErrorNotifier product functionality.
• Raw dropped files are public content merely because they are preserved in AIWikis memory.
• The bundled WordPress themes/plugins are ErrorNotifier-owned product code.
• The UAIX or LLMWikis wizards perform automatic repository writes, automatic publication, automatic LLM Wiki sync, certification, or endorsement for ErrorNotifier.

AI-Agent Rule

When a task asks whether ErrorNotifier long-term memory reached AIWikis, cite this page, the ErrorNotifier sub-wiki index, and the setup log. Then check ErrorNotifier.com source files, Studio database state, and publish manifests for current implementation and deployment state before repeating live-site claims.