Use Source Context, Project Control, and Guardrail prompts when MIRENA needs a clean project base before any topical map, content brief, rewrite, internal link plan, information gain pass, SERP feature plan, or schema note begins.
This is the control layer.
It defines the site, audience, offer, primary entities, allowed topics, blocked topics, page queue rules, proof sources, internal link targets, tone rules, compliance rules, and next workflow route.
Start here before running any other prompt collection.
Use the source context template if the project base is not ready. Use Getting Started with MIRENA if you need the full onboarding route first.
MIRENA can run single prompts or master prompts.
Single prompts are best when one job needs precision.
Master prompts are better when several setup tasks share the same source context and should be handled together.
The rule is simple:
Run related setup checks together.
Keep approval gates sequential.
Do not move into Topical Maps + Planning, Content Briefs, Drafting + Rewriting, Information Gain, internal links, SERP feature planning, or schema notes until the guardrail checks pass.
Start with Source Context Before Any Workflow
Source context tells MIRENA what belongs, what does not belong, what must be protected, and which workflow can run next.
It protects the project from drift.
A keyword file, sitemap, competitor list, SERP export, analytics file, or draft folder can contain many ideas that look related. Some belong in the site. Some belong only as internal links. Some should become sections instead of pages. Some should be rejected.
Use Source Context when you need the strategic rule behind this layer.
Use source context to define:
- site purpose
- audience
- offer
- target region
- primary entities
- support entities
- allowed topic lanes
- blocked topic lanes
- hard exclusions
- page queue rules
- protected pages
- proof sources
- internal link targets
- anchor rules
- tone rules
- compliance rules
- next workflow stage
If source context is weak, stop and build it before running any downstream workflow.
Use MIRENA inputs when you need to decide which files should feed the setup. Use MIRENA workflow when the setup needs a clear route into mapping, briefing, rewriting, linking, information gain, SERP formatting, or schema notes. Use MIRENA outputs when the setup package needs a defined output structure.
What Source Context and Guardrail Prompts Do
These prompts help MIRENA control the project before production starts.
They answer questions like:
- What is this site about?
- Who is it for?
- What does it sell, teach, or support?
- Which topics belong?
- Which topics are blocked?
- Which entities should guide the site?
- Which pages should be protected?
- Which ideas deserve a page?
- Which ideas only deserve a section?
- Which ideas should be rejected?
- Which internal links should be used?
- Which claims need proof?
- Which workflow should run next?
This page is not a topical mapping prompt guide.
It is not a raw discovery prompt guide.
It is not an entity SEO prompt guide.
It is not an information gain prompt guide.
It is the project control layer that runs before those workflows.
When the guardrail layer is complete, the project can move into Topical Maps + Planning, Content Briefs, Drafting + Rewriting, Information Gain, Semantic SEO, Entity SEO, or semantic internal linking.
Use Master Prompts for Related Setup Tasks
MIRENA can handle more than one setup task at a time.
That does not mean every workflow should be merged into one large prompt.
A good master prompt bundles tasks that share the same input and belong in the same control layer. It still uses stop conditions. It still returns blocked items. It still routes downstream work only after the setup passes.
Use master prompts for:
- source context setup
- project intake
- topic lane control
- page queue scoring
- guardrail scoring
- proof source review
- tone and compliance setup
- internal link control
- workflow routing
- local context file creation
- project restart setup
- final setup validation
Do not use master prompts to skip gates.
Keep these stages sequential:
- page queue approval
- net new page approval
- topical map creation
- content brief creation
- draft creation
- rewrite execution
- schema cues
- final QA
- publish pack
The reader-facing rule is:
Run related setup checks together. Keep approval gates sequential.
The Source Context and Guardrail Workflow
Run the setup workflow in this order.
- Build the Source Context Profile.
- Define the site purpose.
- Define the audience.
- Define the offer.
- Define target region.
- Define primary entities.
- Define secondary entities.
- Define allowed topic lanes.
- Define blocked topic lanes.
- Define hard exclusions.
- Define adjacent topic rules.
- Import the page queue.
- Score proposed pages.
- Approve, hold, or reject pages.
- Guard page vs section choices.
- Check topic drift.
- Check buyer fit.
- Check workflow fit.
- Check link fit.
- Check differentiation fit.
- Score project focus.
- Protect existing pages.
- Mark rewrite, merge, and blocked pages.
- Define internal link targets.
- Define anchor rules.
- Build the proof source inventory.
- Add claims guardrails.
- Add tone rules.
- Add compliance notes.
- Build the local context file.
- Update master context.
- Set up session restart notes.
- Route the next workflow.
- Create the handoff contract.
- Run setup QA.
Do not move into a downstream workflow until setup QA passes.
The Master Prompt Pattern
Use this pattern when several setup tasks belong together.
text
Run [master prompt pack] for this project.
Use the source context first.
Complete these tasks in order:
1. [task]
2. [task]
3. [task]
Stop if [blocker] is missing or unclear.
Return the output with these fields:
- field
- field
- field
- approved items
- blocked items
- review-needed items
- next workflow route
Do not move into mapping, briefing, rewriting, internal links, information gain, SERP formatting, or schema unless the guardrail checks pass.The Single Control Prompt Pattern
Use this pattern when one setup or validation job needs precision.
text
Run [single control module] for this project.
Use the source context first.
Review [asset] for [specific control goal].
Return:
- finding
- source context fit
- approved item
- blocked item
- review-needed item
- reason
- next workflow route
Do not move downstream unless the control check passes.What to Give MIRENA Before Running Setup
Start with the best source context you have.
Then add:
- website URL
- sitemap or URL list
- product or service notes
- audience notes
- regions served
- buyer types
- offer details
- internal link targets
- protected pages
- existing content plan
- current page queue
- proof sources
- brand voice notes
- compliance notes
- previous MIRENA outputs
- known blocked topics
- known page types
- next desired workflow
For a new project, start with the Source Context Setup Pack.
For an existing site, start with the Project Intake Pack.
For a page queue, start with the Page Queue Approval Pack.
For a restart, start with the Project Restart Pack.
Master Prompt Packs You Can Run
These master prompts run several related guardrail tasks together while preserving stop conditions and handoff rules.
1. Source Context Setup Pack
Use this when a project has no stable source context yet.
Short command:
text
Run Source Context Setup Pack for this project.Expanded prompt:
text
Run Source Context Setup Pack for this project.
Use the source context first.
Build the project control base in this order:
1. Source Context Profile
2. Site purpose
3. Audience definition
4. Offer definition
5. Region definition
6. Primary entity set
7. Secondary entity set
8. Allowed topic lanes
9. Blocked topic lanes
10. Internal link targets
11. Proof source inventory
12. Next workflow route
Stop if the site purpose, audience, offer, or allowed topic lanes are unclear.
Return:
- source context profile
- site purpose
- audience
- offer
- region
- primary entities
- secondary entities
- allowed topic lanes
- blocked topic lanes
- proof sources
- internal link targets
- blockers
- review-needed items
- next workflow route
Do not create page ideas yet.
Do not move into topical mapping, content briefs, rewriting, internal links, information gain, SERP formatting, or schema notes.Best for:
- new projects
- new sites
- new product lines
- unclear site focus
- first MIRENA session
Output should include:
- source context profile
- audience
- offer
- entities
- allowed lanes
- blocked lanes
- blockers
- next route
Use this to:
Create the project base before any content or SEO workflow starts.
2. Project Intake Pack
Use this when the user has files, exports, URLs, or previous work to load before setup.
Short command:
text
Run Project Intake Pack for this site.Expanded prompt:
text
Run Project Intake Pack for this site.
Use the source context first.
Review all supplied files, URL lists, exports, notes, previous MIRENA outputs, briefs, maps, rewrite plans, internal link notes, proof sources, and analytics summaries.
Complete these tasks in order:
1. Identify each input.
2. Classify each input by use.
3. Mark setup inputs.
4. Mark downstream inputs.
5. Flag missing files.
6. Flag risky inputs.
7. Recommend the setup order.
8. Route each file into the correct workflow.
Return:
- input name or label
- input type
- source quality
- setup value
- downstream value
- risk
- missing field
- keep, hold, ignore, or review
- recommended processing order
- next workflow route
Do not extract raw discovery candidates yet.
Do not create new page ideas yet.
Route the output into Source Context Setup Pack, Topic Lane Control Pack, Page Queue Approval Pack, or Local Context File Pack.Best for:
- existing projects
- large file sets
- site audits
- restarts
- multi-session workflows
Output should include:
- input list
- input type
- quality notes
- setup value
- risk notes
- next route
Use this to:
Load the project safely without letting weak files drive the setup.
3. Topic Lane Control Pack
Use this when topic scope needs strict control.
Short command:
text
Run Topic Lane Control Pack for this site.Expanded prompt:
text
Run Topic Lane Control Pack for this site.
Use the source context first.
Define the topic boundary for the project.
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 vs section rules.
6. Define topic drift warnings.
7. Define escalation rules for review-needed topics.
Return:
- allowed topic lane
- reason it belongs
- blocked topic lane
- reason it is blocked
- hard exclusion
- adjacent topic rule
- page vs section rule
- drift warning
- review-needed topic
- next workflow route
Do not approve pages yet.
Do not build a topical map yet.
Route the output into Page Queue Approval Pack, Guardrail Scoring Pack, or Topical Maps and Planning.Best for:
- broad topics
- semantic SEO projects
- multi-service sites
- AI-generated page queues
- topical map cleanup
Output should include:
- allowed lanes
- blocked lanes
- hard exclusions
- adjacent rules
- drift warnings
- review routes
Use this to:
Protect the site from sideways expansion before mapping starts.
4. Page Queue Approval Pack
Use this when a list of proposed pages needs approval, rejection, or routing.
Short command:
text
Run Page Queue Approval Pack for this page list.Expanded prompt:
text
Run Page Queue Approval Pack for this page list.
Use the source context first.
Review every proposed page before it enters a map, brief, rewrite plan, or publishing queue.
Complete these tasks in order:
1. Import the page queue.
2. Score each page for source context fit.
3. Score buyer fit.
4. Score workflow fit.
5. Score link fit.
6. Score differentiation fit.
7. Decide page, section, merge, hold, or reject.
8. Add rejection notes.
9. Route approved pages into the next workflow.
Return:
- proposed page
- target entity or topic
- source context fit
- buyer fit
- workflow fit
- link fit
- differentiation fit
- page, section, merge, hold, or reject
- reason
- required internal links
- next workflow route
Do not create briefs.
Do not draft pages.
Do not expand the page list beyond the supplied queue unless asked.Best for:
- new page lists
- topical map cleanup
- editorial planning
- client approvals
- site growth planning
Output should include:
- page decision
- fit scores
- rejection notes
- internal link needs
- next route
Use this to:
Stop weak page ideas before they enter the map.
5. Guardrail Scoring Pack
Use this when proposed topics, pages, or workflows need a score before approval.
Short command:
text
Run Guardrail Scoring Pack for this project.Expanded prompt:
text
Run Guardrail Scoring Pack for this project.
Use the source context first.
Score each supplied item using the project guardrails.
Apply these scoring checks:
1. Source context fit
2. Topic fit
3. Entity fit
4. Buyer fit
5. Workflow fit
6. Link fit
7. Differentiation fit
8. Proof support
9. Drift risk
10. Approval readiness
Return:
- 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
Do not approve items with unclear source context fit.
Route the output into Page Queue Approval Pack, Topic Lane Control Pack, or Setup QA.Best for:
- page queues
- cluster ideas
- audit findings
- content refresh lists
- project reviews
Output should include:
- item
- scores
- approval status
- reason
- next route
Use this to:
Make project control repeatable instead of relying on loose judgment.
6. Internal Link Control Pack
Use this when setup needs internal link rules before downstream work.
Short command:
text
Run Internal Link Control Pack for this project.Expanded prompt:
text
Run Internal Link Control Pack for this project.
Use the source context first.
Define internal link rules before topical maps, briefs, rewrites, or page queues move forward.
Complete these tasks in order:
1. Identify priority link targets.
2. Identify protected pages.
3. Define hub links.
4. Define support links.
5. Define commercial routes.
6. Define anchor rules.
7. Define anchors to avoid.
8. Define page role link rules.
9. Flag orphan risks.
10. Route link notes into the next workflow.
Return:
- 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
Do not build a full internal link map yet.
Route the output into Topical Maps and Planning, Content Briefs, Drafting and Rewriting, or semantic internal linking.Best for:
- content briefs
- rewrite plans
- site architecture projects
- product pages
- hub and spoke planning
Output should include:
- link targets
- page roles
- anchor rules
- routes
- orphan risks
- next route
Use this to:
Give downstream workflows clear link direction before content is written.
Use semantic internal linking when the next job is link routing across a cluster.
7. Proof and Evidence Control Pack
Use this when claims need proof rules before briefs or rewrites.
Short command:
text
Run Proof and Evidence Control Pack for this project.Expanded prompt:
text
Run Proof and Evidence Control Pack for this project.
Use the source context first.
Define proof sources and claims guardrails for the project.
Complete these tasks in order:
1. Identify approved proof sources.
2. Identify missing proof sources.
3. Identify claims that need support.
4. Identify claims to avoid.
5. Define first hand input needs.
6. Define example sources.
7. Define evidence rules.
8. Route proof notes into the next workflow.
Return:
- 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
Do not invent proof.
Do not move unsupported claims into a brief or draft.
Route the output into Content Briefs, Drafting and Rewriting, Information Gain, or final QA.Best for:
- product pages
- comparison pages
- information gain work
- high trust content
- final QA
Output should include:
- proof sources
- claim rules
- evidence gaps
- first hand input needs
- next route
Use this to:
Prevent unsupported claims from entering writing workflows.
8. Tone and Compliance Control Pack
Use this when tone, wording, compliance, or brand rules need to be set before production.
Short command:
text
Run Tone and Compliance Control Pack for this project.Expanded prompt:
text
Run Tone and Compliance Control Pack for this project.
Use the source context first.
Define the tone, language, wording, and compliance rules for the project.
Complete these tasks in order:
1. Define brand voice.
2. Define reader tone.
3. Define allowed wording.
4. Define blocked wording.
5. Define claims style.
6. Define compliance notes.
7. Define legal or risk notes.
8. Define rewrite rules.
9. Route tone notes into downstream workflows.
Return:
- brand voice rule
- reader tone rule
- allowed phrase
- blocked phrase
- claim style rule
- compliance note
- risk note
- rewrite rule
- next workflow route
Do not create content yet.
Do not override source context.
Route the output into Content Briefs, Drafting and Rewriting, final QA, or Setup QA.Best for:
- brand-sensitive sites
- legal or compliance review
- content teams
- rewrite projects
- editorial workflows
Output should include:
- voice rules
- blocked wording
- claims rules
- compliance notes
- rewrite rules
- next route
Use this to:
Make style and risk rules clear before writers or editors begin.
9. Workflow Routing Pack
Use this when a project has many possible next steps.
Short command:
text
Run Workflow Routing Pack for this project.Expanded prompt:
text
Run Workflow Routing Pack for this project.
Use the source context first.
Route each approved input, page, topic, or finding into the correct MIRENA workflow.
Use these route options:
- Topical Maps and Planning
- Raw Semantic Discovery
- Content Briefs
- Drafting and Rewriting
- Entity SEO and Salience
- Internal Linking
- Information Gain
- SERP Feature Planning
- Schema Cues after approval
- Final QA
- Hold
- Reject
Return:
- item
- item type
- current state
- source context fit
- route
- reason
- blocker
- required input
- owner or next action
- handoff note
Do not start downstream work.
Only route the work.
Route the output into Handoff Contract or Setup QA.Best for:
- large projects
- multi-team work
- page queues
- content refreshes
- restart sessions
Output should include:
- item
- state
- route
- reason
- blocker
- handoff note
Use this to:
Stop confusion about what should happen next.
10. Local Context File Pack
Use this when the user wants a local copy of project state.
Short command:
text
Run Local Context File Pack for this project.Expanded prompt:
text
Run Local Context File Pack for this project.
Use the source context first.
Create a copy-ready local context file the user can save as plain text.
Include:
1. Project identity
2. Site purpose
3. Audience
4. Offer
5. Region
6. Primary entities
7. Allowed topic lanes
8. Blocked topic lanes
9. Page queue state
10. Protected pages
11. Internal link rules
12. Proof sources
13. Tone rules
14. Compliance notes
15. Approved workflows
16. Previous MIRENA outputs
17. Next workflow route
Return:
- local context file text
- missing fields
- update notes
- restart instructions
- next workflow route
Do not claim persistent storage.
Write it so the user can copy it into a local .txt file.Best for:
- multi-session projects
- restarts
- long content programs
- local project memory
- handoffs
Output should include:
- copy-ready context
- missing fields
- restart notes
- next route
Use this to:
Help the user restart a MIRENA project without losing the setup.
11. Project Restart Pack
Use this when a new session needs to continue from a prior one.
Short command:
text
Run Project Restart Pack from this context file.Expanded prompt:
text
Run Project Restart Pack from this context file.
Use the source context first.
Rebuild the working state from the supplied local context file, previous outputs, page queue, briefs, maps, rewrite notes, and handoff notes.
Complete these tasks in order:
1. Identify project state.
2. Restore source context.
3. Restore approved topic lanes.
4. Restore blocked topic lanes.
5. Restore page queue status.
6. Restore completed outputs.
7. Restore open blockers.
8. Restore next workflow route.
9. Flag missing context.
10. Confirm restart readiness.
Return:
- restored project state
- restored source context
- completed outputs
- open tasks
- blockers
- review-needed items
- next workflow route
- restart readiness
Do not start new work until restart readiness passes.Best for:
- new sessions
- multi-day workflows
- project handoffs
- interrupted work
- long page queues
Output should include:
- restored context
- open tasks
- blockers
- next route
- restart readiness
Use this to:
Resume from the previous workflow without drifting or repeating work.
12. Final Setup Validation Pack
Use this before any downstream workflow begins.
Short command:
text
Run Final Setup Validation Pack for this project.Expanded prompt:
text
Run Final Setup Validation Pack for this project.
Use the source context first.
Validate the project setup before downstream work begins.
Check:
1. Source context exists.
2. Site purpose is clear.
3. Audience is clear.
4. Offer is clear.
5. Primary entities are clear.
6. Allowed lanes are clear.
7. Blocked lanes are clear.
8. Page queue rules are clear.
9. Internal link rules are clear.
10. Proof sources are clear.
11. Tone rules are clear.
12. Compliance notes are clear.
13. Next workflow route is clear.
Return:
- validation item
- pass, revise, hold, or fail
- issue
- required fix
- blocker
- approved downstream workflow
- next workflow route
Do not move downstream if required setup fields are missing.
Return a clear pass, revise, hold, or fail decision.Best for:
- before topical mapping
- before content briefs
- before rewriting
- before internal links
- before schema notes
Output should include:
- validation status
- blockers
- fixes
- approved route
- next workflow
Use this to:
Confirm the project is ready before MIRENA starts content work.
Single Control Prompts You Can Run
These prompts handle one setup, scoring, routing, or validation job at a time.
Use them when the task needs precision or when a master prompt flags a blocker.
1. Source Context Profile
Use this to create the core project profile.
Short command:
text
Run Source Context Profile for this project.Expanded prompt:
text
Run Source Context Profile for this project.
Use the source context first.
Create a clear profile for the site and project.
Return:
- site name
- site purpose
- audience
- offer
- region
- primary entities
- support entities
- allowed topic lanes
- blocked topic lanes
- proof sources
- internal link priorities
- next workflow route
Flag any missing profile fields.
Do not create page ideas yet.Best for:
- first setup
- restarts
- project documentation
- handoffs
- source context repair
Output should include:
- profile
- missing fields
- allowed lanes
- blocked lanes
- next route
Use this to:
Create the base file every other workflow can read.
2. Site Purpose Definition
Use this when the site purpose is unclear.
Short command:
text
Define the site purpose for this project.Expanded prompt:
text
Run Site Purpose Definition for this project.
Use the source context first.
Define what the site exists to do.
Return:
- site purpose
- primary job of the site
- secondary jobs
- topics that support the purpose
- topics that do not support the purpose
- commercial route
- trust route
- next workflow route
Do not define the site as everything it could cover.
Keep the purpose narrow enough to control the map.Best for:
- new sites
- unfocused projects
- broad blogs
- rebrands
- product pivots
Output should include:
- site purpose
- primary job
- secondary jobs
- commercial route
- blocked directions
Use this to:
Set the reason the site exists before page planning begins.
3. Audience Definition
Use this when MIRENA needs to know who the content serves.
Short command:
text
Define the audience for this project.Expanded prompt:
text
Run Audience Definition for this project.
Use the source context first.
Define the audience for this site or workflow.
Return:
- primary audience
- secondary audience
- buyer stage
- skill level
- pain points
- decision needs
- objections
- language level
- topics they need
- topics they do not need
- next workflow route
Do not define the audience too broadly.
Flag audience groups that may need separate pages or separate workflows.Best for:
- content briefs
- product pages
- service pages
- use case pages
- comparison pages
Output should include:
- audience
- stage
- needs
- objections
- topic fit
- next route
Use this to:
Keep the project aligned with the people it needs to help.
4. Offer Definition
Use this when the product, service, or value offer needs clarity.
Short command:
text
Define the offer for this project.Expanded prompt:
text
Run Offer Definition for this project.
Use the source context first.
Define what the site offers and how content should support it.
Return:
- primary offer
- secondary offer
- offer category
- buyer problem
- solution promise
- proof needed
- pages that support the offer
- topics that do not support the offer
- next workflow route
Do not turn the offer into generic positioning.
Tie the offer to page planning, internal links, and conversion routes.Best for:
- commercial pages
- SaaS pages
- service pages
- product-led content
- buyer journeys
Output should include:
- offer
- promise
- buyer problem
- proof
- support pages
- blocked topics
Use this to:
Connect the content system to the business route.
5. Region Definition
Use this when geography, language, or market focus changes the workflow.
Short command:
text
Define the region for this project.Expanded prompt:
text
Run Region Definition for this project.
Use the source context first.
Define the region, market, and language context for this workflow.
Return:
- target country
- target region
- target city if relevant
- language
- spelling rules
- local proof needs
- local page needs
- topics affected by region
- blocked regions
- next workflow route
Do not create local pages unless region intent supports them.Best for:
- local SEO
- multi-location sites
- regional service pages
- international pages
- language-sensitive projects
Output should include:
- target region
- language rules
- local proof needs
- local page notes
- next route
Use this to:
Stop region drift and keep local intent clean.
6. Primary Entity Set
Use this to define the main entities that anchor the project.
Short command:
text
Define the primary entity set for this project.Expanded prompt:
text
Run Primary Entity Set for this project.
Use the source context first.
Identify the primary entities that should anchor the site or workflow.
Return:
- primary entity
- entity type
- reason it belongs
- page or cluster that supports it
- buyer relevance
- internal link target
- proof source
- next workflow route
Do not build an entity map.
Only define the core entity set for project control.Best for:
- site setup
- topical map control
- entity SEO preparation
- content strategy
- guardrail checks
Output should include:
- primary entities
- entity type
- reason
- link target
- next route
Use this to:
Give the project a stable entity base before mapping.
7. Secondary Entity Set
Use this to define support entities without creating a full entity map.
Short command:
text
Define the secondary entity set for this project.Expanded prompt:
text
Run Secondary Entity Set for this project.
Use the source context first.
Identify support entities that can reinforce the primary entities.
Return:
- secondary entity
- related primary entity
- entity type
- reason it belongs
- allowed page type
- internal link target
- risk note
- next workflow route
Do not build the full entity map.
Do not include entities that drift outside source context.Best for:
- support clusters
- topical maps
- content briefs
- internal link planning
- entity SEO preparation
Output should include:
- support entities
- related primary entity
- page type
- risk
- next route
Use this to:
Define support signals without opening the site to every adjacent topic.
8. Allowed Topic Lanes
Use this to define what the site can cover.
Short command:
text
Define allowed topic lanes for this project.Expanded prompt:
text
Run Allowed Topic Lanes for this project.
Use the source context first.
Define the topic lanes that belong on the site.
Return:
- allowed topic lane
- reason it belongs
- related entity
- audience fit
- offer fit
- allowed page types
- internal link target
- next workflow route
Do not include broad topics unless they support the site purpose.
Flag lanes that need review.Best for:
- source context setup
- topical map control
- page queue review
- editorial planning
- project restarts
Output should include:
- allowed lanes
- reasons
- entities
- page types
- link targets
Use this to:
Give MIRENA a clear list of topics it can use.
9. Blocked Topic Lanes
Use this to define topics that should not be pursued.
Short command:
text
Define blocked topic lanes for this project.Expanded prompt:
text
Run Blocked Topic Lanes for this project.
Use the source context first.
Define topic lanes that should not enter the map, brief, rewrite plan, or page queue.
Return:
- blocked topic lane
- reason it is blocked
- risk if included
- related allowed lane if any
- safer alternative
- review rule
- next workflow route
Do not soften blocked lanes into page ideas.
Keep the block clear.Best for:
- broad sites
- drift repair
- page queue approval
- agency workflows
- AI-assisted content planning
Output should include:
- blocked lanes
- reason
- risk
- safer alternative
- next route
Use this to:
Stop MIRENA from expanding into topics that dilute the site.
10. Hard Exclusions
Use this to define topics, claims, or directions that are never allowed.
Short command:
text
Define hard exclusions for this project.Expanded prompt:
text
Run Hard Exclusions for this project.
Use the source context first.
List topics, claims, workflows, page types, or angles that must be excluded.
Return:
- hard exclusion
- exclusion type
- reason
- risk
- example of a blocked request
- allowed alternative if any
- next workflow route
Do not approve excluded items in any downstream workflow.Best for:
- compliance-sensitive sites
- brand safety
- editorial rules
- high trust content
- project governance
Output should include:
- exclusion
- type
- reason
- blocked request example
- alternative
Use this to:
Create non-negotiable guardrails.
11. Adjacent Topic Rules
Use this to control near topics that may or may not belong.
Short command:
text
Define adjacent topic rules for this project.Expanded prompt:
text
Run Adjacent Topic Rules for this project.
Use the source context first.
Review adjacent topics and decide how each should be handled.
Return:
- adjacent topic
- relationship to source context
- allowed as page, section, internal link, example, or reject
- risk of drift
- required condition for approval
- next workflow route
Do not approve adjacent topics only because they are semantically near.Best for:
- topical mapping
- raw discovery review
- broad keyword sets
- competitor research
- page queue cleanup
Output should include:
- adjacent topic
- handling rule
- drift risk
- condition for approval
- next route
Use this to:
Handle near topics without letting them overtake the map.
12. Page Queue Import
Use this when a list of proposed pages needs to be loaded.
Short command:
text
Import this page queue for review.Expanded prompt:
text
Run Page Queue Import for this project.
Use the source context first.
Import the supplied page queue without approving it yet.
Return:
- proposed page
- proposed URL if supplied
- proposed page type
- target topic
- target audience
- source note
- duplicate risk
- review-needed item
- next workflow route
Do not approve, reject, brief, or draft pages yet.
Route the output into Page Queue Scoring.Best for:
- page lists
- content plans
- client queues
- sitemap expansion
- editorial plans
Output should include:
- page list
- page type
- topic
- source note
- risk
- next route
Use this to:
Load the queue cleanly before scoring.
13. Page Queue Scoring
Use this when proposed pages need a fit score.
Short command:
text
Score this page queue.Expanded prompt:
text
Run Page Queue Scoring for this page list.
Use the source context first.
Score each proposed page before approval.
Return:
- proposed page
- source context fit
- entity fit
- buyer fit
- workflow fit
- link fit
- differentiation fit
- overlap risk
- proof support
- total score
- approve, revise, hold, or reject
- reason
- next workflow route
Do not brief or draft pages.
Route the output into Page Approval Gate.Best for:
- new page queues
- topical map prep
- editorial approval
- site expansion
- content audits
Output should include:
- scores
- approval state
- reason
- next route
Use this to:
Rank proposed pages before they enter planning.
14. Page Approval Gate
Use this when scored pages need a final decision.
Short command:
text
Run Page Approval Gate for this page queue.Expanded prompt:
text
Run Page Approval Gate for this page queue.
Use the source context first.
Review scored pages and decide the next action for each.
Return:
- proposed page
- score summary
- approve, revise, hold, merge, section, or reject
- reason
- required fix
- required internal link
- next workflow route
Do not approve pages with unresolved blockers.
Route approved pages into Topical Maps and Planning, Content Briefs, or Drafting and Rewriting.Best for:
- final page approvals
- editorial planning
- agency handoffs
- roadmap decisions
- topical map updates
Output should include:
- decision
- reason
- fix
- link need
- next route
Use this to:
Stop unapproved pages from reaching production.
15. Page Rejection Notes
Use this when rejected pages need clear reasons.
Short command:
text
Write rejection notes for these pages.Expanded prompt:
text
Run Page Rejection Notes for this page queue.
Use the source context first.
Write clear rejection notes for pages that should not move forward.
Return:
- rejected page
- rejection reason
- failed guardrail
- safer alternative
- section option if any
- internal link option if any
- review condition
- next workflow route
Do not rewrite rejected pages as approved ideas.
Keep the rejection clear.Best for:
- client feedback
- editorial planning
- map cleanup
- drift repair
- page queue governance
Output should include:
- rejected page
- reason
- failed guardrail
- safer alternative
- review condition
Use this to:
Document why a page should not move forward.
16. Page vs Section Guard
Use this when a topic may not deserve a dedicated page.
Short command:
text
Run Page vs Section Guard for this topic.Expanded prompt:
text
Run Page vs Section Guard for this topic.
Use the source context first.
Decide if the topic should become a dedicated page, page section, FAQ, example, table, internal link anchor, or rejection.
Return:
- topic
- recommended treatment
- reason
- source context fit
- intent fit
- overlap risk
- internal link target
- next workflow route
Do not create a new page if a section can satisfy the need.
Route approved page ideas into Topical Maps and Planning.Best for:
- keyword lists
- topical maps
- page queues
- content briefs
- SERP reviews
Output should include:
- treatment
- reason
- risk
- link target
- next route
Use this to:
Avoid creating pages for topics that only need sections.
17. Topic Drift Check
Use this when a topic may pull the project away from its purpose.
Short command:
text
Run Topic Drift Check for this topic.Expanded prompt:
text
Run Topic Drift Check for this topic.
Use the source context first.
Check if the topic drifts away from the site purpose, audience, offer, entity set, or approved topic lanes.
Return:
- topic
- drift signal
- source context fit
- allowed lane if any
- blocked lane if any
- risk
- keep, revise, section, hold, or reject
- next workflow route
Do not approve topics with high drift risk.Best for:
- adjacent topics
- AI page ideas
- competitor ideas
- broad keyword exports
- topical map audits
Output should include:
- drift signal
- risk
- decision
- route
Use this to:
Keep the site focused.
18. Buyer Fit Check
Use this when a topic or page needs buyer relevance review.
Short command:
text
Run Buyer Fit Check for this page idea.Expanded prompt:
text
Run Buyer Fit Check for this page idea.
Use the source context first.
Review if the page idea supports the right audience, buyer stage, problem, decision, or conversion route.
Return:
- page idea
- target buyer
- buyer stage
- buyer problem
- decision value
- conversion support
- buyer fit score
- keep, revise, hold, or reject
- next workflow route
Do not approve ideas that attract the wrong audience.Best for:
- commercial pages
- comparison pages
- use cases
- service pages
- SaaS pages
Output should include:
- buyer
- stage
- problem
- score
- decision
- next route
Use this to:
Make sure traffic goals support the business.
19. Workflow Fit Check
Use this when a task needs the right MIRENA route.
Short command:
text
Run Workflow Fit Check for this task.Expanded prompt:
text
Run Workflow Fit Check for this task.
Use the source context first.
Decide which MIRENA workflow should handle the task.
Choose from:
- Source Context and Guardrails
- Raw Semantic Discovery
- Topical Maps and Planning
- Content Briefs
- Drafting and Rewriting
- Entity SEO and Salience
- Internal Linking
- Information Gain
- SERP Feature Planning
- Schema Cues after approval
- Final QA
- Hold
- Reject
Return:
- task
- current stage
- best workflow
- reason
- required input
- blocker
- next workflow route
Do not start the workflow.
Only route the task.Best for:
- unclear user requests
- large projects
- handoffs
- restart sessions
- mixed inputs
Output should include:
- best workflow
- reason
- blocker
- next route
Use this to:
Send each task to the right part of MIRENA.
20. Link Fit Check
Use this when a page idea needs internal link support review.
Short command:
text
Run Link Fit Check for this page idea.Expanded prompt:
text
Run Link Fit Check for this page idea.
Use the source context first.
Review if the page has enough internal link support and a clear role in the site.
Return:
- page idea
- likely parent page
- likely support pages
- target internal links
- anchor direction
- orphan risk
- link fit score
- keep, revise, hold, or reject
- next workflow route
Do not approve pages with no clear link route unless the strategy explains why.Best for:
- page queues
- topical maps
- content briefs
- internal link planning
- site architecture
Output should include:
- parent page
- support pages
- link targets
- orphan risk
- score
- route
Use this to:
Avoid pages that have no place in the site architecture.
21. Differentiation Fit Check
Use this when a page needs a reason to exist.
Short command:
text
Run Differentiation Fit Check for this page idea.Expanded prompt:
text
Run Differentiation Fit Check for this page idea.
Use the source context first.
Review if the page has a clear reason to exist beyond repeated coverage.
Return:
- page idea
- repeated coverage risk
- useful difference
- proof source
- first hand input option
- information gain route
- differentiation fit score
- keep, revise, hold, or reject
- next workflow route
Do not approve pages that only repeat what already exists.Best for:
- competitive topics
- content refreshes
- page queues
- information gain work
- final approvals
Output should include:
- repeated risk
- useful difference
- proof source
- score
- route
Use this to:
Confirm each page has a useful reason to exist.
22. Focus Score
Use this when the project needs an overall focus check.
Short command:
text
Run Focus Score for this project.Expanded prompt:
text
Run Focus Score for this project.
Use the source context first.
Score the project for focus before downstream workflows begin.
Return:
- site purpose clarity score
- audience clarity score
- offer clarity score
- entity clarity score
- allowed lane clarity score
- blocked lane clarity score
- page queue clarity score
- link direction score
- proof readiness score
- total focus score
- pass, revise, hold, or fail
- highest priority fix
- next workflow route
Do not move downstream if focus is weak.Best for:
- setup QA
- restarts
- large sites
- broad projects
- before topical mapping
Output should include:
- scores
- total
- decision
- priority fix
- next route
Use this to:
Measure how ready the project is before production.
23. Protected Pages
Use this when existing pages should not be overwritten, merged, or redirected without review.
Short command:
text
Define protected pages for this project.Expanded prompt:
text
Run Protected Pages for this project.
Use the source context first.
Identify pages that should be protected during mapping, rewriting, merging, or internal link changes.
Return:
- protected page
- reason for protection
- current role
- traffic or conversion note if available
- link role
- allowed changes
- blocked changes
- review rule
- next workflow route
Do not recommend merging, deleting, or redirecting protected pages without review.Best for:
- site restructures
- content refreshes
- rewrite projects
- internal link changes
- migration planning
Output should include:
- protected page
- role
- allowed changes
- blocked changes
- review rule
Use this to:
Prevent important pages from being changed too early.
24. Pages to Rewrite
Use this when existing pages need rewrite routing.
Short command:
text
Identify pages to rewrite.Expanded prompt:
text
Run Pages to Rewrite for this project.
Use the source context first.
Identify pages that should move into a rewrite workflow.
Return:
- page
- rewrite reason
- current weakness
- source context fit
- entity issue if any
- information gain issue if any
- internal link issue if any
- rewrite priority
- next workflow route
Do not rewrite the pages yet.
Route approved pages into Drafting and Rewriting.Best for:
- content audits
- refresh projects
- old posts
- weak pages
- ranking repair
Output should include:
- page
- reason
- weakness
- priority
- route
Use this to:
Send rewrite candidates into the right workflow.
25. Pages to Merge
Use this when several pages may overlap.
Short command:
text
Identify pages to merge.Expanded prompt:
text
Run Pages to Merge for this project.
Use the source context first.
Review page overlap and identify merge candidates.
Return:
- source page
- overlapping page
- overlap reason
- stronger target page
- merge risk
- content to preserve
- link update needed
- review-needed item
- next workflow route
Do not merge pages automatically.
Route merge candidates into review before action.Best for:
- duplicate content
- cannibalization cleanup
- old blog libraries
- site restructures
- topical map audits
Output should include:
- merge pair
- reason
- stronger target
- content to preserve
- link update
- review note
Use this to:
Find overlap without making irreversible decisions.
26. Pages to Block
Use this when pages should not move forward.
Short command:
text
Identify pages to block.Expanded prompt:
text
Run Pages to Block for this project.
Use the source context first.
Identify pages that should not enter the map, brief queue, rewrite queue, or publishing queue.
Return:
- blocked page
- blocked reason
- failed guardrail
- risk if published
- safer alternative
- review condition
- next workflow route
Do not turn blocked pages into drafts.Best for:
- weak page queues
- topic drift
- duplicate ideas
- off-context topics
- low-value pages
Output should include:
- blocked page
- reason
- failed guardrail
- risk
- alternative
Use this to:
Prevent weak or off-context pages from entering production.
27. Internal Link Targets
Use this to define priority internal destinations.
Short command:
text
Define internal link targets for this project.Expanded prompt:
text
Run Internal Link Targets for this project.
Use the source context first.
Define the pages that should receive internal links from future maps, briefs, rewrites, and support pages.
Return:
- target page
- page role
- entity supported
- funnel role
- preferred source pages
- preferred anchors
- anchors to avoid
- priority
- next workflow route
Do not build the full internal link map yet.Best for:
- briefs
- rewrites
- topical maps
- commercial pages
- support clusters
Output should include:
- target page
- role
- entity
- anchors
- priority
- route
Use this to:
Give every downstream workflow clear link targets.
28. Anchor Rules
Use this when anchor text needs control.
Short command:
text
Define anchor rules for this project.Expanded prompt:
text
Run Anchor Rules for this project.
Use the source context first.
Define anchor text rules for internal links.
Return:
- target page
- preferred anchor type
- sample anchor
- anchors to avoid
- context rule
- overuse risk
- page role note
- next workflow route
Do not create random anchor text.
Tie anchors to page purpose and reader path.Best for:
- internal links
- content briefs
- rewrites
- hub and spoke planning
- navigation cleanup
Output should include:
- target page
- preferred anchor
- avoid list
- context rule
- risk
Use this to:
Keep internal links useful and context-driven.
29. Proof Source Inventory
Use this to define which sources can support claims.
Short command:
text
Build the proof source inventory.Expanded prompt:
text
Run Proof Source Inventory for this project.
Use the source context first.
Identify approved sources that can support claims, examples, comparisons, and proof sections.
Return:
- proof source
- source type
- claim it can support
- page or workflow where it belongs
- source quality
- missing proof source
- risk note
- next workflow route
Do not invent proof sources.
Route missing proof into Evidence Control or Information Gain.Best for:
- content briefs
- information gain
- product pages
- comparison pages
- final QA
Output should include:
- proof source
- claim supported
- source quality
- missing source
- route
Use this to:
Keep claims tied to real support.
30. Claims Guard
Use this when the project needs rules for claims.
Short command:
text
Run Claims Guard for this project.Expanded prompt:
text
Run Claims Guard for this project.
Use the source context first.
Define which claims are allowed, which claims need proof, and which claims should be avoided.
Return:
- claim type
- allowed claim
- proof required
- claim to avoid
- safer wording
- risk note
- next workflow route
Do not approve unsupported claims.
Route claims needing evidence into Proof Source Inventory or Information Gain.Best for:
- product pages
- service pages
- comparison pages
- high trust content
- compliance review
Output should include:
- claim type
- proof needed
- claim to avoid
- safer wording
- route
Use this to:
Stop unsupported claims before writing begins.
31. Tone Rules
Use this when voice and wording need control.
Short command:
text
Define tone rules for this project.Expanded prompt:
text
Run Tone Rules for this project.
Use the source context first.
Define how MIRENA should write, edit, and structure language for this project.
Return:
- brand voice
- reader tone
- sentence style
- formatting preference
- allowed wording
- blocked wording
- examples of preferred phrasing
- next workflow route
Do not draft content yet.
Route tone notes into briefs, rewrites, and final QA.Best for:
- brand setup
- rewrite projects
- editorial handoffs
- docs
- product pages
Output should include:
- voice
- tone
- allowed wording
- blocked wording
- route
Use this to:
Keep output consistent across sessions and workflows.
32. Compliance Notes
Use this when risk, legal, medical, finance, or brand safety rules apply.
Short command:
text
Define compliance notes for this project.Expanded prompt:
text
Run Compliance Notes for this project.
Use the source context first.
Define risk rules and compliance notes for the project.
Return:
- compliance area
- rule
- claim restriction
- required disclaimer if any
- approval need
- risk note
- blocked wording
- next workflow route
Do not draft regulated claims without review.
Route compliance notes into briefs, rewrites, and final QA.Best for:
- high trust content
- regulated industries
- legal review
- brand risk
- client approval workflows
Output should include:
- rule
- restriction
- approval need
- blocked wording
- route
Use this to:
Keep risk rules visible before writing starts.
33. Local Context File Builder
Use this when the user wants a copy-ready project memory file.
Short command:
text
Build a local context file for this project.Expanded prompt:
text
Run Local Context File Builder for this project.
Use the source context first.
Create a plain text context file the user can copy into a local .txt file.
Include:
- project name
- site purpose
- audience
- offer
- region
- primary entities
- allowed lanes
- blocked lanes
- hard exclusions
- page queue state
- protected pages
- internal link targets
- proof sources
- tone rules
- compliance notes
- completed workflows
- open tasks
- next workflow route
Do not claim persistent storage.
Return copy-ready text only.Best for:
- session continuity
- project handoff
- long workflows
- local storage
- restart setup
Output should include:
- plain text context
- open tasks
- next route
- restart notes
Use this to:
Let the user save project state locally.
34. Master Context Update
Use this after a major workflow changes the project state.
Short command:
text
Update the master context for this project.Expanded prompt:
text
Run Master Context Update for this project.
Use the source context first.
Update the project context with the latest approved outputs.
Return:
- newly approved item
- changed rule
- new blocked item
- new protected page
- completed workflow
- open task
- next workflow route
- copy-ready update block
Do not remove earlier context unless a newer approved decision replaces it.Best for:
- after page approvals
- after topical maps
- after briefs
- after rewrites
- after QA
Output should include:
- updates
- changed rules
- open tasks
- copy-ready block
Use this to:
Keep the project memory current.
35. Session Restart Setup
Use this when a user returns to a project later.
Short command:
text
Set up this session restart.Expanded prompt:
text
Run Session Restart Setup for this project.
Use the source context first.
Review the supplied local context, previous outputs, and current user request.
Return:
- restored project state
- last completed workflow
- open tasks
- current blockers
- next approved workflow
- missing context
- restart readiness
- next workflow route
Do not start new work until restart readiness passes.Best for:
- new chat sessions
- long projects
- interrupted workflows
- file reuploads
- page queues
Output should include:
- restored state
- blockers
- open tasks
- readiness
- route
Use this to:
Continue from the last approved state.
36. Next Workflow Route
Use this when a task needs to move into the next MIRENA workflow.
Short command:
text
Route this task into the next workflow.Expanded prompt:
text
Run Next Workflow Route for this task.
Use the source context first.
Decide the correct next workflow for the task.
Return:
- task
- current state
- approved next workflow
- reason
- required input
- blocker
- handoff note
- next action
Do not start the next workflow.
Only route it.Best for:
- handoffs
- unclear next steps
- multi-stage projects
- page queues
- final review
Output should include:
- next workflow
- reason
- required input
- blocker
- handoff note
Use this to:
Send work forward without skipping validation.
37. Handoff Contract
Use this when a setup output needs to become a clean downstream handoff.
Short command:
text
Create the handoff contract for this project.Expanded prompt:
text
Run Handoff Contract for this project.
Use the source context first.
Create a handoff package that downstream workflows can use.
Return:
- source context summary
- approved items
- blocked items
- review-needed items
- required inputs
- internal link targets
- proof sources
- tone rules
- compliance notes
- next workflow route
- stop conditions
Do not hand off incomplete setup.Best for:
- team handoffs
- content briefs
- topical maps
- rewrites
- QA transitions
Output should include:
- approved items
- blocked items
- required inputs
- stop conditions
- route
Use this to:
Make sure the next workflow receives the right instructions.
38. Setup QA
Use this before downstream work begins.
Short command:
text
Run Setup QA for this project.Expanded prompt:
text
Run Setup QA for this project.
Use the source context first.
Check the setup for completeness and readiness.
Review:
- source context
- site purpose
- audience
- offer
- entities
- allowed lanes
- blocked lanes
- page queue rules
- internal link targets
- proof sources
- tone rules
- compliance notes
- next workflow route
Return:
- check item
- pass, revise, hold, or fail
- issue
- required fix
- blocker
- approved downstream workflow
- next workflow route
Do not move downstream if required setup is missing.Best for:
- before mapping
- before briefs
- before rewrites
- before information gain
- before schema notes
Output should include:
- pass or fail
- issues
- required fixes
- blockers
- approved route
Use this to:
Confirm the project is ready for the next workflow.
Which Prompt Should You Run First?
Start with Source Context Setup Pack if the project base is missing.
Start with Project Intake Pack if you have files, exports, notes, or previous work.
Start with Topic Lane Control Pack if the site has drift risk.
Start with Page Queue Approval Pack if you already have proposed pages.
Start with Guardrail Scoring Pack if the page queue needs scores.
Start with Local Context File Pack if the project needs to be saved for another session.
Start with Project Restart Pack if you are continuing from a previous session.
Start with Final Setup Validation Pack before moving into a downstream workflow.
Common Setup Starting Points
I Am Starting a New MIRENA Project
Use this prompt first.
text
Run Source Context Setup Pack for this project.
Use the source context first.
Build:
1. Source Context Profile
2. Site purpose
3. Audience definition
4. Offer definition
5. Region definition
6. Primary entity set
7. Secondary entity set
8. Allowed topic lanes
9. Blocked topic lanes
10. Internal link targets
11. Proof source inventory
12. Next workflow route
Stop if the site purpose, audience, offer, or allowed topic lanes are unclear.
Return:
- source context profile
- site purpose
- audience
- offer
- region
- primary entities
- secondary entities
- allowed lanes
- blocked lanes
- proof sources
- internal link targets
- blockers
- review-needed items
- next workflow route
Do not create page ideas yet.Then run:
text
Run Final Setup Validation Pack for this project.
Use the source context first.
Validate that the project has a clear source context, site purpose, audience, offer, entities, allowed lanes, blocked lanes, page queue rules, internal link rules, proof sources, tone rules, compliance notes, and next workflow route.
Return:
- validation item
- pass, revise, hold, or fail
- issue
- required fix
- blocker
- approved downstream workflow
- next workflow routeI Have a Page Queue
Use this prompt first.
text
Run Page Queue Approval Pack for this page list.
Use the source context first.
Review every proposed page before it enters a map, brief, rewrite plan, or publishing queue.
Return:
- proposed page
- target entity or topic
- source context fit
- buyer fit
- workflow fit
- link fit
- differentiation fit
- page, section, merge, hold, or reject
- reason
- required internal links
- next workflow route
Do not create briefs.
Do not draft pages.Then run:
text
Run Page Rejection Notes for rejected pages.
Use the source context first.
Return:
- rejected page
- rejection reason
- failed guardrail
- safer alternative
- section option if any
- internal link option if any
- review condition
- next workflow routeRoute approved pages into Topical Maps + Planning or Content Briefs.
I Have a Broad Topic and Need Guardrails
Use this prompt first.
text
Run Topic Lane Control Pack for this site.
Use the source context first.
Define:
1. Allowed topic lanes
2. Blocked topic lanes
3. Hard exclusions
4. Adjacent topic rules
5. Page vs section rules
6. Topic drift warnings
7. Review-needed topics
Return:
- allowed topic lane
- reason it belongs
- blocked topic lane
- reason it is blocked
- hard exclusion
- adjacent topic rule
- page vs section rule
- drift warning
- review-needed topic
- next workflow route
Do not approve pages yet.Then run:
text
Run Page vs Section Guard for this topic list.
Use the source context first.
Decide if each topic should become a dedicated page, page section, FAQ, example, table, internal link anchor, or rejection.
Return:
- topic
- recommended treatment
- reason
- source context fit
- intent fit
- overlap risk
- internal link target
- next workflow routeI Need to Save the Project for Later
Use this prompt.
text
Run Local Context File Pack for this project.
Use the source context first.
Create a copy-ready local context file the user can save as plain text.
Include:
- project identity
- site purpose
- audience
- offer
- region
- primary entities
- allowed topic lanes
- blocked topic lanes
- page queue state
- protected pages
- internal link rules
- proof sources
- tone rules
- compliance notes
- approved workflows
- previous MIRENA outputs
- next workflow route
Do not claim persistent storage.
Write it so the user can copy it into a local .txt file.I Am Restarting a Project
Use this prompt.
text
Run Project Restart Pack from this context file.
Use the source context first.
Rebuild the working state from the supplied local context file, previous outputs, page queue, briefs, maps, rewrite notes, and handoff notes.
Return:
- restored project state
- restored source context
- completed outputs
- open tasks
- blockers
- review-needed items
- next workflow route
- restart readiness
Do not start new work until restart readiness passes.I Need to Route the Next Step
Use this prompt.
text
Run Workflow Routing Pack for this project.
Use the source context first.
Route each approved input, page, topic, or finding into the correct MIRENA workflow.
Use these route options:
- Topical Maps and Planning
- Raw Semantic Discovery
- Content Briefs
- Drafting and Rewriting
- Entity SEO and Salience
- Internal Linking
- Information Gain
- SERP Feature Planning
- Schema Cues after approval
- Final QA
- Hold
- Reject
Return:
- item
- item type
- current state
- source context fit
- route
- reason
- blocker
- required input
- owner or next action
- handoff noteReview the Setup Before Moving Forward
Before the project moves downstream, check that the setup includes:
- source context profile
- site purpose
- audience
- offer
- region
- primary entities
- secondary entities
- allowed topic lanes
- blocked topic lanes
- hard exclusions
- adjacent topic rules
- page queue rules
- page approval decisions
- rejected page notes
- protected pages
- pages to rewrite
- pages to merge
- pages to block
- internal link targets
- anchor rules
- proof sources
- claims guardrails
- tone rules
- compliance notes
- local context file
- master context update
- next workflow route
- handoff contract
- setup QA result
Do not move into mapping, briefing, rewriting, internal links, information gain, SERP formatting, or schema if the setup has unresolved blockers.
How This Workflow Connects to Other MIRENA Workflows
Source Context, Project Control, and Guardrails sit before every other MIRENA workflow.
A clean page queue can feed Topical Maps + Planning when the next job is site structure.
A validated page target can feed Content Briefs when the next job is writer instruction.
A rewrite queue can feed Drafting + Rewriting when the next job is page repair.
A differentiation issue can feed Information Gain when the next job is useful difference.
An entity issue can feed Entity SEO when the next job is entity structure.
A meaning or topic fit issue can feed Semantic SEO when the next job is context and relevance.
A link route issue can feed semantic internal linking when the next job is page relationship design.
Schema cues should only follow after the visible page content is approved.
Source Context and Guardrail Mistakes to Avoid
Mistake 1: Starting with Keywords Instead of Context
A keyword file is not source context.
Load the site, audience, offer, allowed lanes, blocked lanes, and next workflow route first.
Mistake 2: Approving Too Many Adjacent Topics
Adjacent topics can look useful.
Some only deserve examples, sections, internal links, or rejection. Use Adjacent Topic Rules and Page vs Section Guard before adding pages.
Mistake 3: Treating Master Prompts as Permission to Skip Gates
Master prompts can run related setup checks together.
They should not skip approval gates.
Mistake 4: Creating Pages Before Scoring the Queue
A proposed page should pass source context fit, buyer fit, workflow fit, link fit, and differentiation fit before it moves downstream.
Mistake 5: Forgetting Protected Pages
Protected pages need rules before mapping, merging, rewriting, or internal link changes begin.
Mistake 6: Letting Unsupported Claims Enter Briefs
Claims need proof rules before briefs or drafts are created.
Use Proof Source Inventory and Claims Guard before writing.
Mistake 7: Losing Project State Between Sessions
Long MIRENA projects need a local context file.
Use Local Context File Builder and Project Restart Pack to preserve setup and next steps.
FAQs About Source Context and Guardrail Prompts
What is source context in MIRENA?
Source context is the project control base.
It tells MIRENA what the site is, who it serves, what it offers, which topics belong, which topics are blocked, which pages matter to the site, and which workflow can run next.
Should I use a single prompt or a master prompt?
Use a single prompt when one control task needs precision.
Use a master prompt when several related setup tasks share the same input and can safely run together.
Keep approval gates sequential.
Can MIRENA run several setup tasks at once?
Yes.
MIRENA can run related setup checks together, such as source context profile, allowed topic lanes, blocked topic lanes, proof sources, internal link targets, and next workflow routing.
Do not bundle downstream work unless the setup passes.
What should run before topical mapping?
Run Source Context Setup Pack, Topic Lane Control Pack, Page Queue Approval Pack, and Final Setup Validation Pack.
Then route approved items into Topical Maps + Planning.
What should run before a content brief?
Run Source Context Setup Pack, Page Approval Gate, Internal Link Control Pack, Proof and Evidence Control Pack, and Setup QA.
Then route the approved page into Content Briefs.
What should run before rewriting?
Run Source Context Profile, Pages to Rewrite, Protected Pages, Internal Link Targets, Claims Guard, and Tone Rules.
Then route the page into Drafting + Rewriting.
What should run before information gain?
Run Source Context Differentiation Check, Differentiation Fit Check, Proof Source Inventory, and Claims Guard.
Then route the page into Information Gain.
What should run before internal linking?
Run Internal Link Control Pack, Internal Link Targets, Anchor Rules, Link Fit Check, and Protected Pages.
Then route the output into semantic internal linking.
What should run before schema notes?
Run Setup QA, Claims Guard, Proof Source Inventory, Final QA, and the approved draft check.
Schema cues should only follow approved visible content.
Can I save MIRENA project context locally?
Yes.
Run Local Context File Builder and copy the output into a local .txt file. In a later session, paste it back and run Project Restart Pack.