OD ART ENGINE APPLICATION GUIDE
Published 2026-10-31

These are the latest selected local copies in this release. The date describes publication, not a claim that newer versions cannot exist elsewhere. Text structure and application were reviewed. Native OD efficacy was not tested.

DEDICATED AUTHORING AND RAW OUTPUT CHECK
Use a separate authoring LLM or a dedicated OD authoring chat. Back up that chat's existing Custom Instructions, then replace conflicting inherited roleplay instructions with one complete generator. Keep the authoring task separate from story memories. A field placement or mode label does not guarantee instruction priority or output compliance.
Repeat the chosen scope and delivery format in each compilation request, including follow-ups. Use this request header outside the character payload:
Mode: CANONICAL CHARACTER. Return the complete artifact in this reply, even if unchanged. Do not refer me to an earlier result.
Format: exactly three nonempty comma-separated blocks separated by exactly two standalone uppercase BREAK lines, with a blank line before and after each separator; no headings, quotes, dialogue, thoughts or explanation.
Target: Mira, fictional adult woman aged 30, warm brown skin, brown eyes, oval face, lean build, black shoulder-length braids.
For a temporary profile, change Mode to CURRENT-FORM and repeat the complete identity plus the accepted change and coverage. Do not paste the request header, generator instructions or a status reply into CPD.
Inspect native Copy text before using a result. The raw result must contain exactly two standalone BREAK lines and three nonempty blocks. Reject missing artifacts and added prose rather than treating a claim of completion as completion. Display styling and raw copied text can differ.
LIMITED NATIVE OBSERVATIONS, OCTOBER 31, 2026
In one Eclipse Genius session displaying FREE, Fluidity v1.1 in Roleplay mode added prose and omitted BREAK lines. Changing only to Texting yielded correctly separated raw canonical and current-form outputs. Texting was marked SUNSETTING; its future availability and behavior are not guaranteed. Realistic anime v1.1 also returned references to earlier results on repeated requests. An added output guard helped one canonical retry but a later current-form request still returned a status message. These limited text observations motivated the complete-artifact rule and explicit request header; they do not establish a universal fix or native image fidelity. Recheck the actual copied artifact in the current model, mode and setup.
The request header above shows the Fluidity/realistic anime three-block convention. For Body Horror v2.2, replace its Format line with: one complete concise unweighted payload, without BREAK separators.

1. CHOOSE A ROLE
An art engine gives an LLM rules for writing still-image prompts. It is text, not executable software, a native plug-in, or a model selector. Use a dedicated authoring chat to supply the engine, current character facts, and scene. Send only its resolved visual description to the image generator. Extra Details is a proposed chat-facing placement where available; automatic delivery to every image route is not established.

A CPD contains one character's permanent visible appearance. A generator writes CPD text in another LLM; the generator instructions themselves do not belong in CPD. A fragment supplies only rendering, palette, or an example scene. A setup guide explains manual placement.

2. SELECT A MATCHING PACK
Reusable engines: realistic anime with proportion preservation, shared painted fantasy Revision 2, the group painting variant, or the Dreamy-targeted photographic profile. Choose one primary treatment.
Character examples: Rin photographic, ivory ghost, gold ghost, and cartoon 3D fantasy V3. These carry fixed identity. Use a matching CPD and engine as one deliberate example, or replace all identity references before adapting. Do not merge the ivory and gold ghost variants accidentally.
CPD generators: Fluidity, realistic anime treatment, or non-graphic body horror anime treatment. Fluidity and realistic anime use curated v1.2 three-block authoring contracts. The newer Body Horror v2.2 uses a concise unweighted payload by default, with legacy layout only when requested. The latter two labels are treatments, not model selectors.

3. MANUALLY CHECK THE DESTINATION
Choose an actually available model and generation route in your account. The target named in a source file is not proof of current availability. Confirm which character or source image is selected. Transfer only the text needed by that route. Keep pose, clothes, place, time, and lighting in the changing scene unless intentionally permanent. Avoid stacking multiple conflicting rendering instructions.

4. AVOID IDENTITY BLENDING
Keep user Persona facts separate from the main character CPD. Keep NPC appearance under the NPC's name or its own card where supported. In a multi-person visual prompt, write one clause per named person, then explicit positions. Repeating a shared style is not a substitute for appearance ownership. These are authoring safeguards, not tested regional-conditioning controls.

5. USE EDIT WITH ITS ACTUAL SOURCE
Choose the source image first. State one change and the visible traits that should remain. Compare face, proportions, silhouette, garment fit, crop, and light with the source. Return to a clean source if accumulated edits drift. Do not claim exact recovery of hidden anatomy or guaranteed preservation.

6. CHECK OBSERVED RESULTS
Record actual model, route, input, selected character or image, and settings. Establish a baseline, change one variable, then compare repeated outputs for the same criteria. Mark untested combinations untested. Numerical weights, BREAK, underscore tokens, artist names, and preservation wording in legacy templates do not establish a universal native parser or measured efficacy.

DOWNLOAD NOTES
Each reader page lists its role, destination, revision, limitations, byte count, and SHA-256. Published copies use OD display branding and updated companion links. Original source art packages are retained. Published authoring instructions and the maintained compiler include the curated revisions recorded in export provenance. Superseded aliases, unrelated roleplay engines, and third-party reference images are excluded from this art release.

Library tutorials: https://duhployed.com/learn/#tutorials
Art reference: https://duhployed.com/learn/references/art.html
Source review: https://duhployed.com/learn/source-review.html
Freebies: https://duhployed.com/learn/freebies/

ACCEPTED FORM, COVERAGE AND SOURCE RECORD
Choose canonical permanent identity or an explicitly requested temporary current-form profile before generating text. For a changing character, supply the accepted transition, form/stage, complete relevant visible appearance and unchanged anchors. A partial mixture is intentional only when defined. Do not blend every form, infer new anatomy or copy obsolete skin/hair back over a changed feature.
Only a canonical CHARACTER result is intended to replace permanent CPD. A CURRENT-FORM profile stays with the actual scene/image handoff unless a permanent revision is explicitly intended. A saved character or preset may still inject an older appearance: inspect and reconcile those inputs rather than assuming an ED block, snapshot or tracker overrides them.
The skin-tone automatic-clothing-coverage workaround was withdrawn by its supplied author after confounded initial tests and contrary clean-character results. Keep stable identity separate from what the current garments and crop reveal; field placement does not guarantee occlusion. An affection score, stage label or SCE heading does not establish permission, undressing or a completed action.
For editing, select actual accepted source pixels. Record source -> crop -> attempted edit -> accepted result, including failed passes and each displayed charge, outside the generation prompt. State the change and its explicit preservation exception; inspect each subject, pose and background geometry separately. Multiple-image identity/composition transfer is only an experiment when the route actually accepts those inputs.
The supplied abbreviation PD is not expanded; do not guess its field. Replacing smoke or mist with vapors is an untested lexical suggestion, not a verified fix. Emphatic copy wording, nested weights and a selected success do not isolate a reliable cause. A still crop is not camera motion, and native video output must be distinguished from later external splicing or audio work.
Current-form worksheet: https://duhployed.com/learn/modules/current-form-continuity.html
Tracker design review: https://duhployed.com/learn/modules/affection-tracker-review.html
Scenario worksheet: https://duhployed.com/learn/modules/scenario-engineering.html
