UAIX Memory, Long-Running Tasks, and Follow Goals: Baseline Reference for Matching Workflow

Reader Decision: uaix

As a baseline reference, UAIX Memory, Long-Running Tasks, and Follow Goals 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 UAIX Memory, Long-Running Tasks, and Follow Goals with the artifact matching workflow. The reader job is to design matching around participant intent, opportunity fit, and durable project memory. The first decision is to use uaix 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 user roles, matching mechanics, stored project context, and trust controls.

What To Preserve: memory

The strongest source signals are UAIX Memory, Long-Running Tasks, and Follow Goals; Executive summary; What UAIX memory is today; How Follow Goals and long-running work currently fit; Where the current guidance is incomplete. Those signals are read before routing to memory-systems/uai-handoff/matching-workflow, because category metadata is not allowed to write the article by itself. The specific pattern is: identify long-running, decide whether follow changes the claim, and keep goals tied to reader action.

• Source lesson 1: uaix sets the reader situation, memory names the review concern, and long-running decides whether the lesson is distinct.
• Source lesson 2: follow sets the reader situation, goals names the review concern, and guidance decides whether the lesson is distinct.
• Source lesson 3: tasks sets the reader situation, work names the review concern, and where decides whether the lesson is distinct.
• Source lesson 4: example sets the reader situation, runtime names the review concern, and uai decides whether the lesson is distinct.

Baseline reference test:

• Foundation check: define uaix before adding companion distinctions.
• Scope check: use memory to set the first public boundary.
• Orientation check: make long-running 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 UAIX Memory, Long-Running Tasks, and Follow Goals.
• 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 uaix, follow, and tasks so this page is not interchangeable with a neighboring archive record.

What To Withhold: long-running

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

Reuse Check: memory-systems/uai-handoff/matching-workflow

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 turn system design into proof that matching or memory services are live. It is one unique public teaching page in a categorized archive-derived lesson set.