GENERATIVE AI & VISUAL SYSTEMS
Image generation, reference-driven editing, ComfyUI workflow design, KREA 2, Qwen Image Edit, Prompt Engineering and visual relationship analysis.
I can take a visual-content task from raw files to a checked live page: prepare assets, maintain naming consistency, upload to WordPress, verify desktop and mobile presentation, and keep the media library usable.
The role match is only the entry point. My broader value comes from connecting domains that are normally separated: visual production, AI models, infrastructure, automation, research, quantitative logic and system design.
Image generation, reference-driven editing, ComfyUI workflow design, KREA 2, Qwen Image Edit, Prompt Engineering and visual relationship analysis.
Character LoRA training, dataset taxonomy, caption rules, identity consistency, labeling systems, testing loops and model-effect optimization.
Image-to-video prompting, motion and camera design, video enhancement, FlashVSR, SeedVR2, Topaz Video AI, FFmpeg and media processing.
NVIDIA GPU environments, CUDA, PyTorch, model quantization, VRAM optimization, Paperspace, RunPod, Docker, Linux services and remote operations.
WordPress, static sites, Cloudflare Tunnel, Zero Trust, R2, Pages, Workers, DNS, HTTPS, storage, file transfer and multi-device content workflows.
Python, Shell, JSON and YAML workflows, AI pair programming, browser automation, Playwright, config-driven systems, feature switches and batch pipelines.
Primary-source tracing, cross-source verification, misinformation detection, timeline reconstruction, logical vulnerability mapping and uncertainty analysis.
Freqtrade, Backtrader, CCXT, price-action rule modeling, scoring systems, first-principles reasoning, decision theory and modular system design.
I am most useful where the problem is real but the path is unclear: unfamiliar tools, fragmented workflows, difficult environments and decisions that need both technical judgment and execution.
Handle website content, images, files, media and routine operations carefully enough that the team does not need to supervise every step.
Combine models, nodes, data, prompts and tools into working image or video systems rather than treating each component in isolation.
Trace failures, compare sources, test assumptions and identify the actual bottleneck before spending time on the wrong solution.
Turn successful manual work into a repeatable process with naming rules, checklists, configuration, scripts or automation.
These examples show the work I naturally take on: unclear requirements, fragmented tools, difficult environments and workflows that need to become repeatable.
Experience across WordPress, visual preparation, media-file organization, cloud storage and content publishing workflows.
Integrated model files, custom nodes, quantized components and context logic across A4000 and L40 environments while diagnosing memory, dependency and compatibility failures.
Created taxonomy and caption rules separating stable identity from variable styling, accessories, expression, pose and framing before training.
Connected cloud startup, application launch, service state, remote access and usage timing through Raspberry Pi, systemd and Cloudflare Tunnel.
Cross-checked original sources, timestamps, translations, repost chains and logical dependencies to separate verified facts from inference and narrative distortion.
Formalized price-action concepts such as ranges, breakouts, pullbacks, signal bars, EMA context and rejection rules into modular scoring and backtesting structures.
I do not merely collect information. I test its structure, trace its origin,
identify distortion and show which conclusions the evidence can actually support.
Useful decisions begin by separating evidence, inference, framing and unknowns.
Most information is not entirely true or entirely false. It is incomplete, reframed, selectively presented, delayed, mistranslated, or detached from its original context. My work is to reconstruct the information chain and build the most defensible model the evidence can support.
Trace claims backward through reposts, citations, screenshots, translations and secondary reporting until the earliest available source is identified.
Compare evidence across languages, platforms, documents, timestamps, images and technical records while detecting shared-source amplification.
Detect where meaning changes through omission, framing, selective quotation, mistranslation, visual manipulation or emotional packaging.
Identify hidden assumptions, invalid inference, circular reasoning, false dilemmas, causal confusion and conclusions unsupported by evidence.
Separate chronology from causality and rebuild the sequence of actors, incentives, constraints, decisions and downstream effects.
Distinguish verified facts from interpretations, hypotheses, disputed claims and unresolved unknowns—and define what would change the conclusion.
A persuasive number is not yet a meaningful comparison. The benchmark must preserve workload, hardware, quality and measurement definitions.
I do not optimize for certainty.
I optimize for the most accurate belief the available evidence can support.
I am most useful when the problem crosses several domains and no single tutorial explains the entire path.
Separate symptoms, requirements, constraints and assumptions.
Use primary documentation, source comparison and direct testing.
Isolate data, model, dependency, compute, network and interface layers.
Create the smallest version that delivers real value.
Document, automate, parameterize and define failure handling.
Technical range only matters if other people can trust the process. I work independently, but I make assumptions, evidence, trade-offs and handoff points visible.
I reproduce the issue, read the primary documentation, isolate the failing layer and return with a clearer problem—not only a request for help.
RESULT / LESS BACK-AND-FORTHI state what is verified, what is inferred, what remains unknown and what evidence would change the decision.
RESULT / BETTER TECHNICAL DECISIONSCommands, configuration, dependencies, failure modes and operating steps are captured so the workflow does not live only in one person’s memory.
RESULT / LOWER MAINTENANCE RISKI do not wait to master an entire field before making progress. I identify the critical unknowns, learn what the path requires and validate each step.
RESULT / FASTER TIME TO FIRST VALUEI would not spend the first month only observing. The goal is to understand the system, prove one useful improvement and leave behind a repeatable operating path.
Understand the team, current workflows, website structure, content rules, technical tools, recurring bottlenecks and decisions that still depend on manual effort.
Take ownership of one real task with visible value—such as a content batch, a fragile workflow or a contained technical problem—and deliver it end to end.
Turn the successful path into a checklist, documented workflow, reusable component or lightweight automation.
Show me a real task: a website content batch, an AI workflow, a technical failure, an information problem or a repetitive process. I can explain how I would reduce the uncertainty, complete the critical path and leave behind a clearer system.