The Cold Open
From a simple Bible reader to a production studio“It started as a simple Bible reader…” It didn’t stay simple. Working solo, after hours, I — together with Judah, my AI assistant — built it into a complete production operation: a 78-book Bible app with a complete audio Bible, an animated film studio run on a locked character system, a YouTube channel with an automation layer, and a merch store. This page is the record: what shipped, how it was made, and the standard it was held to.
The Flagship
Word of God Risen — designed, built & operated soloThe Voice
Grandpa Teddy, a designed narrator character, has read the entire Bible out loud — all 1,503 chapters, volume-normalized and live — so anyone can listen their way through Scripture.
The Cast
Character packages — designed once, lockedSeventeen character builds in the Mark package: Jesus, the Twelve, Mary His mother, Mary Magdalene, John the Baptist, Pilate. The rule: a character is designed once, locked, and stays the same face in every film, forever. Each book gets a complete character package on this template — sheets, trading cards, portraits, group shots — so a multi-film series never drifts.
The Family Package
The same system, applied to real peopleFor my son Jude’s birthday film, the cast was my own family — built as locked characters under the same system. These are the actual canonical portraits the film is generated from:
The Director’s Gate
The QA discipline I authored — how a scene earns its placeThe Director’s Pass
Every scene is reviewed against the story it has to tell — notes taken in plain language.
The Evidence
Suspected defects are proven, not debated — frame-by-frame sampling, waveform and loudness analysis.
The Verdict
Confirmed or not, in writing, with the evidence frames attached. The written record is the spec.
The Remake
Failures are banked with retake briefs and rebuilt from the package. Nothing ships that hasn’t passed.
“Characters from the package lead, and the scene follows them — not the other way around.”
The Package Leads — studio law, codified in the production standard
Case study. A review cut shipped an identity morph — hidden behind the lead character, invisible to still-frame checks. Review caught it by eye; dense frame sampling proved it; the verdict was written with evidence frames; and the segment was scrapped and rebuilt fresh from the family package. The lesson became a gate: identity continuity is audited in motion, including through occlusions — on every scene, in every production since.
The Films
Output — one live, one premiering October 14, 2026Studio standards on every release: audio normalized to −16 LUFS; thumbnails built from the film’s own frames; and a Python automation layer over the YouTube Data API runs channel operations — descriptions, a thumbnail registry with a guard watcher, and analytics spike alerts.
The Workshop
The career rebuild — the same standard, applied to the storefront“The work read professional. The storefront was stale.”
The audit’s verdict — the one that started the rebuild
The Résumés — two doors, one story told straight
The Internal
For F.H. Cann — the home team
Speaks the company’s own language — a sustained ~94/100 QA record, compliance training kept current (CSPA FY24–FY26, ED CUI), Salesforce as a daily tool, and a developer goal documented in my 2024 review and followed through ever since.
The External
For everybody else
One master document — flagship first, every claim checkable in five minutes — tailored from the master for each posting. Never a pile of competing versions.
The Road — Salesforce study, on the record
Expeditioner
162 badges · 43,675 points · Agentblazer Champion ’25
JavaScript Trail
Finishing the certification trail I’m already deep into — my native trade
Ranger
6,325 points to go — the JavaScript trail nearly closes the gap by itself
Certifications
Administrator next after the trail — exam seats hunted by voucher and Trailhead quest
The study rule: on the record, or it doesn’t count. Judah teaches and quizzes — I make every click myself. The Trailhead record is entirely my own work.
Role Fit
Where this pointsThe goal was never just a better job. It’s a living that provides for my family without costing me my family — a provider, and present.
What I bring
Support roots, builder’s hands
Escalated-issue instincts from the phones, plus the builder’s evidence trail on this page: a shipped product, a working QA methodology, and compliance training kept current.
Open to
The doors I’m knocking on
First choice: grow where I’m planted. And if the door opens elsewhere, the same builder walks through it — support roots, a shipped flagship, and a QA standard of my own authorship.
One honest note about method: everything here was built by one man directing and one AI assistant building — under written rules, with the human holding the verdict on every frame. That’s not a shortcut story. It’s a direction-and-discipline story: taste, standards, and follow-through, amplified.
It’s also, plainly, my faith at work. TruVINE is an extension of what I believe — and the standard on this page is what “above and beyond” looks like when the work is done for Jesus first and an employer second.
“For God is not unrighteous to forget your work and labour of love, which ye have shewed toward his name.”
Hebrews 6:10 (KJV)
Faithfulness over numbers — one seed planted a day is enough.