v3: P2 prompt pack (scenes 00, II-V) + pilot bench - regime detect, HUD, hand scrub
This commit is contained in:
@@ -0,0 +1,56 @@
|
||||
# Scene prompt - Course IV: the traffic (pods are cattle, Services are the brand)
|
||||
|
||||
v2 diagram: client -> LB -> Ingress -> Service VIP -> ready pod in the pool, not-ready
|
||||
pod silently removed. "Readiness decides membership - traffic follows." Six parts.
|
||||
Generate ~4 at 16:9, curate with the reject checklist, save to disk for pickup.
|
||||
|
||||
---
|
||||
|
||||
Dark technical exploded-view illustration in a cinematic sci-fi engineering style.
|
||||
Solid near-black deep void background, hex #070b14 - completely clean: no stars, no grid,
|
||||
no texture, no particles behind or around the objects. Matte dark metal-and-glass surfaces
|
||||
with glowing neon edge lighting: primary cyan #3fbaf5, secondary magenta #e879f9 accents,
|
||||
cool white rim highlights. Camera: fixed 30-degree isometric angle, subject perfectly
|
||||
centered with generous empty margins on all sides. Even studio lighting, no vignette,
|
||||
no lens flare, no depth-of-field blur. ABSOLUTELY NO text, no letters, no numbers, no
|
||||
words, no code, no glyphs, no labels, no arrows, no callout lines, no UI elements
|
||||
anywhere in the image - every surface marking must be an abstract geometric pattern
|
||||
only. Every component is fully separated from its neighbours by generous gaps of pure
|
||||
void - nothing touching, nothing overlapping, and no beams, cables, or connectors
|
||||
spanning between the separated parts.
|
||||
|
||||
The subject: six objects arranged in a gentle descending arc from upper left to lower
|
||||
right, a delivery route pulled apart into its checkpoints, each floating alone in void.
|
||||
|
||||
First, upper left: a small smooth luminous white-cyan orb, simple and organic against
|
||||
all the machinery, clearly the visitor of the scene.
|
||||
|
||||
Second: a wide flat splitter wedge of dark metal, its leading edge glowing cyan and its
|
||||
trailing edge fanning into several subtle facets, built to divide incoming flow.
|
||||
|
||||
Third: a tall thin archway frame of dark metal - an open rectangular gate with a cyan
|
||||
glowing inner rim and nothing inside the opening.
|
||||
|
||||
Fourth, centre of the scene: a floating faceted prism of dark glass with a strong steady
|
||||
cyan core glow, the calm fixed point of the whole composition.
|
||||
|
||||
Fifth, lower right: a sealed pod capsule - a smooth dark pill shape with a healthy bright
|
||||
cyan glow and crisp edge light, solid and present.
|
||||
|
||||
Sixth, drifting below and away from the arc: an identical pod capsule but dim - its glow
|
||||
faded to a weak grey-magenta ember, tilted, clearly falling out of the formation.
|
||||
|
||||
---
|
||||
|
||||
## Build-side notes (not part of the prompt)
|
||||
|
||||
- **Slice plan:** 6 polygons - client orb, LB wedge, Ingress arch, Service prism, ready
|
||||
pod, not-ready pod. Collapse packs the arc into a tight column behind the prism; scrub
|
||||
opens the route. The not-ready pod's travel is the teaching beat: it exits the
|
||||
formation as the legend hits "readiness decides membership". Clamp at hero.
|
||||
- **Legend mapping (v2 terms):** client / LoadBalancer "at the edge" / Ingress or Gateway
|
||||
API "host- and path-routing" / Service VIP "the stable name in front of the churn" /
|
||||
pod ready "in the pool" / pod not ready "silently removed". Field note: "the network
|
||||
is broken after a deploy is usually readiness telling the truth".
|
||||
- **Watermark:** Gemini sparkle bottom-right - strip with
|
||||
`bztmon-site/scripts/dewatermark.mjs` before slicing.
|
||||
Reference in New Issue
Block a user