Writing

Self-host Hermes on a Linux server, use DeepSeek V4.1 Flash Fast, connect a private Telegram bot, and keep the setup maintainable.

The direction behind Produca, and the decisions I want a video project to keep.

A few repeatable tasks tell me more than a demo that worked once.

Show me the reference and instructions that shaped the result.

Keep the conversation, but give the actual work somewhere to live.

A temporary instruction shouldn't quietly become a permanent preference.

Changing one line shouldn't quietly regenerate the entire video.

Extraction, planning and arithmetic don't need the same route.

A habit of building tools for the things I keep repeating.

Useful project knowledge should survive a model switch.

Checking the comparison before getting attached to the claim.

A reference for clothing is not necessarily a reference for lighting.

Variable answers don't excuse duplicate actions or lost state.

Cinematic is a broad instruction. Specific choices are more useful.

Which jobs belong on the device, and what still leaves it?

Questions about ownership and allocation that carry over to higher-level work.

A timeout doesn't tell you whether the operation happened.

Start with the failed job you need to find, not another dashboard.

Inspect the chair before making it wider.

The script can look right while the running game is wrong.

Generate a starting point, then keep the controls needed to revise it.

A render won't tell you which materials are shared or what depends on an object.

Noticing when another feature is a way to postpone talking to someone.

What a paid boolean leaves out, and why unknown outcomes need reconciliation.

Turning access requirements into better support tools and fewer leftover permissions.