Meldwork/docs/assets/harness-engine-architecture.prompt.txt

Use case: style-transfer
Asset type: README technical architecture infographic
Input images: Image 1: the attached flat Meldwork Harness Engine architecture diagram is a structural reference only; preserve its system semantics, but completely redesign the composition, visual language, and module arrangement.
Primary request: Redesign the Meldwork Harness Engine architecture as a premium product-grade AI systems map. Do not use a flat five-row table. Build a spatial architecture around a central 3D control core labeled "HARNESS CORE". The diagram must explain how a user request becomes streamed Agent work, compressed shared context, durable state, and recoverable execution.
Scene/backdrop: deep graphite documentation canvas, subtly textured like a dark technical presentation board; no scenery
Subject and information architecture: center = a beveled dark navy 3D control module titled "HARNESS CORE" with four clear responsibilities around it: "RUN CONTROL", "CONTEXT PACK", "SESSION REGISTRY", "RECOVERY". Upper-left = a 3D conversation surface module labeled "CONVERSATION SURFACES" with two smaller cards "DIRECT CHAT" and "GROUP CHAT"; direct chat connects to "INLINE STREAM", group chat connects to "TRACE PANEL". Upper-right = a media-inspired event module labeled "STREAMING EVENTS" with a waveform strip, playhead markers, and compact event chips labeled "ANSWER DELTA", "TOOL", "PLAN", "STATUS". Left-middle = a stacked translucent capsule module labeled "COMPRESSED SHARED CONTEXT" with smaller tags "STABLE CONSTRAINTS", "RECENT CONCLUSIONS", "EVIDENCE CAPSULES". Right-middle = an Agent runtime constellation with separate beveled tiles labeled "CODEX", "HERMES", "OPENCLAW", and a bridge tile "AGENT ADAPTERS" leading to "TOOL CALLS". Bottom = a horizontal durable-state vault labeled "DURABLE STATE" containing four compact modules "RUN JOURNAL", "RUN LEDGER", "WORKSPACE STATE", "RECOVERY CHECKPOINTS". Include a visible circular session token ring around the core labeled "NATIVE SESSION" and a small arrowed loop labeled "SESSION ROTATION".
Flow semantics: cyan arrows flow from CONVERSATION SURFACES into HARNESS CORE, from HARNESS CORE into COMPRESSED SHARED CONTEXT and AGENT ADAPTERS, from Agent runtime into STREAMING EVENTS and back to the UI. A coral recovery loop labeled exactly "401 RETRY / RECOVERY" and a second coral loop labeled "AGENT TIMEOUT" return from the Agent runtime to HARNESS CORE. Teal persistence lines flow down from HARNESS CORE and Agent runtime into DURABLE STATE. Keep every relationship readable and avoid crossing arrows through text.
Style/medium: high-end 3D technical infographic, dark-mode product architecture board, isometric-lite extruded modules with crisp edges, restrained glass and metal materials, subtle ambient occlusion, precise vector-like labels over 3D forms, premium enterprise systems design, not concept art
Composition/framing: 16:9 landscape, balanced asymmetrical composition with the core slightly left of center and runtime constellation on the right; title at top "Meldwork Harness Engine"; generous margins; modules large enough for README viewing; clear visual hierarchy; no numbered sections
Color palette: graphite and near-black background; dark navy core; electric cyan data paths; teal context and persistence paths; coral recovery paths; violet trace accents; white text; muted silver secondary text
Lighting/mood: cinematic but restrained, soft rim light around the core, controlled highlights on bevels, no dramatic lens flare
Materials/textures: beveled matte metal, translucent context capsules, subtle holographic event chips, waveform and timeline marks, thin luminous connectors
Text (verbatim): "Meldwork Harness Engine", "HARNESS CORE", "RUN CONTROL", "CONTEXT PACK", "SESSION REGISTRY", "RECOVERY", "CONVERSATION SURFACES", "DIRECT CHAT", "GROUP CHAT", "INLINE STREAM", "TRACE PANEL", "STREAMING EVENTS", "ANSWER DELTA", "TOOL", "PLAN", "STATUS", "COMPRESSED SHARED CONTEXT", "STABLE CONSTRAINTS", "RECENT CONCLUSIONS", "EVIDENCE CAPSULES", "CODEX", "HERMES", "OPENCLAW", "AGENT ADAPTERS", "TOOL CALLS", "DURABLE STATE", "RUN JOURNAL", "RUN LEDGER", "WORKSPACE STATE", "RECOVERY CHECKPOINTS", "NATIVE SESSION", "SESSION ROTATION", "401 RETRY / RECOVERY", "AGENT TIMEOUT"
Constraints: preserve the above semantics; all labels must be spelled exactly; use only these labels and no extra prose; prioritize readability over decorative detail; modules must look like one coherent system; show arrows with distinct colors and arrowheads; no logos, no watermark, no fake terminal screenshot, no code blocks
Avoid: flat stacked rows, generic flowchart boxes, white background, pastel corporate template, excessive gradients, neon overload, random 3D objects, tangled connectors, tiny labels, spelling errors, extra captions, stock icons