OpenKatana · Set review policy:
OpenKatana_set_review_policy configures a project's review requirements before rendering, helping you catch uninspected source material and unreviewed timeline changes before committing to a final render. Its optional strict mode prevents rendering until every source used in the timeline has been inspected and the current timeline revision has been previewed. You can also require a motion assessment of the current revision against a reference, which adds a measured comparison to your visual review process. This makes the node useful when you want a repeatable quality-control checkpoint rather than relying on memory to confirm that everything has been checked. It changes the review policy and reports outstanding requirements; it does not inspect footage, perform motion analysis, render the timeline, or approve a completed render itself.
OpenKatana · Set review policy Input Parameters:
project_id
A required STRING identifying the OpenKatana project whose review policy you want to change. The underlying operation uses this identifier to locate the project, update its policy, and check its current timeline for outstanding review requirements. Use the identifier of the same project you use for source inspection, timeline previews, motion assessment, and rendering so those operations contribute to the correct project's review status. The provided interface does not specify a default value, permitted identifier format, length limits, or a list of available identifiers.
arguments
A required STRING carrying the tool's arguments as JSON text. For this operation, supply the required Boolean setting strict and, optionally, the Boolean setting require_motion; these are properties inside this string, not separate node inputs. For example, {"strict": true, "require_motion": false} enables strict review without requiring motion assessment, while {"strict": true, "require_motion": true} also requires the current revision to be measured against a reference through revise_motion. When strict mode is active, rendering requires inspection of every source used by the timeline through preview_source or source_contact_sheet, plus a preview of the current revision through preview_timeline. The underlying operation requires strict to be true or false and gives require_motion a default of None when omitted; the supplied context does not show how omission affects a previously stored motion policy, so specify it explicitly when you want a definite configuration. No default string, character limits, or numeric ranges are shown for this node input.
after
An optional STRING accepted by the node's execution interface. The supplied implementation accepts this value but does not explicitly read it or pass it into the review-policy operation, so no direct effect on the policy or returned review status is established by the shown code. If your workflow uses this socket for execution ordering, keep that separate from the review settings supplied in arguments; connecting it does not itself inspect sources or satisfy review requirements. The Python execution method defaults to None when this input is omitted, and the provided interface specifies no string default, length limits, or allowed options.
OpenKatana · Set review policy Output Parameters:
result_json
A STRING containing the serialized response from the review-policy operation. The underlying tool returns strict, indicating the resulting strict-mode setting; require_motion, indicating the resulting motion-review setting; and blocking, reporting outstanding review requirements for the project's current state. These values help you distinguish between successfully changing the policy and actually being ready to render: a successful policy update can still report work that must be completed. Read any reported blockers as instructions for the next review steps rather than as proof that this node failed. An empty blocker list means no outstanding requirements were reported by that check, not that the finished video has been artistically approved. The node wraps the tool response using shared response-handling code whose exact JSON envelope is not included in the supplied context.
OpenKatana · Set review policy Usage Tips:
- For a standard pre-render review checkpoint, use
{"strict": true, "require_motion": false}, inspect every timeline source withpreview_sourceorsource_contact_sheet, and preview the current timeline withpreview_timeline. - For projects where motion matching matters, use
{"strict": true, "require_motion": true}and complete the required measurement against a reference withrevise_motion. Enabling this setting does not perform the measurement automatically. - Finish your timeline edits before completing revision-specific checks. Strict mode requires a preview of the current revision, and motion review, when required, must also cover that revision; checks of an earlier edit do not establish that the latest version was reviewed.
- Read
blockingafter changing the policy and address the reported requirements before starting a render. You can call this node again with your intended settings to obtain an updated report. - Specify both Boolean settings explicitly when you need a predictable configuration. For example,
{"strict": false, "require_motion": false}explicitly requests that both settings be disabled rather than relying on the unspecified handling of an omitted motion setting. - If the reported blockers mention identity references, use
inspect_identityto inspect the generated clips against the relevant references and record an acceptance or rejection. The supplied identity-checking code distinguishes between a missing review and a rejected review; neither is resolved simply by changing the motion setting. - Treat this node as a review gate, not a quality-improvement tool. It helps enforce checks before rendering, but you still need to evaluate the previews and make any necessary creative corrections.
OpenKatana · Set review policy Common Errors and Solutions:
strict must be true or false
- Explanation: The operation received a value for
strictthat is not a Boolean, such as the text"true", a number, ornull. - Solution: Use an unquoted JSON Boolean inside
arguments, such as{"strict": true, "require_motion": false}.
require_motion must be true or false
- Explanation: A supplied, non-null value for
require_motionis not a Boolean. For example,"false"is text rather than the Booleanfalse. - Solution: Set
require_motionto an unquotedtrueorfalse. Although the underlying function accepts an omitted or null value, an explicit Boolean is clearer when you want to control the resulting policy.
unexpected inputs: ...
- Explanation: The node's execution code rejects additional named inputs that are not declared by its interface. This can happen if an integration tries to pass
strictorrequire_motionas separate node fields. - Solution: Use only
project_id,arguments, and the optionalafterinput. Place review-policy settings inside the JSON text supplied toarguments.
Invalid arguments JSON or missing strict setting
- Explanation: The exact parsing or missing-argument message is not shown in the supplied code, but malformed JSON cannot provide the intended settings, and the underlying operation requires
strict. Common mistakes include single quotation marks, trailing commas, and omitting the required setting. - Solution: Start with valid JSON such as
{"strict": true, "require_motion": false}. Use double quotation marks around property names, lowercase Boolean values, and no trailing comma.
Render remains blocked after enabling strict mode
- Explanation: This is a review-policy outcome rather than necessarily an error from this node. Enabling strict mode establishes requirements; it does not complete source inspections, preview the current revision, or perform a required motion assessment.
- Solution: Read
blocking, inspect the timeline sources, preview the current revision, and completerevise_motionif motion review is required. Address any other reported blockers before retrying the render.
inspect generated clip … against identity reference … with inspect_identity
- Explanation: This blocker text comes from the supplied identity-review checker and indicates that a generated clip has no recorded review against a particular identity reference. A general source preview is not the same as a recorded identity acceptance.
- Solution: Use
inspect_identityfor the indicated clip and reference, inspect the comparison, and call it again with an explicit acceptance or rejection to record your decision.
generated clip … was rejected against identity reference …
- Explanation: The identity-review checker found a recorded rejection for the generated clip against the named identity reference. Repeating a preview without recording a new review does not resolve that rejection.
- Solution: Review the mismatch, revise or replace the clip as needed, and inspect the resulting clip against the reference again. Record acceptance only when you are satisfied that it meets the identity requirement.
