01Define the reader task and evidence boundary
The local-test prompt set begins by separating the exact phrase “MiniMax H3 local rendering” from any claim about a product, model, plugin, agent, integration, control, access state, or output. This prompts route produces a dedicated local-test prompt set; it has its own input list, reviewer question, decision field, and handoff owner. The review lens is environment, hardware, dependencies, model files, source rights, inputs, resource use, failures, outputs, and review. Freeze one authorized input and environment manifest, record model identity and resource readings, retain failures, compare matched outputs, and avoid extrapolating from one machine. The minimax h3 local rendering test prompts artifact is deliberately different from adjacent companion pages, so retain its plan intent and its specific deliverable rather than widening it into a general product narrative. Name the reader's question, the artifact that answers it, the owner of that artifact, and acceptance conditions a second reviewer can inspect. Preserve source files and versions when authorized, redact unnecessary personal, credential, or billing information, and mark unavailable fields as unavailable. Do not borrow controls from another surface, infer regional access from a public post, or turn a proposed workflow into a guaranteed capability. Compare one declared variable at a time, retain rejected attempts with reasons when policy permits, and distinguish editorial usefulness from technical performance. Current product documentation and the visible authorized workspace remain the places to check labels, controls, entitlement, formats, limits, and behavior. This page supports a local planning or evaluation decision; it makes no claim about customer adoption, commercial performance, repeatability, quality, or future availability. Keep the record revisable when the product surface, source rights, model label, plugin version, delivery destination, or review rubric changes.
02Run the route-specific brief or review
For the task “prepare environment, input, resource, failure, quality, and provenance questions”, keep the source brief, authorization, visible account context, input and output identifiers, settings, timestamps, reviewer, and disposition together. This prompts route produces a dedicated local-test prompt set; it has its own input list, reviewer question, decision field, and handoff owner. The review lens is environment, hardware, dependencies, model files, source rights, inputs, resource use, failures, outputs, and review. Freeze one authorized input and environment manifest, record model identity and resource readings, retain failures, compare matched outputs, and avoid extrapolating from one machine. The minimax h3 local rendering test prompts artifact is deliberately different from adjacent companion pages, so retain its plan intent and its specific deliverable rather than widening it into a general product narrative. Name the reader's question, the artifact that answers it, the owner of that artifact, and acceptance conditions a second reviewer can inspect. Preserve source files and versions when authorized, redact unnecessary personal, credential, or billing information, and mark unavailable fields as unavailable. Do not borrow controls from another surface, infer regional access from a public post, or turn a proposed workflow into a guaranteed capability. Compare one declared variable at a time, retain rejected attempts with reasons when policy permits, and distinguish editorial usefulness from technical performance. Current product documentation and the visible authorized workspace remain the places to check labels, controls, entitlement, formats, limits, and behavior. This page supports a local planning or evaluation decision; it makes no claim about customer adoption, commercial performance, repeatability, quality, or future availability. Keep the record revisable when the product surface, source rights, model label, plugin version, delivery destination, or review rubric changes.
03Close with a narrow disposition
A useful local-test prompt set closes at the scale of the evidence: it records what was observed, what remains unknown, which decision was made, and what event requires a retest. This prompts route produces a dedicated local-test prompt set; it has its own input list, reviewer question, decision field, and handoff owner. The review lens is environment, hardware, dependencies, model files, source rights, inputs, resource use, failures, outputs, and review. Freeze one authorized input and environment manifest, record model identity and resource readings, retain failures, compare matched outputs, and avoid extrapolating from one machine. The minimax h3 local rendering test prompts artifact is deliberately different from adjacent companion pages, so retain its plan intent and its specific deliverable rather than widening it into a general product narrative. Name the reader's question, the artifact that answers it, the owner of that artifact, and acceptance conditions a second reviewer can inspect. Preserve source files and versions when authorized, redact unnecessary personal, credential, or billing information, and mark unavailable fields as unavailable. Do not borrow controls from another surface, infer regional access from a public post, or turn a proposed workflow into a guaranteed capability. Compare one declared variable at a time, retain rejected attempts with reasons when policy permits, and distinguish editorial usefulness from technical performance. Current product documentation and the visible authorized workspace remain the places to check labels, controls, entitlement, formats, limits, and behavior. This page supports a local planning or evaluation decision; it makes no claim about customer adoption, commercial performance, repeatability, quality, or future availability. Keep the record revisable when the product surface, source rights, model label, plugin version, delivery destination, or review rubric changes.
