Mascot Revision Director
Do not patch isolated pixels or append features onto the old design. Reposition
the affected A/B/C character as one visual system and regenerate only that
candidate.
Input contract
Require project context, current art-direction record, user feedback, actual
image QA findings when available, and explicit keep-locks. Vague feedback such
as “更聪明一点” or “不像我” is valid input.
Procedure
- Interpret the feedback in relation to project role and audience. A bare
A/B/C selection is routing, not final approval; only modification feedback
enters this node.
- Re-evaluate silhouette, proportion, anatomy, non-human support topology, scene capability, signature
feature, memory hook, face/personality, palette, material and rendering together.
- Preserve only explicit keep-locks and still-valid identity features.
- Resolve dependencies: changing a tail, for example, may require rebalancing
silhouette, stance, rhythm and material treatment.
Every regenerated direction must retain or improve a visible standing and
manipulation strategy, even when the user feedback does not mention limbs.
When revising a schema 3.0 or 3.1 package, upgrade its revised package
records to schema 3.2 and add validated scene, presentation, surface and
tail plans before rendering.
- Use
../mascot-design-director/scripts/design_director.py::build_holistic_revision_prompt; preserve or intentionally redesign the subject class, artistry plan and recognition plan with the whole character.
to produce a complete new candidate specification. Do not create an anchor,
three-view or derivative asset while revising.
Output contract
Return the new integrated rationale, complete revised direction, anatomy plan,
prompt, preserved locks and superseded decisions. Route only the affected A/B/C
label back to the candidate renderer for one complete replacement image. Final
delivery remains a separate post-QA explicit-confirmation step.
1---2name: mascot-revision-director3description: Reframe mascot feedback as a whole-design constraint and produce one coherent revised direction for the affected candidate, including vague non-professional feedback.4---56# Mascot Revision Director78Do not patch isolated pixels or append features onto the old design. Reposition9the affected A/B/C character as one visual system and regenerate only that10candidate.1112## Input contract1314Require project context, current art-direction record, user feedback, actual15image QA findings when available, and explicit keep-locks. Vague feedback such16as “更聪明一点” or “不像我” is valid input.1718## Procedure19201. Interpret the feedback in relation to project role and audience. A bare21 A/B/C selection is routing, not final approval; only modification feedback22 enters this node.232. Re-evaluate silhouette, proportion, anatomy, non-human support topology, scene capability, signature24 feature, memory hook, face/personality, palette, material and rendering together.253. Preserve only explicit keep-locks and still-valid identity features.264. Resolve dependencies: changing a tail, for example, may require rebalancing27 silhouette, stance, rhythm and material treatment.28 Every regenerated direction must retain or improve a visible standing and29 manipulation strategy, even when the user feedback does not mention limbs.30 When revising a schema 3.0 or 3.1 package, upgrade its revised package31 records to schema 3.2 and add validated scene, presentation, surface and32 tail plans before rendering.335. Use `../mascot-design-director/scripts/design_director.py::build_holistic_revision_prompt`; preserve or intentionally redesign the subject class, artistry plan and recognition plan with the whole character.34 to produce a complete new candidate specification. Do not create an anchor,35 three-view or derivative asset while revising.3637## Output contract3839Return the new integrated rationale, complete revised direction, anatomy plan,40prompt, preserved locks and superseded decisions. Route only the affected A/B/C41label back to the candidate renderer for one complete replacement image. Final42delivery remains a separate post-QA explicit-confirmation step.
yang0