MIRENA · Product documentation
MIRENA uses controlled prompts as workflow instructions, not as the product's only value.
The prompt system defines roles, required inputs, stage order, output contracts, stop rules, validation, handoffs, and versioning so one instruction can be used consistently inside the wider operating system.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
Prompts sit inside the operating system.
A prompt can define a task, but it does not by itself resolve source context, page ownership, evidence, state, validation, or approval. MIRENA uses prompts as controlled instructions within a larger workflow.
The same specialist prompt can be called at several checkpoints with different accepted inputs and output requirements.
Prompt classes.
| Class | Job | Required controls |
|---|---|---|
| Master workflow prompt | Carry a complete use case through several stages | Scope, inputs, stage sequence, outputs, review gates |
| Specialist prompt | Perform one bounded analysis or production task | Current state, owner, evidence, output fields |
| Validation prompt | Check an output against acceptance rules | Expected state, failure classes, evidence |
| Repair prompt | Fix the smallest failing unit | Failed finding, protected content, downstream impact |
| Handoff prompt | Package accepted work for the next owner | Version, decisions, open issues, next route |
Variables prevent hidden assumptions.
A controlled prompt names the site, entity, page or asset, user task, audience, offer, evidence, date, constraints, protected material, desired output, and current approval state.
Missing required variables should produce a hold or clarification record rather than plausible invented content.
Output contracts make the result usable.
A return contract specifies fields, order, state labels, evidence references, rejected options, unresolved items, owner, and next route.
The goal is not to force every output into the same shape. It is to give each workflow the minimum structure the next owner needs.
Stop rules protect the page and the user.
- Stop when identity or page ownership is unresolved
- Stop when a required claim lacks evidence
- Stop when rights or permissions are unclear
- Stop when sensitive data is unsuitable for the route
- Stop when a legal, security, accessibility, or specialist review is mandatory
- Stop when the requested action requires an external system or permission that is unavailable
Versioning and change control.
A material prompt change can alter decisions, output fields, state transitions, or safety behaviour. The change should identify the prior version, reason, affected workflows, compatibility, validation, and rollback.
Prompt count is not a quality metric by itself. The controlled set is valuable only when each instruction has a defined job and remains consistent with the product workflow.
Protected product material.
Normal subscribers may use MIRENA and reviewed outputs under the applicable terms. Protected prompts, system instructions, knowledge files, configuration, and backend logic may not be extracted, cloned, repackaged, resold, or represented as another product.
Check the controlling first-party and official sources.
These routes support the current public statement. External platform and legal sources remain subject to their own updates.
MIRENA product overview
Current first-party prompt count and operating context.
MIRENA workflow
Current first-party stage and handoff sequence.
OpenAI service terms
Official GPT builder and user platform terms.
Move to the page that owns the next question.
Each route has a separate job so company, product, trust, legal, and compliance information does not collapse into one promotional page.
Owned route
Agents and modules
Responsibilities and state control called by prompts.
Open route →
Owned route
MIRENA Workflow
The sequence in which prompt classes operate.
Open route →
Owned route
Inputs
Required variables, evidence, rights, and safety.
Open route →
Owned route
Outputs
Return contracts and handoff fields.
Open route →
Owned route
Acceptable Use
Product rights, automation, misuse, and prohibited extraction.
Open route →
Owned route
Open MIRENA
Use the controlled product interface.
Open route →