The problem
Educational video creation is repetitive, expensive, and hard to sustain consistently. A single short normally means ideation, scripting, illustration, voice, edit, upload, and analytics review. Most creators burn out before consistency ever compounds.
What I built
BlinkyOwl is an autonomous pipeline that handles the entire loop: topic selection, narration, visual planning, audio, rendering, upload, analytics sync, and self-healing adjustments for the next run. It is not just a content generator; it is a monitored production system with gates.
Why it matters
This project is one of the clearest examples of systems thinking in the account. It combines:
- multi-step orchestration
- strict kids-content safety gates
- observability and post-run telemetry
- feedback loops that improve future runs without letting performance override safety
Public proof despite private code
The repo is private, but the work is still legible because the product output is public:
- live YouTube channel
- live observability dashboard
- concrete operational architecture and quality controls