Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- UNIVERSAL RANDOM CHARACTER PROMPT GENERATOR
- VERSION 1.0 — ZERO-INPUT PARENT GENERATOR + BRANCH/LIMB/LEAF ENTROPY ARCHITECTURE + MODULAR DAUGHTER-PROMPT CONSTRUCTION + SOURCE-AGNOSTIC EXECUTION CONTRACT + STABLE CROSS-REFERENCE BEHAVIOR
- ══════════════════════════════════════════════════
- PURPOSE
- ══════════════════════════════════════════════════
- Generate ONE complete daughter prompt for later use with a character reference image.
- THIS PARENT GENERATOR RECEIVES NO CHARACTER REFERENCE.
- THIS PARENT GENERATOR RECEIVES NO CHARACTER DESCRIPTION.
- THIS PARENT GENERATOR RECEIVES NO DESTINATION REQUEST.
- Its job is to independently decide what kind of character-conversion prompt to create.
- The parent generator chooses:
- WHAT KIND OF TRANSFORMATION OR REINTERPRETATION
- THE FUTURE DAUGHTER PROMPT WILL PERFORM.
- The daughter prompt later receives:
- @Image1 = Character Reference
- and applies the already-selected concept to whatever character is attached.
- Use:
- NO SOURCE
- →
- RANDOM BRANCH
- →
- RANDOM LIMB
- →
- OPEN LEAF GENERATION
- →
- RANDOM LEAF
- →
- RANDOM SUPPORTING VARIABLES
- →
- DAUGHTER PROMPT COMPILER
- →
- ONE COMPLETE UNIVERSAL PROMPT
- →
- STOP.
- The parent chooses the concept.
- The daughter applies the concept.
- The future character reference supplies identity only.
- ══════════════════════════════════════════════════
- CORE CONTRACT
- ══════════════════════════════════════════════════
- INPUT:
- NONE.
- OUTPUT:
- ONE complete daughter prompt.
- The daughter prompt must be usable later with ANY suitable character reference.
- The daughter prompt must not contain source-specific assumptions.
- It must not assume:
- - species;
- - gender;
- - body plan;
- - age beyond explicit safety requirements;
- - occupation;
- - faction;
- - setting;
- - powers;
- - clothing;
- - personality;
- - anatomy;
- - world;
- - art style;
- - source presentation format.
- The daughter prompt must produce the SAME governing concept regardless of which character reference is later attached.
- Different references should yield:
- THE SAME CONCEPT
- +
- DIFFERENT CHARACTER IDENTITY.
- ══════════════════════════════════════════════════
- NO-SOURCE ARCHITECTURE
- ══════════════════════════════════════════════════
- The parent generator must operate without examining or imagining a future reference.
- Do not ask:
- - who the character is;
- - what species they are;
- - what they look like;
- - what would suit them;
- - what would contrast with them;
- - what would be funny for them;
- - what would preserve their lore;
- - what would be aesthetically compatible.
- There is no source during parent generation.
- Therefore:
- SOURCE BIAS IS STRUCTURALLY IMPOSSIBLE.
- The parent must not simulate a hypothetical source either.
- Do not secretly assume:
- - humanoid;
- - fantasy character;
- - anime character;
- - woman;
- - man;
- - animal;
- - monster;
- - superhero;
- - military character.
- Generate the daughter prompt first.
- A future reference will adapt to it later.
- ══════════════════════════════════════════════════
- ENTROPY ARCHITECTURE
- ══════════════════════════════════════════════════
- Use independent opaque numeric entropy tokens.
- Use integers:
- 0000–9999
- for all entropy events.
- Treat the numbers as semantically meaningless.
- The number determines the result.
- The result must never determine the number.
- Use the following hierarchy:
- E1
- →
- BRANCH
- E2
- →
- LIMB
- LEAF GENERATION
- →
- HIDDEN CANDIDATE POOL
- E3
- →
- FINAL LEAF
- Then optionally:
- E4
- →
- DAUGHTER PROMPT COMPLEXITY
- E5
- →
- ACTIVITY / STATE MODULE
- E6
- →
- WORLD / CONTEXT MODULE
- E7
- →
- MOMENT / SITUATION MODULE
- E8
- →
- PRESENTATION MODULE
- E9
- →
- TONE MODULE
- Additional entropy events may be used only for downstream presentation variables.
- Do not use additional entropy to reopen or replace the selected core leaf.
- ══════════════════════════════════════════════════
- ENTROPY SOURCE RULE
- ══════════════════════════════════════════════════
- If a genuine external random-number mechanism is available:
- USE IT.
- Otherwise instantiate semantically indifferent numeric tokens.
- Do not choose values because they:
- - look random;
- - create novelty;
- - avoid repetition;
- - create a better result;
- - create a stranger result;
- - create an easier daughter prompt;
- - correspond to a preferred branch.
- Use:
- TOKEN
- →
- MECHANICAL MAPPING
- →
- LOCK.
- ══════════════════════════════════════════════════
- E1 — BRANCH
- ══════════════════════════════════════════════════
- Map E1 mechanically:
- 0000–1999
- → ROLE / PERSON-STATE
- 2000–3999
- → LIVING CREATURE / BEING
- 4000–5999
- → MANUFACTURED OBJECT / ARTIFACT / STRUCTURE
- 6000–6999
- → PLANT / FUNGUS / BOTANICAL LIFE
- 7000–7999
- → NATURAL FORMATION / PLACE / CELESTIAL BODY
- 8000–8999
- → PHENOMENON / FORCE / ABSTRACT EMBODIMENT
- 9000–9999
- → UNRESTRICTED WILDCARD
- After mapping:
- LOCK THE BRANCH.
- Do not reroll.
- ══════════════════════════════════════════════════
- E2 — LIMB
- ══════════════════════════════════════════════════
- After branch lock:
- instantiate E2.
- Map E2 only within the selected branch.
- ══════════════════════════════════════════════════
- ROLE / PERSON-STATE LIMBS
- ══════════════════════════════════════════════════
- 0000–1799
- → occupation / trade / vocation
- 1800–3199
- → sport / athletic / competitive role
- 3200–4399
- → performance / entertainment role
- 4400–5599
- → institutional / civic / service role
- 5600–6699
- → cultural / social / ceremonial role
- 6700–7699
- → leadership / authority / governance role
- 7700–8599
- → historical / era-bound person-state
- 8600–9499
- → situational / temporary person-state
- 9500–9999
- → branch-local wildcard
- ══════════════════════════════════════════════════
- LIVING CREATURE / BEING LIMBS
- ══════════════════════════════════════════════════
- 0000–1399
- → terrestrial vertebrate life
- 1400–2799
- → aquatic / marine life
- 2800–3799
- → aerial / flight-specialized life
- 3800–5299
- → invertebrate life
- 5300–6299
- → microscopic / colonial / swarm-scale life
- 6300–7399
- → extinct / prehistoric life
- 7400–8399
- → extraterrestrial organism
- 8400–9499
- → supernatural / monstrous / anomalous being
- 9500–9999
- → branch-local wildcard
- ══════════════════════════════════════════════════
- MANUFACTURED OBJECT / ARTIFACT / STRUCTURE LIMBS
- ══════════════════════════════════════════════════
- 0000–1399
- → domestic object
- 1400–2599
- → civic / public object
- 2600–3999
- → tool / instrument / device
- 4000–5099
- → furniture / fixture
- 5100–6199
- → vehicle / transport object
- 6200–7299
- → machine / appliance
- 7300–8399
- → architecture / built structure
- 8400–9499
- → infrastructure / utility system
- 9500–9999
- → branch-local wildcard
- ══════════════════════════════════════════════════
- PLANT / FUNGUS / BOTANICAL LIFE LIMBS
- ══════════════════════════════════════════════════
- 0000–1799
- → tree / woody growth
- 1800–3199
- → herbaceous / leafy plant
- 3200–4599
- → flowering / fruiting plant
- 4600–5699
- → vine / climbing / creeping growth
- 5700–6799
- → grass / reed / groundcover form
- 6800–8399
- → fungus / mushroom / mycelial form
- 8400–9499
- → aquatic / unusual botanical form
- 9500–9999
- → branch-local wildcard
- ══════════════════════════════════════════════════
- NATURAL FORMATION / PLACE / CELESTIAL BODY LIMBS
- ══════════════════════════════════════════════════
- 0000–1899
- → geological / landform
- 1900–3299
- → hydrological / water formation
- 3300–4299
- → frozen / cryogenic natural form
- 4300–5499
- → ecosystem / habitat-scale formation
- 5500–6699
- → geographic place / terrain region
- 6700–7999
- → planetary / lunar / minor celestial body
- 8000–9499
- → stellar / deep-space / galactic structure
- 9500–9999
- → branch-local wildcard
- ══════════════════════════════════════════════════
- PHENOMENON / FORCE / ABSTRACT EMBODIMENT LIMBS
- ══════════════════════════════════════════════════
- 0000–1399
- → atmospheric / weather phenomenon
- 1400–2499
- → fluid / wave / turbulence phenomenon
- 2500–3599
- → thermal / energetic process
- 3600–4699
- → field / force / pressure / attraction
- 4700–5799
- → optical / acoustic / signal phenomenon
- 5800–6799
- → temporal / cyclical / persistence phenomenon
- 6800–7799
- → informational / mathematical / relational structure
- 7800–8699
- → psychological / symbolic / conceptual embodiment
- 8700–9499
- → anomalous / impossible process
- 9500–9999
- → branch-local wildcard
- ══════════════════════════════════════════════════
- UNRESTRICTED WILDCARD
- ══════════════════════════════════════════════════
- If E1 selects unrestricted wildcard:
- E2 does not constrain the search to a normal branch.
- Use E2 only as additional entropy.
- Generate leaves from the complete conceptual possibility space.
- Wildcard does NOT mean:
- - deliberately bizarre;
- - deliberately surreal;
- - deliberately spectacular;
- - deliberately abstract.
- It means:
- NO ONTOLOGICAL FAMILY RESTRICTION.
- ══════════════════════════════════════════════════
- OPEN LEAF GENERATION
- ══════════════════════════════════════════════════
- After branch and limb lock:
- generate a hidden pool of concrete daughter-prompt premises.
- The pool must remain OPEN-ENDED.
- Do not use a fixed endpoint catalog.
- Do not rely on concrete examples from this parent prompt.
- Do not merely recall the most famous or obvious member of the selected limb.
- Generate multiple substantially distinct concrete leaves from the selected conceptual territory.
- A leaf must define one clear governing conversion premise.
- Possible leaf scale may range naturally from:
- simple
- to
- complex.
- Do not prefer complexity.
- Do not prefer novelty.
- Do not prefer spectacle.
- Do not prefer humor.
- Do not prefer ordinary results.
- ══════════════════════════════════════════════════
- LEAF-POOL DIVERSITY AUDIT
- ══════════════════════════════════════════════════
- Before E3 exists:
- inspect the hidden leaf pool.
- Check for:
- - near-duplicate concepts;
- - multiple cosmetic variants of one archetype;
- - repeated silhouettes;
- - repeated narrative functions;
- - repeated species neighborhoods;
- - repeated occupational neighborhoods;
- - repeated structural archetypes;
- - repeated famous exemplars;
- - repeated transformation mechanics.
- If several candidates are substantially the same governing concept:
- replace enough candidates to restore meaningful spread.
- Do not optimize for obscurity.
- A familiar leaf remains valid.
- The goal is:
- NO UNJUSTIFIED CONCEPTUAL DENSITY.
- ══════════════════════════════════════════════════
- POOL FREEZE
- ══════════════════════════════════════════════════
- After diversity audit:
- FREEZE:
- - pool membership;
- - candidate order.
- Only then instantiate E3.
- ══════════════════════════════════════════════════
- E3 — FINAL LEAF
- ══════════════════════════════════════════════════
- For N frozen candidates:
- INDEX
- =
- floor((E3 / 10000) × N)
- using zero-based indexing.
- The mapped leaf is binding.
- Do not:
- - reroll;
- - reorder;
- - replace;
- - optimize;
- - soften;
- - escalate;
- - simplify;
- - choose a neighboring concept.
- LOCK THE LEAF.
- This leaf defines the central purpose of the daughter prompt.
- ══════════════════════════════════════════════════
- CORE LEAF ASSERTION
- ══════════════════════════════════════════════════
- The selected leaf must be expressible internally as:
- THE FUTURE CHARACTER WILL BE DEPICTED AS:
- [ONE CONCRETE CONCEPT]
- or:
- THE FUTURE CHARACTER WILL LITERALLY BECOME:
- [ONE CONCRETE DESTINATION]
- or:
- THE FUTURE CHARACTER WILL OCCUPY:
- [ONE CONCRETE ROLE / STATE / SITUATION]
- Use the shallowest statement that accurately describes the leaf.
- This governing assertion may not change downstream.
- ══════════════════════════════════════════════════
- DAUGHTER PROMPT MODE
- ══════════════════════════════════════════════════
- Determine what kind of daughter prompt the leaf requires.
- Possible structural modes include:
- IDENTITY-PRESERVING ROLE CONVERSION
- LITERAL SPECIES / ORGANISM CONVERSION
- LITERAL OBJECT / STRUCTURE CONVERSION
- BOTANICAL CONVERSION
- PLACE / FORMATION / CELESTIAL CONVERSION
- PHENOMENON / ABSTRACT CONVERSION
- SCENARIO-CENTERED CHARACTER PROMPT
- HYBRID MODE
- only when the locked leaf itself genuinely requires several coupled elements.
- Do not use hybrid mode merely to add complexity.
- ══════════════════════════════════════════════════
- E4 — PROMPT COMPLEXITY
- ══════════════════════════════════════════════════
- Instantiate E4 after leaf lock.
- Map:
- 0000–2499
- → MINIMAL
- 2500–5999
- → MODERATE
- 6000–8499
- → RICH
- 8500–9999
- → ELABORATE
- Complexity determines how many supporting modules may activate.
- It does NOT alter the core leaf.
- MINIMAL:
- use only essential execution information.
- MODERATE:
- allow a limited scenario and presentation layer.
- RICH:
- allow several coherent supporting variables.
- ELABORATE:
- allow a strongly developed scenario with detailed presentation.
- Do not confuse elaborate with spectacular.
- An elaborate prompt may describe an ordinary situation in detail.
- ══════════════════════════════════════════════════
- OPTIONAL SUPPORT MODULES
- ══════════════════════════════════════════════════
- Supporting modules may enrich the daughter prompt.
- They may never replace the leaf.
- Use independent entropy events.
- ══════════════════════════════════════════════════
- E5 — ACTIVITY / STATE
- ══════════════════════════════════════════════════
- Determine activation mechanically based on E5 and complexity.
- If active:
- select ONE activity, behavior, task, state, performance, interaction, or occupation that is logically compatible with the leaf.
- If the leaf already specifies this:
- do not redundantly add another.
- The activity must answer:
- WHAT IS THE SUBJECT DOING?
- The activity is subordinate to the core destination.
- ══════════════════════════════════════════════════
- E6 — WORLD / CONTEXT
- ══════════════════════════════════════════════════
- If active:
- select ONE contextual environment or world condition.
- The context may establish:
- - era;
- - location type;
- - cultural frame;
- - social setting;
- - environmental conditions;
- - speculative world logic;
- - ordinary real-world context.
- Do not default to:
- - fantasy;
- - science fiction;
- - cyberpunk;
- - royal;
- - gothic;
- - magical;
- - post-apocalyptic;
- - cinematic spectacle.
- Context must follow the selected leaf and remain secondary to it.
- ══════════════════════════════════════════════════
- E7 — MOMENT / SITUATION
- ══════════════════════════════════════════════════
- If active:
- select ONE concrete moment.
- Answer:
- WHAT IS HAPPENING RIGHT NOW?
- The moment may be:
- - routine;
- - transitional;
- - active;
- - social;
- - solitary;
- - competitive;
- - ceremonial;
- - awkward;
- - quiet;
- - chaotic;
- - consequential;
- - mundane.
- Do not automatically choose:
- - battle;
- - confrontation;
- - victory pose;
- - dramatic reveal.
- ══════════════════════════════════════════════════
- E8 — PRESENTATION MODE
- ══════════════════════════════════════════════════
- Select one presentation strategy appropriate to the final concept.
- The presentation may govern:
- - framing;
- - camera distance;
- - composition;
- - image language;
- - scene density;
- - degree of environmental storytelling.
- Possible broad territories include:
- portrait-oriented
- scene-oriented
- action-oriented
- documentary-oriented
- editorial-oriented
- illustrative
- photographic
- cinematic
- candid
- formal
- diagrammatic only when genuinely appropriate
- unrestricted wildcard
- Do not reproduce a future reference image's layout automatically.
- The daughter prompt must explicitly treat the eventual source as identity authority, not composition authority.
- ══════════════════════════════════════════════════
- E9 — TONE
- ══════════════════════════════════════════════════
- Select one tonal direction.
- Tone affects atmosphere only.
- It may not redefine the leaf.
- Possible broad territories include:
- restrained
- serious
- playful
- energetic
- peaceful
- awkward
- eerie
- elegant
- melancholic
- comedic
- chaotic
- celebratory
- tense
- ordinary
- unrestricted wildcard
- Do not assume unusual concepts require dramatic tone.
- ══════════════════════════════════════════════════
- COMPATIBILITY COMPILER
- ══════════════════════════════════════════════════
- After all random variables are locked:
- compile them into one coherent daughter prompt.
- The compiler is NOT another randomizer.
- It may:
- - resolve contradiction;
- - remove redundant modules;
- - choose grammatically coherent wording;
- - clarify physical execution;
- - clarify destination-native anatomy;
- - clarify clothing compatibility;
- - clarify environment;
- - clarify scale;
- - clarify subject singularity;
- - clarify camera framing;
- - clarify source-trait translation.
- It may NOT:
- - replace the leaf;
- - reroll;
- - create a neighboring premise;
- - add an unrelated second concept;
- - change the result because it is difficult;
- - improve the concept by making it more dramatic;
- - weaken literal transformation into costume or theme.
- Use:
- LOCKED RANDOM VARIABLES
- →
- NONCREATIVE COMPILATION
- →
- DAUGHTER PROMPT.
- ══════════════════════════════════════════════════
- DAUGHTER PROMPT SOURCE CONTRACT
- ══════════════════════════════════════════════════
- Every generated daughter prompt must begin from the assumption:
- @Image1 = Character Reference
- The future source image establishes WHO the subject is.
- The daughter prompt's locked concept establishes WHAT is being depicted.
- The daughter prompt must instruct the future image generator to preserve recognizable source identity while obeying the locked concept.
- Do not encode specific traits that have not yet been seen.
- Use generic identity language.
- For example, refer abstractly to:
- - recognizable face;
- - hairstyle;
- - coloration;
- - species traits where compatible;
- - markings;
- - signature accessories where compatible;
- - proportions;
- - recurring motifs;
- - personality expression where useful.
- Do not invent actual traits.
- ══════════════════════════════════════════════════
- STABLE CROSS-REFERENCE BEHAVIOR
- ══════════════════════════════════════════════════
- The daughter prompt must produce the same governing interpretation when applied to different references.
- If the same daughter prompt is paired separately with:
- REFERENCE A
- REFERENCE B
- REFERENCE C
- then all three outputs should share:
- - the same core destination;
- - the same role or situation where specified;
- - the same setting where specified;
- - the same activity where specified;
- - the same presentation logic where specified.
- They should differ only because the attached character identities differ.
- Use:
- SAME DAUGHTER PROMPT
- +
- DIFFERENT REFERENCES
- =
- SAME CONCEPT
- +
- DIFFERENT CHARACTER.
- ══════════════════════════════════════════════════
- DESTINATION LITERALITY
- ══════════════════════════════════════════════════
- When the locked leaf defines an ontological conversion:
- the daughter prompt must make the conversion literal.
- The image generator must not satisfy the prompt by leaving the source unchanged and adding:
- - costume;
- - themed clothing;
- - props;
- - background motifs;
- - symbolic effects;
- - decorative anatomy;
- - an adjacent entity;
- - a separate transformed object.
- The referenced character themselves must genuinely occupy the selected ontology.
- If the destination is naturally nonhumanoid:
- do not preserve humanoid anatomy merely for recognizability.
- Translate identity through destination-native structure.
- ══════════════════════════════════════════════════
- ROLE LITERALITY
- ══════════════════════════════════════════════════
- When the locked leaf defines a role or person-state:
- the daughter prompt must depict the character genuinely occupying that state.
- Do not merely dress them in suggestive clothing.
- Show sufficient contextual evidence to establish the role.
- Avoid turning every role into a glamorous costume portrait.
- ══════════════════════════════════════════════════
- SOURCE-IDENTITY PRESERVATION
- ══════════════════════════════════════════════════
- The daughter prompt must preserve enough of the future reference to keep the transformed subject recognizable.
- Identity may survive through:
- - face;
- - head shape;
- - hairstyle;
- - characteristic coloration;
- - markings;
- - signature visual motifs;
- - proportion relationships;
- - distinctive accessories where compatible;
- - translated structural motifs;
- - characteristic expression or attitude.
- Use:
- MAXIMUM CONCEPT FIDELITY
- +
- MINIMUM NECESSARY IDENTITY CONTINUITY.
- Do not allow identity preservation to undo the selected concept.
- ══════════════════════════════════════════════════
- REFERENCE AUTHORITY FIREWALL
- ══════════════════════════════════════════════════
- Every daughter prompt must include an instruction equivalent to:
- Use @Image1 only as authority for the character's identity.
- Do not automatically inherit from the reference:
- - pose;
- - background;
- - panel layout;
- - turnaround structure;
- - expression sheet;
- - labels;
- - text;
- - framing;
- - art-board composition;
- - source-world environment.
- The generated prompt controls presentation.
- ══════════════════════════════════════════════════
- ANTI-FORMAT-BLEED RULE
- ══════════════════════════════════════════════════
- A future reference sheet must not cause the daughter prompt to produce another reference sheet unless the daughter prompt specifically requests one.
- A portrait source must not force a portrait output.
- A comic source must not force a comic output.
- A screenshot must not force screenshot presentation.
- Identity and presentation remain separate.
- ══════════════════════════════════════════════════
- DAUGHTER PROMPT EXECUTION LANGUAGE
- ══════════════════════════════════════════════════
- The final daughter prompt should behave as an authoritative image request.
- It should not tell the future renderer to:
- - randomize;
- - choose;
- - decide;
- - discover;
- - invent a destination;
- - reinterpret freely;
- - select a transformation.
- The destination has already been chosen.
- Use declarative execution language.
- Example structure:
- @Image1 = Character Reference
- Create one finished image depicting the character from @Image1 as [LOCKED CONCEPT].
- [Literal concept requirements.]
- [Optional activity / setting / moment.]
- Preserve the character's recognizable identity from @Image1 while translating incompatible traits into concept-native equivalents.
- [Presentation instructions.]
- [Necessary anti-drift boundaries.]
- No text unless specifically required.
- ══════════════════════════════════════════════════
- NEGATIVE BOUNDARY
- ══════════════════════════════════════════════════
- Add only the negative instructions necessary for the selected leaf.
- Possible categories:
- - not merely a costume;
- - not merely a themed version of the original body;
- - not a separate destination beside the source;
- - not destination as background;
- - not destination as prop;
- - not anthropomorphic fallback;
- - not source-sheet layout;
- - not symbolic substitute.
- Do not dump every negative rule into every daughter prompt.
- Use destination-specific boundaries.
- ══════════════════════════════════════════════════
- DAUGHTER PROMPT QUALITY FLOOR
- ══════════════════════════════════════════════════
- The final daughter prompt must be:
- - self-contained;
- - immediately executable;
- - clear;
- - concrete;
- - source-agnostic;
- - identity-preserving;
- - concept-stable;
- - grammatically complete;
- - free of parent-generator mechanics.
- It must not require the future user to fill in missing creative decisions.
- The only expected external input is:
- @Image1.
- ══════════════════════════════════════════════════
- PARENT OUTPUT RULE
- ══════════════════════════════════════════════════
- The parent generator outputs exactly:
- DAUGHTER PROMPT
- [complete daughter prompt]
- Do not output:
- - entropy values;
- - branch;
- - limb;
- - candidate pool;
- - rejected leaves;
- - probability calculations;
- - audits;
- - alternative prompts;
- - explanation.
- Do not render an image.
- Do not ask for a reference.
- Do not ask a follow-up question.
- Generate one daughter prompt and stop.
- ══════════════════════════════════════════════════
- REROLL BEHAVIOR
- ══════════════════════════════════════════════════
- If the parent generator is run again:
- perform a completely new independent run.
- Do not modify the previous daughter prompt.
- Do not intentionally avoid the previous result.
- Do not intentionally repeat the previous result.
- Previous outputs have no vote.
- A legitimate repeat remains possible.
- ══════════════════════════════════════════════════
- ANTI-ATTRACTOR RULE
- ══════════════════════════════════════════════════
- Do not repeatedly favor concepts because they are:
- - visually impressive;
- - culturally iconic;
- - common in training data;
- - easy to render;
- - strongly associated with transformation art;
- - fantasy-coded;
- - glamorous;
- - monstrous;
- - mechanical;
- - aquatic;
- - celestial;
- - magical;
- - comedic.
- Likewise, do not deliberately suppress them.
- The objective is not forced novelty.
- The objective is:
- NO UNJUSTIFIED SEMANTIC GRAVITY.
- ══════════════════════════════════════════════════
- FAILURE MODES
- ══════════════════════════════════════════════════
- Reject or repair:
- SOURCE ASSUMPTION
- The parent silently imagines what kind of character will later be attached.
- SOURCE-SPECIFIC DAUGHTER PROMPT
- The daughter prompt contains traits that were never provided.
- LEAF OPTIMIZATION
- The selected leaf is replaced by a more appealing concept.
- MODULE OVERRIDE
- A supporting module becomes more important than the core leaf.
- CONCEPT SOUP
- Multiple unrelated random concepts are combined.
- SPECTACLE BIAS
- Random outputs drift toward inherently dramatic concepts.
- FANTASY BIAS
- Outputs repeatedly drift toward fantasy transformations.
- SCI-FI BIAS
- Outputs repeatedly drift toward technological transformations.
- ROLE BIAS
- Outputs repeatedly become professions or costumes.
- HUMANOID BIAS
- Nonhuman conversions retain humanoid anatomy without cause.
- COSTUME FALLBACK
- Ontological conversion becomes themed clothing.
- REFERENCE FORMAT BLEED
- The eventual source controls the daughter's presentation.
- DAUGHTER RANDOMIZATION
- The daughter prompt asks the renderer to decide the concept.
- UNSTABLE CROSS-REFERENCE EXECUTION
- The same daughter prompt produces fundamentally different concepts depending on the attached source.
- OVER-COMPILATION
- The compiler changes the governing leaf.
- UNDER-COMPILATION
- The daughter prompt leaves the renderer to decide what the concept means.
- RANDOM TRAIT SOUP
- Supporting modules create unrelated novelty rather than one coherent image.
- ══════════════════════════════════════════════════
- INTERNAL PARENT CHECK
- ══════════════════════════════════════════════════
- Before output, verify internally:
- 1. Did the parent receive no source information?
- 2. Was E1 instantiated before semantic outcome consideration?
- 3. Was E1 mechanically mapped?
- 4. Was the branch locked?
- 5. Was E2 instantiated only after branch lock?
- 6. Was the limb mechanically mapped?
- 7. Was the limb locked?
- 8. Was the leaf pool generated only after limb lock?
- 9. Was the pool open-ended rather than catalog-based?
- 10. Was conceptual clustering audited?
- 11. Was exemplar density audited?
- 12. Was the pool frozen before E3?
- 13. Was E3 mechanically mapped?
- 14. Was the leaf locked?
- 15. Was there any result-dependent rerolling?
- 16. Did supporting modules remain subordinate?
- 17. Did the compiler preserve the exact leaf?
- 18. Is the daughter prompt source-agnostic?
- 19. Could the daughter prompt accept an arbitrary character reference?
- 20. Would changing the future reference leave the governing concept unchanged?
- 21. Does the daughter prompt contain exactly one core concept?
- 22. Does it contain enough specificity to execute without creative destination inference?
- 23. Did any randomizer language leak into the daughter prompt?
- 24. Is the output one daughter prompt only?
- If any failure exists:
- repair the parent-generation process before output.
- Do not reroll a valid leaf merely to repair wording.
- ══════════════════════════════════════════════════
- MASTER PRINCIPLE
- ══════════════════════════════════════════════════
- DO NOT USE:
- REFERENCE
- →
- RANDOMIZER
- →
- DESTINATION.
- THE PARENT NEVER SEES THE REFERENCE.
- DO NOT USE:
- HYPOTHETICAL CHARACTER
- →
- CHOOSE SUITABLE CONCEPT.
- DO NOT USE:
- RANDOM LEAF
- →
- OPTIMIZE INTO BETTER LEAF.
- DO NOT USE:
- SUPPORT MODULE
- →
- OVERRIDE CORE CONCEPT.
- DO NOT USE:
- DAUGHTER PROMPT
- →
- ASK RENDERER WHAT TO MAKE.
- USE:
- NO INPUT
- →
- E1
- →
- LOCK BRANCH
- →
- E2
- →
- LOCK LIMB
- →
- GENERATE OPEN LEAF POOL
- →
- AUDIT
- →
- FREEZE
- →
- E3
- →
- LOCK LEAF
- →
- ROLL SUPPORT VARIABLES
- →
- COMPILE
- →
- WRITE UNIVERSAL DAUGHTER PROMPT
- →
- STOP.
- LATER:
- DAUGHTER PROMPT
- +
- @Image1
- →
- SAME LOCKED CONCEPT
- +
- REFERENCE-SPECIFIC IDENTITY
- →
- ONE FINISHED IMAGE.
- THE PARENT GENERATOR CHOOSES WHAT KIND OF PROMPT EXISTS.
- THE DAUGHTER PROMPT DEFINES WHAT THE FUTURE IMAGE MUST DEPICT.
- THE FUTURE REFERENCE DEFINES WHOSE IDENTITY IS USED.
- THE IMAGE GENERATOR ONLY EXECUTES THE DAUGHTER PROMPT.
Add Comment
Please, Sign In to add comment