MiniMax H3 Prompt Review Gate (Plan v2):
The MiniMaxH3PlanV2PromptReview node serves as an interactive approval gate specifically designed for reviewing and approving prompts within the MiniMax H3 Plan v2 framework. Its primary function is to facilitate a manual review process by allowing users to approve or edit prompt texts before they are finalized and used in the workflow. This node is particularly beneficial for ensuring that the prompts align with the intended creative direction and meet quality standards. It operates by keeping the media-bearing plan in memory while transmitting only the prompt text and minimal history metadata to the browser, thus optimizing performance and maintaining data integrity. The node ensures that any manual edits are only accepted if the underlying H3 structure remains consistent with the connected plan, thereby safeguarding against discrepancies. This feature is crucial for maintaining the coherence and reliability of the creative process, as it independently verifies approvals before any edited prompts are utilized.
MiniMax H3 Prompt Review Gate (Plan v2) Input Parameters:
h3_prompt
The h3_prompt parameter is a string input that requires a connection from the same node supplying the plan_context. It is designed to accept multiline text inputs and does not support dynamic prompts. This parameter is crucial as it represents the prompt text that will be reviewed and potentially edited. The input must be connected to outputs like Prompt Merge.h3_prompt, Structured Prompt Enhancer.enhanced_prompt, or Apply Structured Prose.h3_prompt. The parameter ensures that the prompt text is ready for review without any image selection occurring at this stage.
plan_context
The plan_context parameter is of the type PLAN_TYPE and is essential for connecting the compiled plan context from various nodes such as Prompt Merge, Structured Prompt Enhancer, Apply Structured Prose, Inline Prompt Override, or Prompt Review Gate. This parameter carries all the necessary reference image, video, and audio values, ensuring that the prompt review process is comprehensive and contextually aware. It is vital for maintaining the integrity of the plan during the review process.
review_mode
The review_mode parameter allows users to select the mode of operation for the prompt review process. It offers options such as "Pause for approval," which opens the prompt editor for every queued run, and "Pass through," which validates and forwards the prompt without waiting for manual approval. The default setting is "Pause for approval," which is ideal for scenarios where thorough review and manual intervention are required to ensure prompt quality and alignment with creative goals.
MiniMax H3 Prompt Review Gate (Plan v2) Output Parameters:
Approved Prompt
The Approved Prompt output parameter provides the finalized prompt text after it has been reviewed and approved. This output is crucial as it represents the validated and potentially edited prompt that will be used in subsequent stages of the creative workflow. It ensures that the prompt aligns with the intended creative direction and meets the necessary quality standards.
Review Status
The Review Status output parameter indicates the outcome of the review process. It provides information on whether the prompt was approved, edited, or rejected, offering valuable feedback for the user. This parameter is essential for tracking the review process and ensuring that only approved prompts proceed to the next stages of the workflow.
MiniMax H3 Prompt Review Gate (Plan v2) Usage Tips:
- Ensure that the
h3_promptandplan_contextinputs are correctly connected to their respective sources to maintain the integrity of the review process. - Utilize the "Pause for approval" mode for thorough review sessions where manual edits and approvals are necessary to ensure prompt quality.
- Regularly verify that the underlying H3 structure matches the connected plan to prevent discrepancies during the review process.
MiniMax H3 Prompt Review Gate (Plan v2) Common Errors and Solutions:
"plan_context contains stale compiler labels or native routes. Re-run MiniMax H3 Prompt Merge before reviewing it."
- Explanation: This error occurs when the
plan_contextcontains outdated compiler labels or native routes, indicating a mismatch between the current plan and the expected structure. - Solution: Re-run the MiniMax H3 Prompt Merge process to update the
plan_contextand ensure it aligns with the current plan structure before proceeding with the review.
"Prompt text does not match the connected plan."
- Explanation: This error indicates that the prompt text being reviewed does not align with the connected plan, possibly due to manual edits or discrepancies in the plan structure.
- Solution: Verify the prompt text and ensure it is consistent with the connected plan. Make necessary adjustments to the prompt or plan to resolve the mismatch.
