Raw source material · Information Gain
They are screenshots, workflows, notes, examples, observations, reviews, decisions, questions, and evidence drawn from direct contact with the subject. MIRENA checks those inputs, matches them to the page job, and turns the accepted material into briefing and repair instructions.
Definition and search boundary
The strongest input has a clear source, a current purpose, enough support, and a page role that helps the reader.
Google’s people focused guidance asks whether content demonstrates first hand expertise and depth of knowledge. Its guidance on how content was created also points to evidence of work, including testing details and photographs.
MIRENA separates raw inputs from the published signal, then assigns the input to an answer, example, comparison, process, decision, proof, or route.
Google describes many factors and signals. First hand inputs support helpfulness, trust, and useful difference, but they are not presented as a single ranking switch.
MIRENA internal workflow
The workflow prevents stale evidence, private data, unsupported claims, irrelevant anecdotes, and unplanned screenshots from entering the final content.
MIRENA fixes the site, audience, offer, target query, page role, allowed topic lanes, protected pages, and the decision the content must support.
MIRENA checks source type, freshness, ownership, privacy, permission, completeness, confidence, and whether the input is safe to use.
MIRENA records repeated claims, examples, headings, questions, formats, and internal page overlap before direct inputs are selected.
MIRENA labels screenshots, notes, workflows, reviews, decisions, observations, support questions, examples, and available proof.
MIRENA assigns each accepted input to the intro, comparison, process, example, evidence, question, decision, or internal route it can improve.
MIRENA marks accepted, held, rejected, blocked, and review needed inputs, then routes them into the brief, rewrite, map, link plan, or later evidence task.
Eight input types
Setup details, operating steps, limits, tradeoffs, and observations recorded during direct use.
Images from a real workflow, product flow, page review, or process, with permission and enough context to explain what matters.
Notes about buried answers, weak sections, missing proof, unclear intent, poor order, and better formatting choices.
Before and after blocks with the reason for the change and the lesson the reader can reuse.
Thresholds, conditions, route choices, rejection rules, and patterns used during real delivery.
Checklists, operating notes, templates, governance rules, and approved process material that can support the page.
Repeated questions, objections, friction, implementation problems, and handoff gaps from users or teams.
Direct counts, tests, review findings, behavioral notes, and small analyses with a clear method and limitation.
Six readiness gates
MIRENA records where the input came from, who owns it, and which project or workflow produced it.
The input must still match the current product, process, audience, query, and site rules.
Private names, customer records, screenshots, form data, session notes, and internal material need permission, masking, or removal.
The input must support the claim or lesson it is expected to carry. Missing support stays marked as missing.
The input must improve an answer, example, comparison, decision, process, entity relationship, or next route.
The input needs a section target, format, owner, review note, and next workflow before it moves into drafting.
Input to content routing
Content role: Annotated example or evidence block
MIRENA instruction: Show the task, point to the relevant detail, explain the lesson, and give the next action.
Content role: Process or decision block
MIRENA instruction: Name the sequence, approval gate, failure point, owner, and handoff condition.
Content role: Intro or rewrite instruction
MIRENA instruction: Use the finding to sharpen the answer, remove vague setup, or repair a failed block.
Content role: Example or comparison section
MIRENA instruction: Show what changed, why it changed, and what the reader should learn.
Content role: Selection or route block
MIRENA instruction: Give the condition, threshold, choice, and next step in a compact form.
Content role: Question, objection, or internal link route
MIRENA instruction: Answer the real friction and route the reader to the next proof or action.
Weak use and MIRENA placement
A product screenshot appears without a task, annotation, or lesson.
The brief names the workflow step, the detail to notice, the point the image supports, and the next action.
A generic process repeats the usual steps.
The process names the approval gate, owner, common failure, blocked state, and handoff condition from direct work.
The revised block is shown without explaining the decision.
The comparison identifies the buried answer, structural change, evidence need, and reader benefit.
A filler question repeats the body copy.
The question reflects real implementation friction and routes the reader to the missing proof, process, or support path.
Eight improvement areas
A direct observation or review note can make the first answer more precise and grounded.
Direct use can reveal fit, limits, tradeoffs, and distinctions that feature lists miss.
First hand inputs can surface attributes and relationships that change interpretation or choice.
Workflow notes can replace vague steps with gates, owners, failure points, and handoffs.
A grounded example can show the context, decision, change, and reusable lesson.
Real support questions can expose missing answers, objections, and next routes.
A rule or threshold can help the reader choose the correct route or action.
The input can reveal the next proof source, support page, comparison, or workflow the reader needs.
Page or section decision
The input strengthens the existing answer and does not create a separate user task.
The input needs a comparison, process, example, evidence, question, or decision component but not a new URL.
Another approved URL already owns the topic, proof source, comparison, or support task.
The input reveals a distinct query, user job, page role, and enough depth to justify a separate page decision.
Common mistakes
Confidence is not evidence. The raw input must show what was reviewed, observed, used, or decided.
An image needs a task, annotation, lesson, and reason to exist.
Direct contact with the topic is not enough when the detail pulls the content away from the approved page job.
Some inputs belong in comparisons, process sections, examples, questions, decisions, or internal routes.
MIRENA does not manufacture observations, outcomes, screenshots, quotes, customer evidence, or data.
Unplanned inputs often disappear during drafting or arrive too late to influence the structure.
MIRENA outputs
Source label, owner, freshness, privacy, confidence, usefulness, section target, and readiness state.
Review the routeAvailable evidence, missing evidence, blockers, permission notes, safe use, and approved next route.
Review the routeThe accepted input becomes a visible signal type, placement, reader value, proof need, and writer instruction.
Review the routeThe input, example, screenshot, proof, format, section role, and internal link target move into the approved brief.
Review the routeMIRENA names the generic block, missing source, stronger input, placement, and repair action.
Review the routeEvery accepted, held, rejected, blocked, or review needed input receives an owner and workflow route.
Review the routeQuestions
They are raw source materials drawn from direct contact with the subject, including screenshots, workflow notes, reviews, examples, observations, decisions, support questions, and evidence.
No. A first hand input is the raw material. An experience led signal is the useful trace that appears inside the final content after the input is validated and placed.
No. One annotated screenshot, one workflow note, one decision rule, or one grounded example can add strong value when it supports the page job.
Yes. MIRENA can use them to sharpen an intro, improve a comparison, add missing entity support, repair a process block, strengthen an example, or create a clearer next route.
No. Inputs can support answers, comparisons, processes, examples, questions, decisions, internal links, or page ownership.
No. MIRENA can inventory, assess, place, and route supplied inputs. It does not invent direct use, observations, outcomes, screenshots, quotes, customer records, or data.
Only when it reveals a distinct search need, user job, page role, and enough depth for separate ownership. Otherwise it should strengthen an existing section, block, or route.
Next route
Use the Information Gain prompts for First Hand Input Inventory, Experience Signal Plan, Evidence Block Builder, brief insertions, rewrite planning, and final handoff.
Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.