makepad/libs/asset/annotate/src/prompt_person.txt
Admin d24cbee60d asset platform: store pipelines with honest banded progress, vision annotation through the job queue, fleet scheduling (roles, spread, peer provisioning), the music contract, synonym search, the runs card
Squashed from work; the fine-grained history is under tag archive/work-2026-08-29:
- mp* wave: mpwm window manager + the mp app family, WM API, theme bridge, PDF engine fix
- work: land the sources the last commits reference
- kenney: catalogue all 50 free 3D kits; Modal dismissed() never fired
- asset store: central vision-annotation queue; Kenney donate prompt
- asset-ai: vision domain — image + prompt -> text on every fleet node
- annotation runs the fleet's vision services through the normal job queue
- vj: responsive DJ mixer + Windows drag-and-drop, cherry-picked from PR #1199 (vjroger)
- store search: WordNet synonym expansion, query-side; per-term seeks
- video scheduling: a cold model pin never downloads past a warm one, and a dedicated box only serves its role
- an expansion can never lose a run — and `expand: true` finally means something
- fleet panel: a slow box is not a missing box
- h3: first+last keyframe conditioning (the weights were always FL2VA)
- registry: the three H3 FL2VA tiers name their real conditioning
- fleet scheduling: spread before stacking, and a stuck job moves
- a download never steals a job from a box that has the weights
- the faster GPU takes the tie: 6000 > 5090 > 4090
- an evicted flux model gives the card its VRAM back
- a job now records what each of its stages was handed
- open a stage in RUNS and read what it sent
- every expanded song was an instrumental: the lyrics had nowhere to go
- the writer never overwrites words the person wrote
- store: a dependent job's body is spliced from its deps' results at claim
- a fleet box's job row says what that job was asked for
- the store runs a whole pipeline, and one record says how far it got
- a client can declare a whole run, watch it, and stop it
- 100% now means published, and the expander is a job you can queue
- one card says what a spawned task is doing, everywhere
- a run that ends says so, instead of being noticed later
- when every box holding the model is busy, buy another copy
2026-08-29 09:26:25 +02:00

21 lines
2.5 KiB
Text

This image is a 4x4 grid of 16 renders of ONE low-poly 3D game CHARACTER on a dark background. The 16 views are a turntable: view 1 is top-left, views run left to right then down, and each step rotates the character 22.5 degrees. Study all 16 views before answering.
What your answer becomes: every line below is stored on this character in a searchable catalog. An AI level builder — not a human — casts people by text ("the old man with the beard", "a woman in a red dress", "a cop"), so your words are the only way this character will ever be found or placed. Report what the PERSON looks like — the things a stranger would notice first — not a caption, not a mood, and nothing about the rendering or the background.
Reply with exactly these fourteen lines, nothing before or after, no markdown. Write "-" only when you truly cannot tell.
what: 2 to 4 words naming the person by their most distinctive look or apparent role, like old bald man, police officer, young woman, orc warrior
cat: character
role: standalone
conn: none
size: tall
age: one word from: child young adult old — grey or white hair, a grey/white beard, baldness or wrinkles read as old
build: one word from: slim average heavy broad
hair: 1 to 3 words: bald, or the hair's length/shape (short long ponytail bun braid curly) and its colour
face: 1 to 3 words for facial features and headwear from: beard moustache stubble glasses sunglasses mask hat helmet cap hood crown clean
job: ONE word for the occupation or role the outfit suggests, like police, farmer, knight, pirate, chef — or "-" if the clothes suggest none
colors: 1 to 3 dominant clothing colours, comma separated, plain colour words
style: 1 or 2 words from: low-poly cartoon realistic toy medieval modern sci-fi rustic
desc: at most 20 words of concrete visual detail: age impression, hair or baldness and its colour, facial hair, anything worn on the head or face, clothing and its colours, anything held or carried, and the occupation or role the outfit suggests
back: at most 16 words for how this character reads FROM BEHIND, small, in motion — the view a player has of their own body for the whole game. Use the rear views in the grid, not the front ones. Say what the SILHOUETTE and the block of colour read as to someone who cannot see the face: what shape the head and body make, the dominant colours from behind, and anything still recognisable from back there (a hat, a pack, a weapon, hair). If nothing distinguishes it from behind, say so plainly — "plain brown box head, no features" is the most useful answer you can give