Integrating HORMA into UAIX.org: Baseline Reference for Uaix Horma Reader-Action Map

Reader Decision: uaix

As a baseline reference, Integrating HORMA into UAIX.org 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 Integrating HORMA into UAIX.org with the artifact uaix horma reader-action map. The reader job is to decide how uaix, horma, and already change the reader action implied by Integrating HORMA into UAIX.org. The first decision is to use uaix as the visible problem and horma as the check that keeps the lesson grounded. This page is distinct because it asks the reader to separate integration, wizard, and Executive summary so the article teaches one named move around uaix.

What To Preserve: horma

The strongest source signals are Integrating HORMA into UAIX.org; Executive summary; UAIX concepts, structure, audiences, and constraints; What UAIX already publishes; Who UAIX serves today. Those signals are read before routing to memory-systems/uai-handoff/uaix-horma-reader-action-map, because category metadata is not allowed to write the article by itself. The specific pattern is: identify already, decide whether integration changes the claim, and keep wizard tied to reader action.

• Source lesson 1: uaix sets the reader situation, horma names the review concern, and already decides whether the lesson is distinct.
• Source lesson 2: integration sets the reader situation, wizard names the review concern, and boundary decides whether the lesson is distinct.
• Source lesson 3: constraints sets the reader situation, what names the review concern, and integrating decides whether the lesson is distinct.
• Source lesson 4: documentation sets the reader situation, structure names the review concern, and summary decides whether the lesson is distinct.

Baseline reference test:

• Foundation check: define uaix before adding companion distinctions.
• Scope check: use horma to set the first public boundary.
• Orientation check: make already 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 Integrating HORMA into UAIX.org.
• 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, integration, and constraints so this page is not interchangeable with a neighboring archive record.

What To Withhold: already

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

Reuse Check: memory-systems/uai-handoff/uaix-horma-reader-action-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 publish a generic archive-summary frame when the public lesson depends on uaix, already, and boundary. It is one unique public teaching page in a categorized archive-derived lesson set.