v3: P2 prompt pack (scenes 00, II-V) + pilot bench - regime detect, HUD, hand scrub
This commit is contained in:
@@ -0,0 +1,54 @@
|
||||
# Scene prompt - Course III scene A: the node (where intent becomes a process)
|
||||
|
||||
v2 diagram: kubelet -> containerd/CRI-O -> CNI -> kube-proxy, pod lands here.
|
||||
"kubelet drives, runtime executes, cni wires, proxy routes." Five 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: five machines arranged in a descending diagonal chain from upper left to
|
||||
lower right, one workstation pulled apart into its stations, each floating alone with
|
||||
generous void between them.
|
||||
|
||||
First, upper left: a compact command module - a dark angular unit with a bright cyan
|
||||
glowing visor strip across its front, alert and directive, the driver of the chain.
|
||||
|
||||
Second: a powerful engine block - the largest unit, dark layered metal with visible
|
||||
stacked internal plates glowing faint cyan at their edges, an industrial machine built
|
||||
to assemble and launch things.
|
||||
|
||||
Third: a wiring hub - a dark ring-shaped unit with evenly spaced glowing cyan ports
|
||||
around its rim and one bright magenta port, clearly the connector of the group.
|
||||
|
||||
Fourth, lower right: a routing prism - a faceted dark crystal wedge with thin magenta
|
||||
light tracing its edges, sharp and directional.
|
||||
|
||||
Fifth, floating just above the chain's midpoint: a small sealed capsule - a smooth dark
|
||||
pill-shaped pod with a soft white-cyan glow, the payload this whole chain exists to run,
|
||||
descending toward the engine block but not touching anything.
|
||||
|
||||
---
|
||||
|
||||
## Build-side notes (not part of the prompt)
|
||||
|
||||
- **Slice plan:** 5 polygons - kubelet visor module, containerd engine, CNI ring hub,
|
||||
kube-proxy prism, the pod capsule. Collapse packs the chain into one tight machine
|
||||
(capsule docked); scrub opens the diagonal and lets the capsule hover. Clamp at hero.
|
||||
- **Legend mapping (v2 terms):** kubelet "node agent - the only thing that starts your
|
||||
container" / containerd/CRI-O "pulls images, runs containers (CRI)" / CNI plugin
|
||||
"a real IP per pod" / kube-proxy or eBPF "makes Services route" / pod "lands here".
|
||||
- **Watermark:** Gemini sparkle bottom-right - strip with
|
||||
`bztmon-site/scripts/dewatermark.mjs` before slicing.
|
||||
Reference in New Issue
Block a user