Recursive Continuation Prompt — v8.8.37: Baseline Reference for Requirements Recursive Reader-Action Map

Practical Lesson: requirements

As a baseline reference, mk-v8.8.37-next-prompt 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 mk-v8.8.37-next-prompt with the artifact requirements recursive reader-action map. The reader job is to decide how requirements, recursive, and prompt change the reader action implied by Recursive Continuation Prompt — v8.8.37. The first decision is to use requirements as the visible problem and recursive as the check that keeps the lesson grounded. This page is distinct because it asks the reader to separate route, static, and Current work-in-progress rule so the article teaches one named move around requirements.

Pattern Evidence: recursive

The strongest source signals are Recursive Continuation Prompt — v8.8.37; Current work-in-progress rule; Mission for v8.8.37; Hard runtime and architecture constraints; Route requirements. Those signals are read before routing to site-operations/product-readiness/requirements-recursive-reader-action-map, because category metadata is not allowed to write the article by itself. The specific pattern is: identify prompt, decide whether route changes the claim, and keep static tied to reader action.

• Source lesson 1: requirements sets the reader situation, recursive names the review concern, and prompt decides whether the lesson is distinct.
• Source lesson 2: route sets the reader situation, static names the review concern, and runtime decides whether the lesson is distinct.
• Source lesson 3: docs sets the reader situation, continuation names the review concern, and artifact decides whether the lesson is distinct.
• Source lesson 4: files sets the reader situation, zip names the review concern, and mk-v8 decides whether the lesson is distinct.

Baseline reference test:

• Foundation check: define requirements before adding companion distinctions.
• Scope check: use recursive to set the first public boundary.
• Orientation check: make prompt 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 mk-v8.8.37-next-prompt.
• 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 requirements, route, and docs so this page is not interchangeable with a neighboring archive record.

Review Move: prompt

• Use requirements to name the situation a reader can recognize.
• Use recursive to define what evidence belongs in the public article.
• Use prompt to decide whether the page is a new lesson or a duplicate.
• Use route to state what the page does not prove.
• Use static to remove vague, dramatic, or repetitive wording.
• Use runtime to keep the article useful without hidden context.

Publication Rule: site-operations/product-readiness/requirements-recursive-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 requirements, prompt, and runtime. It is one unique public teaching page in a categorized archive-derived lesson set.