2IX Source Memory Guide

2IX.org is the public handoff and registry front door for the workspace. It connects practical project transfer points: what the project is, who owns the current contact path, which package artifacts should be uploaded, and where durable project memory should live.

AIWikis preserves 2IX source memory so humans and agents can recover the setup outcome without treating AIWikis as the 2IX source authority. Current behavior, package state, registry seed data, and production deployment truth must still be checked against the 2IX source root and 2IX-Publish package manifest.

Source Ownership

Surface	Source Authority	AIWikis Role
Public handoff site	2IX.org	Preserve routing and setup memory
Project/contact registry	2IX.org Participants Database plus twoix-registry-seeder	Explain field intent and update triggers
Short-term handoff packets	UAIX.org patterns and local source packets	Route readers to UAIX-style handoff use
Long-term project memory	AIWikis.org reviewed content pages	Preserve public-safe summaries and source boundaries
Upload packages	Workspace package builder and 2IX-Publish	Preserve deployment boundary and package-target notes

Current Setup

• The 2IX WordPress source root contains the custom 2ix block theme.
• The registry surface uses Participants Database pages: /registry/, /registry-directory/, /registry-record/, /registry-profile/, and /registry-thanks/.
• The deployable twoix-registry-seeder plugin seeds one project-owner record for each active top-level workspace project root, excluding *-Publish output folders and tooling folders.
• The shared workspace package builder now includes 2IX so its theme and custom registry plugin are emitted under 2IX-Publish/UPLOAD-THEME and 2IX-Publish/UPLOAD-PLUGIN.

Contact Seed

All seeded project records use Michael Joseph Kappel as project owner contact, with the phone and email stored in the Participants Database record. Update the twoix-registry-seeder project list when a new top-level workspace project is added or when a project gets a different public contact.

Update Triggers

• A new top-level WordPress project root appears in the shared WordPress workspace.
• 2IX registry fields, public directory columns, or Participants Database page routing changes.
• The shared production package version changes and 2IX-Publish needs regenerated upload ZIPs.
• AIWikis home, header, footer, or Browser should show a new or renamed major source site.

Claim Boundaries

Do not claim that AIWikis proves 2IX production deployment, live registry completeness, DNS state, or current plugin activation. AIWikis can say that it preserves a reviewed setup guide and links to the 2IX source memory path. For current upload artifacts, read 2IX-Publish/workspace-deployment-manifest.json after the package build.