Varun Nayyar's Progress in Medhavy in July 2026

Not every month of volunteer work produces a pile of new output, and Varun Nayyar's third month on the Medhavy project is a useful example of what a month defined by judgment rather than volume actually looks like. With an outside dependency stuck and outside his control, Varun redirected effort into the things he could actually move: production throughput, project scope, and a full visual direction change.

Working around a blocked dependency

The month's central complication was a narration dependency that stayed unresolved for two months running, diagnosed as an inactive credential and reported to the people who administer the account rather than quietly worked around. Varun's approach was to keep that fact on the record rather than let it get silently absorbed into the schedule: the dependency was not his to close, so he documented it, kept the report open with the right people, and moved his own effort to whatever didn't require it.

Chaining renders to make rebuilds cheap

With narration blocked, Varun built the first four chapters in batch and chained the render commands so an entire set could be produced in a single pass instead of being supervised build by build. That change matters beyond convenience: when a style update arrives later and everything has to be rebuilt, having one command produce the whole set is what makes rebuilding cheap enough to actually do, rather than a chore that gets postponed indefinitely.

Cutting scope from 12 topics to 4

The second decision was subtractive rather than additive. The original plan covered 12 topics; Varun pruned it down to the four that genuinely benefit from animation, following an explicit instruction from the project's leadership to visualize only what actually warrants it. He's candid that this is the harder call to make, since cutting eight planned deliverables looks like less progress on paper even when it's the correct decision for the project.

A new tool and a new visual style

Partway through the month, the project's creative direction shifted again: a new production tool and a distinct visual style were introduced as a creative call rather than a correction of prior work. Varun onboarded onto the new tool, worked out what the style shift meant technically, and delivered three sample videos in the new style for review within a fortnight, logging three weeks at twenty hours each for a total of sixty hours that month.

Key takeaways

• A stalled external dependency was documented and reported rather than absorbed silently into the schedule.
• Chaining render commands turned a full-set rebuild into a single command, making future style changes far cheaper to apply.
• Twelve planned topics were pruned down to the four that actually benefit from animation, following explicit project guidance.
• A new production tool and visual style were onboarded within about two weeks, resulting in three review-ready samples.
• The month totaled sixty documented hours and was reported as in compliance with program expectations.

Who this is for

This update is aimed at anyone following the Medhavy project or the broader Humanitarians AI Fellows program, particularly volunteers curious about how a project keeps moving when a key dependency stalls. It's a practical look at prioritizing throughput and scope over raw output when circumstances outside your control change the plan.