Document Krea2 prompt tuning methodology
This commit is contained in:
@@ -45,6 +45,22 @@ Version: `2026-06-30-generated-route-validation-positive-channel-cleanup`
|
|||||||
code path before closing the category. Manual prompt-axis wins are not
|
code path before closing the category. Manual prompt-axis wins are not
|
||||||
enough; the generated route can still drop the key contact hierarchy or add
|
enough; the generated route can still drop the key contact hierarchy or add
|
||||||
limiting positive-channel wording.
|
limiting positive-channel wording.
|
||||||
|
14. Treat the final prompt that Krea receives and the rendered generator images
|
||||||
|
as the source of truth. Tests are guardrails for known failures, not proof
|
||||||
|
that the prompt will render the intended pose. If a test passes while the
|
||||||
|
rendered image or prompt audit shows drift, update the test and the method
|
||||||
|
rather than trusting the test.
|
||||||
|
15. Atlas/catalog prompt wording must use direct visual prompt sentences. Do
|
||||||
|
not send option-list wording such as `or`, `may`, `optionally`, or `either`
|
||||||
|
in pose cues, and do not append meta instructions such as `keep the visible
|
||||||
|
partner...` or generic camera-layout prose to atlas routes. Krea2 is not an
|
||||||
|
instruction-following LLM in this loop; prompt text should describe the
|
||||||
|
image, not explain a policy.
|
||||||
|
16. Do not promote generator edits from a few isolated renders unless the final
|
||||||
|
generated prompt is structurally wrong before rendering. For pose wording
|
||||||
|
changes, collect prompt/image evidence across multiple women, source cases,
|
||||||
|
and seeds when feasible, then patch only the repeated generator-safe
|
||||||
|
hierarchy. Keep early wins as prompt-guide or provisional evidence.
|
||||||
|
|
||||||
## Promotion Gates
|
## Promotion Gates
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user