50 MIRENA source context and project control prompts for clean setup, clear gates, and safe handoff.

Run Source Context Setup Pack for [TARGET].

Run Source Context Setup Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Create the project control base before page discovery, mapping, briefing, rewriting, linking, or production begins.

Complete these tasks in order:
1. Build the Source Context Profile.
2. Define the site purpose, audience, offer, and target region.
3. Rank the primary and secondary entity sets.
4. Define allowed topic lanes, blocked topic lanes, and hard exclusions.
5. Record internal link targets and approved proof sources.
6. Choose the next setup route without creating page ideas.

Return the result with these fields:
- source context profile
- site purpose
- audience
- offer
- target region
- primary entities
- secondary entities
- allowed topic lanes
- blocked topic lanes
- proof sources
- internal link targets
- blockers
- review-needed items
- next setup route

Control rules:
- Stop when the site purpose, audience, offer, or allowed topic lanes are unclear.
- Do not create a page queue.
- Do not create a topical map, brief, draft, rewrite, link map, information gain plan, SERP plan, or schema note.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Project Intake Pack for [TARGET].

Run Project Intake Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Classify supplied files, URLs, exports, notes, and previous MIRENA work before any weak input can drive the project.

Complete these tasks in order:
1. Identify every supplied input.
2. Classify each input by type, source quality, and likely use.
3. Separate setup inputs from downstream production inputs.
4. Flag missing files, conflicting records, stale material, and risky inputs.
5. Mark each input keep, hold, ignore, or review.
6. Recommend the safe processing order and next setup pack.

Return the result with these fields:
- input name or label
- input type
- source quality
- setup value
- downstream value
- risk
- missing field
- keep, hold, ignore, or review
- recommended processing order
- next setup route

Control rules:
- Do not extract raw page ideas.
- Do not let an unverified or stale file override approved source context.
- Route each input before any downstream analysis begins.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Topic Lane Control Pack for [TARGET].

Run Topic Lane Control Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Set the project’s topical boundary before any proposed page can enter a map or publishing queue.

Complete these tasks in order:
1. Define allowed topic lanes.
2. Define blocked topic lanes.
3. Define hard exclusions.
4. Define adjacent-topic rules.
5. Define page-versus-content-block rules.
6. Define topic-drift warnings.
7. Define the review route for uncertain topics.

Return the result with these fields:
- allowed topic lane
- reason it belongs
- blocked topic lane
- reason it is blocked
- hard exclusion
- adjacent-topic rule
- page-versus-content-block rule
- drift warning
- review-needed topic
- next setup route

Control rules:
- Do not approve pages.
- Do not build the topical map.
- Treat uncertain adjacency as review-needed rather than silently expanding the site.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Source Context Profile for [TARGET].

Run Source Context Profile for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Create or repair the compact project profile that every later control check must use.

Complete these tasks in order:
1. Name the site, offer, audience, region, entities, topic boundaries, page inventory, proof, and desired output.
2. Mark missing and conflicting fields.
3. Record the approval state.

Return the result with these fields:
- profile field
- current value
- source
- status
- conflict
- missing value
- approval state
- next setup route

Control rules:
- Do not infer a business fact when the source is missing.
- Do not create page ideas.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Site Purpose Definition for [TARGET].

Run Site Purpose Definition for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Give the site one clear role, value, and operating boundary.

Complete these tasks in order:
1. State what the site does.
2. State what it does not do.
3. Name the user outcome and project role.
4. Flag competing or vague purposes.

Return the result with these fields:
- site purpose
- primary user outcome
- included role
- excluded role
- conflict
- approval state
- next setup route

Control rules:
- Do not use a broad industry label as the purpose.
- Do not combine unrelated offers into one purpose.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Audience Definition for [TARGET].

Run Audience Definition for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Define the primary audience by role, state, need, skill, and decision context.

Complete these tasks in order:
1. Name the primary audience.
2. Name optional secondary audiences.
3. Record skill, buyer state, problem, and exclusion.
4. Flag audience conflicts.

Return the result with these fields:
- primary audience
- secondary audience
- user state
- skill level
- need
- excluded audience
- conflict
- next setup route

Control rules:
- Reject labels such as everyone, businesses, or marketers without a narrower state.
- Do not let a secondary audience displace the primary one.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Offer Definition for [TARGET].

Run Offer Definition for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Define what the site sells, teaches, supports, or provides and the conditions attached to it.

Complete these tasks in order:
1. Name the offer.
2. Describe the user job and benefit.
3. Record access, price model, conditions, and exclusions.
4. Flag unsupported or conflicting offer claims.

Return the result with these fields:
- offer name
- offer type
- user job
- benefit
- commercial model
- condition
- exclusion
- claim risk
- next setup route

Control rules:
- Do not turn a desired positioning claim into a verified fact.
- Keep platform, payment, and service boundaries explicit.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Region Definition for [TARGET].

Run Region Definition for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Set geography, language, localization, spelling, availability, and regulatory context.

Complete these tasks in order:
1. Name the target region and language.
2. Record local availability and spelling rules.
3. Record regulated or location-specific claims.
4. Flag missing localization sources.

Return the result with these fields:
- target region
- language
- spelling standard
- availability rule
- local proof need
- regulatory note
- next setup route

Control rules:
- Do not imply service in an unconfirmed region.
- Do not reuse local claims without current local evidence.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Primary Entity Set for [TARGET].

Run Primary Entity Set for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Rank the entities that must lead the site and define the attributes that make each one relevant.

Complete these tasks in order:
1. Extract candidate entities.
2. Rank the primary set.
3. Attach defining attributes and approved relationships.
4. Remove broad or off-context entities.

Return the result with these fields:
- primary entity
- entity type
- weight
- defining attribute
- approved relationship
- excluded association
- source
- next setup route

Control rules:
- Do not promote a high-volume term when it weakens site identity.
- Keep each entity tied to a stated audience, offer, or workflow.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Secondary Entity Set for [TARGET].

Run Secondary Entity Set for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Select supporting entities that add depth without competing with the primary entity stack.

Complete these tasks in order:
1. Extract related entities.
2. Classify support, comparison, proof, and route roles.
3. Attach each entity to a primary owner.
4. Block dilution and redundant entity groups.

Return the result with these fields:
- secondary entity
- role
- primary owner
- relationship
- page or content-block use
- dilution risk
- next setup route

Control rules:
- Do not add an entity because competitors mention it when it lacks project fit.
- Every secondary entity needs a primary owner.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Allowed Topic Lanes for [TARGET].

Run Allowed Topic Lanes for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Define the topic lanes that directly reinforce the approved site purpose, entities, audience, and workflows.

Complete these tasks in order:
1. List allowed lanes.
2. State why each lane belongs.
3. Name the likely page or cluster owner.
4. Record review conditions for narrow exceptions.

Return the result with these fields:
- allowed lane
- reason
- primary entity
- audience fit
- owner
- condition
- next setup route

Control rules:
- Do not treat broad industry relevance as sufficient fit.
- Keep allowed lanes specific enough to guide a page decision.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Blocked Topic Lanes for [TARGET].

Run Blocked Topic Lanes for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Record topics that look adjacent but should not enter the site or current project.

Complete these tasks in order:
1. List blocked lanes.
2. State the conflict with audience, offer, entity, workflow, or route.
3. Name any existing page that should absorb a narrow subtopic.
4. Set the review owner.

Return the result with these fields:
- blocked lane
- reason
- conflicting entity or audience
- possible existing owner
- review owner
- next setup route

Control rules:
- Do not soften a confirmed boundary into an optional note.
- Do not block a topic without recording the reason.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Hard Exclusions for [TARGET].

Run Hard Exclusions for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Set non-negotiable topic, claim, audience, privacy, legal, and workflow exclusions.

Complete these tasks in order:
1. List each hard exclusion.
2. Classify its type.
3. State the trigger and required action.
4. Set the escalation or rejection rule.

Return the result with these fields:
- hard exclusion
- type
- trigger
- reason
- required action
- escalation owner
- next setup route

Control rules:
- Hard exclusions override scores and commercial value.
- Do not proceed when the exclusion status is uncertain.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Adjacent Topic Rules for [TARGET].

Run Adjacent Topic Rules for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Decide when a related topic becomes a page, a content block, an internal link, a hold, or an exclusion.

Complete these tasks in order:
1. Identify the adjacent topic.
2. Check entity, buyer, workflow, and link fit.
3. Choose page, content block, link, hold, or block.
4. Record the boundary condition.

Return the result with these fields:
- adjacent topic
- fit finding
- decision
- existing owner
- boundary condition
- reason
- next setup route

Control rules:
- Do not approve adjacency from lexical similarity alone.
- A separate page needs a distinct user job and route.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Page Queue Approval Pack for [TARGET].

Run Page Queue Approval Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Review a proposed page queue and decide which ideas become pages, content blocks, merges, holds, or rejections.

Complete these tasks in order:
1. Import the page queue without adding new items.
2. Score each proposed page for source-context fit.
3. Score buyer, workflow, link, and differentiation fit.
4. Compare each proposal with existing page owners.
5. Decide page, content block, merge, hold, or reject.
6. Add rejection or revision notes.
7. Route approved items without creating briefs or drafts.

Return the result with these fields:
- proposed page
- target entity or topic
- source-context fit
- buyer fit
- workflow fit
- link fit
- differentiation fit
- page, content block, merge, hold, or reject
- reason
- required internal links
- next workflow route

Control rules:
- Do not expand the supplied page list unless the user asks for discovery.
- Do not create a brief or draft.
- A page decision must have one canonical owner and one reason.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Guardrail Scoring Pack for [TARGET].

Run Guardrail Scoring Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Apply a repeatable scoring model to topics, pages, findings, or workflow requests before approval.

Complete these tasks in order:
1. Score source-context, topic, and entity fit.
2. Score buyer, workflow, link, and differentiation fit.
3. Record proof support and drift risk.
4. Record the evidence for every high or low score.
5. Decide approve, revise, hold, or reject.
6. Choose the next setup or downstream route.

Return the result with these fields:
- item
- item type
- source-context score
- topic-fit score
- entity-fit score
- buyer-fit score
- workflow-fit score
- link-fit score
- differentiation score
- proof support
- drift risk
- approve, revise, hold, or reject
- reason
- next workflow route

Control rules:
- Do not approve an item with unclear source-context fit.
- Do not treat a score as proof of search performance.
- Hard exclusions and wrong-audience conflicts override a high total.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Page Queue Import for [TARGET].

Run Page Queue Import for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Load a proposed page list without altering, expanding, or prematurely approving it.

Complete these tasks in order:
1. Parse each supplied item.
2. Preserve source labels and order.
3. Normalize title, URL, topic, intent, and proposed role.
4. Flag duplicates and malformed rows.

Return the result with these fields:
- queue item ID
- original label
- normalized title
- URL
- topic
- intent
- proposed role
- duplicate flag
- input issue
- next setup route

Control rules:
- Do not add page ideas.
- Keep the original source and row identity.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Page Queue Scoring for [TARGET].

Run Page Queue Scoring for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Score every imported queue item against the approved project controls.

Complete these tasks in order:
1. Score source-context, buyer, workflow, link, and differentiation fit.
2. Record evidence for each score.
3. Flag hard exclusions, duplicates, proof gaps, and route gaps.
4. Recommend a provisional decision.

Return the result with these fields:
- queue item ID
- five fit scores
- evidence
- hard-stop flag
- duplicate flag
- proof gap
- route gap
- provisional decision

Control rules:
- Do not let the score override a hard exclusion.
- Do not approve a page without an owner and route.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Page Approval Gate for [TARGET].

Run Page Approval Gate for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Issue the human-controlled page, content-block, merge, hold, or reject decision.

Complete these tasks in order:
1. Review score evidence and stop conditions.
2. Compare existing owners.
3. Choose one decision.
4. Record approver, reason, dependencies, and route.

Return the result with these fields:
- item
- decision
- canonical owner
- reason
- approver
- dependency
- required change
- next workflow route

Control rules:
- Approval remains human-controlled.
- Do not create a brief or draft inside the gate.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Page Rejection Notes for [TARGET].

Run Page Rejection Notes for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Create a reusable record explaining why a proposed page was rejected, merged, or held.

Complete these tasks in order:
1. Name the rejected or held item.
2. Record the failing control and evidence.
3. Name the existing owner or blocked lane.
4. State what would need to change for review.

Return the result with these fields:
- item
- decision
- failed control
- evidence
- existing owner
- blocked lane
- revision condition
- review date or owner

Control rules:
- Do not hide the rejection reason.
- Do not recycle the same idea under a new title without resolving the cause.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Page vs Section Guard for [TARGET].

Run Page vs Section Guard for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Decide if a user need warrants its own URL or belongs inside an existing page.

Complete these tasks in order:
1. Compare intent, user task, owner, proof, format, and next route.
2. Check search-result and current-site overlap.
3. Choose page, content block, FAQ, table, merge, or hold.
4. Record the canonical owner.

Return the result with these fields:
- topic or query
- distinct user task
- existing owner
- overlap finding
- recommended form
- canonical owner
- reason
- next setup route

Control rules:
- Minor wording differences do not justify separate URLs.
- A new page needs a distinct job, owner, and route.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Topic Drift Check for [TARGET].

Run Topic Drift Check for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Detect when a proposed item moves outside the approved entity, audience, offer, or workflow boundary.

Complete these tasks in order:
1. Compare the item with allowed, blocked, and adjacent lanes.
2. Check entity and buyer displacement.
3. Measure route and owner clarity.
4. Return pass, revise, hold, or block.

Return the result with these fields:
- item
- approved lane
- drift signal
- displaced entity or audience
- route issue
- decision
- reason
- next setup route

Control rules:
- Do not treat query volume as permission to drift.
- Hard exclusions return block.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Buyer Fit Check for [TARGET].

Run Buyer Fit Check for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Test if the proposed page serves a real need for the approved audience before, during, or after the offer.

Complete these tasks in order:
1. Name the target audience and user state.
2. State the page’s buyer or support job.
3. Check the conversion or support route.
4. Flag broad, low-quality, or wrong-audience demand.

Return the result with these fields:
- item
- target audience
- user state
- buyer job
- fit score
- route
- wrong-audience flag
- reason

Control rules:
- Traffic potential alone does not prove buyer fit.
- Do not use a broad audience label.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Workflow Fit Check for [TARGET].

Run Workflow Fit Check for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Test whether a page or task connects to an approved MIRENA output, offer, support path, or workflow stage.

Complete these tasks in order:
1. Name the workflow or offer connection.
2. State the input and expected downstream output.
3. Check handoff feasibility.
4. Return fit, revise, hold, or reject.

Return the result with these fields:
- item
- workflow connection
- input
- expected output
- handoff feasibility
- fit score
- decision
- reason

Control rules:
- Do not invent a workflow connection.
- Do not execute the downstream task.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Link Fit Check for [TARGET].

Run Link Fit Check for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Test whether a page strengthens a meaningful parent, sibling, proof, support, or next-step route.

Complete these tasks in order:
1. Name the parent or hub.
2. Name likely inbound sources.
3. Name useful outbound destinations.
4. Check orphan, circular, and forced-link risk.

Return the result with these fields:
- item
- parent or hub
- inbound sources
- outbound targets
- link purpose
- orphan risk
- fit score
- decision

Control rules:
- Do not approve a page with no defensible route.
- Do not use internal links only to move authority.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Differentiation Fit Check for [TARGET].

Run Differentiation Fit Check for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Test if the item can add useful proof, a decision model, first-hand detail, or a missing relationship.

Complete these tasks in order:
1. Identify repeated result-set or existing-site coverage.
2. Name the proposed information gain.
3. Check proof feasibility.
4. Choose approve, revise, merge, hold, or reject.

Return the result with these fields:
- item
- repeated coverage
- new relationship or evidence
- proof feasibility
- differentiation score
- decision
- reason
- next workflow route

Control rules:
- A new title is not information gain.
- Do not approve a distinction that lacks proof or user value.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Focus Score for [TARGET].

Run Focus Score for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Rate how strongly the project, cluster, or queue reinforces the approved site purpose and entity hierarchy.

Complete these tasks in order:
1. Score purpose alignment, entity concentration, lane discipline, buyer clarity, route clarity, and dilution risk.
2. List the items lowering focus.
3. Recommend keep, repair, merge, hold, or block actions.

Return the result with these fields:
- focus score
- purpose alignment
- entity concentration
- lane discipline
- buyer clarity
- route clarity
- dilution risk
- repair action

Control rules:
- Do not use one score to hide conflicting evidence.
- Report the factors and items behind the total.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Internal Link Control Pack for [TARGET].

Run Internal Link Control Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Set page-role, target, anchor, commercial-route, and orphan-risk rules before downstream link work begins.

Complete these tasks in order:
1. Identify priority link targets and protected pages.
2. Define hub, support, proof, and commercial routes.
3. Define preferred anchors and anchors to avoid.
4. Define source-page and destination-page rules.
5. Flag orphan risks and broken route assumptions.
6. Route link rules into the selected downstream workflow.

Return the result with these fields:
- priority target page
- page role
- link purpose
- preferred anchor
- anchors to avoid
- source page type
- destination page type
- commercial route
- orphan risk
- next workflow route

Control rules:
- Do not build the full internal link map.
- Do not force a link where the user path or entity relationship is weak.
- Keep protected-page ownership visible.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Protected Pages for [TARGET].

Run Protected Pages for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Record pages whose ownership, intent, links, proof, or conversion role must not be damaged by new work.

Complete these tasks in order:
1. List protected URLs.
2. Record page role, owned intent, primary entity, critical links, and protected elements.
3. Name changes that require review.

Return the result with these fields:
- protected URL
- page role
- owned intent
- primary entity
- protected links
- protected element
- change requiring review
- owner

Control rules:
- Do not merge or rewrite a protected page without an explicit decision.
- Keep the canonical owner visible in page-queue review.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Pages to Rewrite for [TARGET].

Run Pages to Rewrite for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Mark existing pages that keep their URL but need structural, intent, proof, entity, link, or conversion repairs.

Complete these tasks in order:
1. List rewrite candidates.
2. Record the retained owner and URL.
3. Name the repair reasons and protected elements.
4. Choose rewrite priority and route.

Return the result with these fields:
- URL
- current role
- retained owner
- repair reason
- protected element
- priority
- rewrite route
- approval state

Control rules:
- Do not rewrite before the owner and keep/remove decisions are approved.
- Do not change a page role silently.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Pages to Merge for [TARGET].

Run Pages to Merge for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Record overlapping pages that should be combined under one canonical owner.

Complete these tasks in order:
1. List source and destination URLs.
2. Compare intent, entities, proof, links, and performance evidence.
3. Choose the canonical owner.
4. Record content, redirect, and link-transfer requirements.

Return the result with these fields:
- source URL
- destination URL
- overlap reason
- canonical owner
- content to keep
- redirect need
- link transfer
- approval state

Control rules:
- Do not merge different user jobs into one mixed-intent page.
- Do not remove a URL until redirect and link consequences are reviewed.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Pages to Block for [TARGET].

Run Pages to Block for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Record page ideas or URLs that must not enter the current site, map, brief, or production queue.

Complete these tasks in order:
1. List the blocked page or idea.
2. Name the hard boundary or failed fit check.
3. Record any existing owner or off-site route.
4. Set the review condition.

Return the result with these fields:
- blocked item
- blocked URL
- failed control
- reason
- existing owner
- off-site route
- review condition
- owner

Control rules:
- Do not disguise a blocked idea under a new title.
- Do not delete a live page without technical and editorial review.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Internal Link Targets for [TARGET].

Run Internal Link Targets for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Create the approved list of pages that downstream maps, briefs, and rewrites should support.

Complete these tasks in order:
1. List destination URLs.
2. Record role, entity, user need, route purpose, priority, and source-page types.
3. Flag missing or unsuitable destinations.

Return the result with these fields:
- target URL
- page role
- entity
- user need
- link purpose
- priority
- source-page type
- missing-destination flag

Control rules:
- Do not add a destination that conflicts with page ownership.
- Do not use generic route descriptions.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Anchor Rules for [TARGET].

Run Anchor Rules for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Set truthful, varied, entity-aware anchor rules for approved internal routes.

Complete these tasks in order:
1. Define preferred anchor patterns.
2. Define anchors to avoid.
3. Map anchors to intent and destination role.
4. Set repetition and placement rules.

Return the result with these fields:
- destination
- preferred anchor
- alternate anchor
- intent
- anchor to avoid
- placement rule
- repetition rule
- review note

Control rules:
- Do not use anchors that promise a page does not deliver.
- Avoid generic anchors when a specific destination can be named.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Proof and Evidence Control Pack for [TARGET].

Run Proof and Evidence Control Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Define approved evidence, unsupported claim rules, first-hand input needs, and proof gaps before production.

Complete these tasks in order:
1. Identify approved and missing proof sources.
2. Identify claims that need support.
3. Identify claims to avoid.
4. Define first-hand input and example needs.
5. Define evidence-quality and citation rules.
6. Route the proof record into the next approved workflow.

Return the result with these fields:
- approved proof source
- missing proof source
- claim type
- support needed
- claim to avoid
- first-hand input need
- example source
- evidence rule
- risk
- next workflow route

Control rules:
- Do not invent proof.
- Do not move unsupported claims into a brief or draft.
- Mark time-sensitive facts for current-source review.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Tone and Compliance Control Pack for [TARGET].

Run Tone and Compliance Control Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Set voice, reader tone, allowed wording, blocked wording, claims style, and legal or compliance notes before writing starts.

Complete these tasks in order:
1. Define the brand voice and reader tone.
2. Define allowed and blocked wording.
3. Define claims style and risk language.
4. Record legal, regulatory, accessibility, and editorial notes.
5. Define rewrite rules for non-compliant language.
6. Route the language controls into the next approved workflow.

Return the result with these fields:
- brand voice rule
- reader tone rule
- allowed phrase
- blocked phrase
- claims-style rule
- compliance note
- risk note
- rewrite rule
- next workflow route

Control rules:
- Do not create the page copy.
- Do not let tone rules override source context or factual accuracy.
- Separate hard restrictions from editorial preferences.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Proof Source Inventory for [TARGET].

Run Proof Source Inventory for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Record the evidence sources available to support claims, comparisons, examples, and first-hand observations.

Complete these tasks in order:
1. List each source.
2. Classify source type, owner, date, scope, reliability, and claim support.
3. Mark current, stale, missing, restricted, or review-needed.

Return the result with these fields:
- source label
- source type
- owner
- date
- supported claim
- scope
- quality
- status
- restriction
- next setup route

Control rules:
- Do not treat a competitor claim as independent proof.
- Mark time-sensitive evidence for current review.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Claims Guard for [TARGET].

Run Claims Guard for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Control which factual, comparative, commercial, legal, and performance claims can enter later work.

Complete these tasks in order:
1. List proposed claims.
2. Map each claim to evidence.
3. Classify approved, qualified, unsupported, prohibited, or time-sensitive.
4. Write the safe wording rule.

Return the result with these fields:
- claim
- claim type
- evidence
- status
- qualification
- prohibited wording
- safe wording rule
- review owner

Control rules:
- No ranking, traffic, lead, sale, or rich-result guarantee.
- Unsupported claims remain blocked.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Tone Rules for [TARGET].

Run Tone Rules for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Set the voice, sentence style, reading level, preferred vocabulary, blocked wording, and CTA style.

Complete these tasks in order:
1. Define the brand voice and reader relationship.
2. Set sentence and paragraph rules.
3. List preferred and blocked terms.
4. Define CTA and correction rules.

Return the result with these fields:
- voice rule
- reader relationship
- sentence rule
- reading level
- preferred term
- blocked term
- CTA rule
- rewrite rule

Control rules:
- Tone does not override factual precision or accessibility.
- Separate hard blocks from style preferences.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Compliance Notes for [TARGET].

Run Compliance Notes for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Record legal, privacy, accessibility, regulatory, platform, and editorial conditions that affect the project.

Complete these tasks in order:
1. List each condition.
2. Name the affected page types and claims.
3. Record required review, source, owner, and stop condition.
4. Set the update trigger.

Return the result with these fields:
- condition
- affected asset
- required review
- required source
- owner
- stop condition
- update trigger
- approval state

Control rules:
- Do not present this control record as legal advice.
- A missing required review remains a blocker.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Workflow Routing Pack for [TARGET].

Run Workflow Routing Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Route approved inputs, pages, topics, or findings to the correct MIRENA workflow without starting that work.

Complete these tasks in order:
1. Identify the item and its current state.
2. Check source-context and approval status.
3. Choose one route from the approved route list.
4. Record the reason, blocker, and required input.
5. Assign the next owner or action.
6. Prepare a handoff note.

Return the result with these fields:
- item
- item type
- current state
- source-context fit
- route
- reason
- blocker
- required input
- owner or next action
- handoff note

Control rules:
- Only route the work.
- Do not execute the selected downstream workflow.
- Schema cues remain blocked until visible copy has human approval.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Local Context File Pack for [TARGET].

Run Local Context File Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Create a portable plain-text project-state record for later sessions, team handoff, or local archiving.

Complete these tasks in order:
1. Record project identity, site purpose, audience, offer, region, and primary entities.
2. Record allowed and blocked topic lanes.
3. Record page-queue state and protected pages.
4. Record proof, link, tone, and compliance rules.
5. Record approved decisions, open blockers, and current route.
6. Create a copy-ready restart block.

Return the result with these fields:
- project identity
- source-context summary
- topic-boundary summary
- page-queue state
- protected-page state
- proof and link controls
- tone and compliance controls
- approved decisions
- open blockers
- current workflow route
- restart block

Control rules:
- Do not include passwords, payment data, or restricted client material.
- Mark unresolved decisions as pending rather than silently treating them as approved.
- Do not start the next workflow.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Project Restart Pack for [TARGET].

Run Project Restart Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Restore a saved project safely, verify what is still current, and identify the next incomplete control gate.

Complete these tasks in order:
1. Load the saved context file and previous approved outputs.
2. Compare saved state with current files, URLs, rules, and project goals.
3. Mark current, stale, conflicting, missing, and review-needed records.
4. Restore approved decisions without repeating completed work.
5. Identify the next incomplete control gate.
6. Create the restart handoff.

Return the result with these fields:
- restored project identity
- current records
- stale records
- conflicts
- missing inputs
- approved decisions restored
- next incomplete gate
- restart blocker
- next setup route

Control rules:
- Do not assume a saved record is still current.
- Do not overwrite a newer approved decision with an older local file.
- Do not skip setup QA after a major project change.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Final Setup Validation Pack for [TARGET].

Run Final Setup Validation Pack for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Run the final project-control gate and stop downstream work when any blocking setup field remains incomplete.

Complete these tasks in order:
1. Check the thirteen setup-gate fields.
2. Separate complete, incomplete, conflicting, and review-needed fields.
3. Confirm page-queue, link, proof, tone, compliance, and route controls.
4. Confirm approval ownership and open blockers.
5. Issue pass, revise, hold, or fail.
6. Prepare the next-workflow handoff only after a pass.

Return the result with these fields:
- setup field
- status
- evidence
- conflict
- blocking gap
- review-needed item
- setup decision
- approval owner
- next workflow route
- handoff readiness

Control rules:
- Do not pass when a core source-context field is missing.
- Do not treat optional polish as a substitute for missing project purpose or boundaries.
- Do not start the next workflow.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Local Context File Builder for [TARGET].

Run Local Context File Builder for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Create the portable local project-state file without starting a new analysis pass.

Complete these tasks in order:
1. Assemble approved context, boundaries, queue state, protected pages, proof, links, tone, compliance, route, and blockers.
2. Add version and approval status.
3. Create a compact restart block.

Return the result with these fields:
- local context file
- version
- approval state
- open blockers
- current route
- restart block

Control rules:
- Exclude sensitive credentials and restricted data.
- Do not mark pending fields approved.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Master Context Update for [TARGET].

Run Master Context Update for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Apply approved changes to the master context while preserving version history and unresolved conflicts.

Complete these tasks in order:
1. Compare proposed changes with the current master context.
2. Classify add, replace, deprecate, conflict, or pending.
3. Record reason, approver, and affected workflows.
4. Issue a new version.

Return the result with these fields:
- field
- old value
- proposed value
- change type
- reason
- approver
- affected workflow
- conflict
- new version

Control rules:
- Only approved changes can replace the master value.
- Keep the previous version and conflict record.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Session Restart Setup for [TARGET].

Run Session Restart Setup for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Prepare the exact context, completed gates, open blockers, and next module for a new MIRENA session.

Complete these tasks in order:
1. Load the latest approved context version.
2. List completed controls and outputs.
3. List open blockers and pending approvals.
4. Name the next module and required input.
5. Create the restart prompt.

Return the result with these fields:
- context version
- completed controls
- approved outputs
- open blockers
- pending approvals
- next module
- required input
- restart prompt

Control rules:
- Do not repeat completed work unless a relevant input changed.
- Do not skip the next incomplete gate.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Next Workflow Route for [TARGET].

Run Next Workflow Route for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Choose the next MIRENA workflow for one approved item and state the required input and owner.

Complete these tasks in order:
1. Identify the approved item and current state.
2. Choose one route.
3. Record the route reason, required input, owner, blocker, and stop condition.
4. Prepare the handoff note.

Return the result with these fields:
- item
- current state
- selected route
- reason
- required input
- owner
- blocker
- stop condition
- handoff note

Control rules:
- Do not run the selected workflow.
- Schema cues remain blocked until approved visible copy exists.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Handoff Contract for [TARGET].

Run Handoff Contract for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Create the formal contract between the approved setup and one downstream workflow.

Complete these tasks in order:
1. Name the item, source-context version, approval state, route, owner, required input, expected output, exclusions, proof, links, and return condition.
2. Record the acceptance gate.

Return the result with these fields:
- item
- source-context version
- approval state
- route
- owner
- required input
- expected output
- exclusions
- proof requirements
- link requirements
- acceptance gate

Control rules:
- Do not hand off an unapproved item.
- Do not let the downstream workflow change source context silently.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.

Run Setup QA for [TARGET].

Run Setup QA for this project.

Use the source context before making any decision.
Current source-context state: [SOURCE_CONTEXT_STATUS]
Current asset type: [ASSET_TYPE]
Current target, file, URL, queue, or project note: [TARGET]
Requested downstream route: [DESIRED_ROUTE]

Control purpose:
Check the complete setup record for missing fields, contradictions, unapproved decisions, and route gaps.

Complete these tasks in order:
1. Check all thirteen setup-gate fields.
2. Check module completion, evidence, conflicts, and approval state.
3. Return pass, revise, hold, or fail.
4. List the exact repair modules.

Return the result with these fields:
- setup field
- status
- evidence
- conflict
- approval state
- blocking gap
- repair module
- setup decision
- next route

Control rules:
- Do not pass when a core field is missing.
- Do not start downstream work inside QA.
- Separate approved, blocked, and review-needed items.
- Give a reason for every hold, rejection, or route.
- Do not start the downstream workflow inside this control prompt.
- Keep approval gates sequential.