Non-Project Memory Packages for Assistants and Social Companions: Baseline Reference for Routing Evidence Map

Learning Point: non-project

As a baseline reference, Non-Project Memory Packages for Assistants and Social Companions should establish the first reader decision and the core vocabulary. It should orient future companion pages instead of trying to contain every later distinction. The public teaching anchor is Non-Project Memory Packages for Assistants and Social Companions with the artifact routing evidence map. The reader job is to audit whether agents can discover, negotiate, and crawl public routes without protected access. The first decision is to use non-project as the visible problem and memory as the check that keeps the lesson grounded. This page is distinct because it asks the reader to separate WAF friction, content negotiation, AI crawling directives, and llms.txt guidance.

Distinct Signal: memory

The strongest source signals are Non-Project Memory Packages for Assistants and Social Companions; Executive Summary; UAIX Wizard Review; What the wizard already does well; The published UAIX data model. Those signals are read before routing to agent-systems/public-wiki-governance/routing-evidence-map, because category metadata is not allowed to write the article by itself. The specific pattern is: identify social, decide whether uaix changes the claim, and keep wizard tied to reader action.

• Source lesson 1: non-project sets the reader situation, memory names the review concern, and social decides whether the lesson is distinct.
• Source lesson 2: uaix sets the reader situation, wizard names the review concern, and packages decides whether the lesson is distinct.
• Source lesson 3: assistants sets the reader situation, summary names the review concern, and assistant decides whether the lesson is distinct.
• Source lesson 4: package sets the reader situation, model names the review concern, and review decides whether the lesson is distinct.

Baseline reference test:

• Foundation check: define non-project before adding companion distinctions.
• Scope check: use memory to set the first public boundary.
• Orientation check: make social understandable without a prior article.
• Vocabulary check: preserve the core terms but leave later deltas for companion pages.
• Entry-point check: the reader should know what decision comes first.

• File role: baseline reference for Non-Project Memory Packages for Assistants and Social Companions.
• Reader question: what first decision should a reader make before acting.
• Editorial move: define the initial public claim and remove platform-specific implementation detail.
• Boundary: do not treat the article as proof that the underlying workflow is active.
• Distinct vocabulary: baseline reference framing scope first-pass orientation combines with non-project, uaix, and assistants so this page is not interchangeable with a neighboring archive record.

Editorial Test: social

• Use non-project to name the situation a reader can recognize.
• Use memory to define what evidence belongs in the public article.
• Use social to decide whether the page is a new lesson or a duplicate.
• Use uaix to state what the page does not prove.
• Use wizard to remove vague, dramatic, or repetitive wording.
• Use packages to keep the article useful without hidden context.

Reader Boundary: agent-systems/public-wiki-governance/routing-evidence-map

A good public version helps future contributors act differently: they can recognize the pattern, check the evidence, and avoid overclaiming. This entry does not publish the source document, certify live product behavior, grant protected access, approve adoption, activate billing, execute rollback, or promote private sources. The boundary for this file is: do not treat connectivity planning as proof that every agent route is live. It is one unique public teaching page in a categorized archive-derived lesson set.