ORBITAL RANCH STUDIOS

STATEMENT OF PRACTICE

I'm a screenwriter, showrunner, and narrative designer. With work spanning film and episodic television, game narrative consulting, and cross-platform storytelling. I've spent my career building systems and story engines that can hold under pressure: writers' rooms with competing creative voices, legacy IP with fifty years of fan expectations, live-service games where narrative has to coexist with weekly gameplay updates.

The constant: figuring out what must stay fixed for a story to succeed, and what can flex without breaking.

// 01 — From Production Problems to Creative Research

Running a writers' room while simultaneously managing transmedia extensions taught me to think in systems. You can't maintain coherence across formats and contributors without clear frameworks: world rules, information protocols, continuity constraints. When we built cross-platform content for shows, it wasn't promotional material. It was narrative architecture that let audiences engage at different depths while the story stayed structurally sound.

That systems thinking deepened when I moved into game narrative. The fundamental shift:

That changes everything.

Players don't want to be told their story. They want conditions that let them forge their own. When you clutch a 1v5 and barely extract with single-digit health, that's your emotional journey.

My job is building the world, setting stakes, and getting out of the way. In interactive formats, over-scripting kills engagement. Narrative lives in world logic, faction rules, environmental storytelling, naming systems - anywhere players read story through play instead of watching it.

My consulting work required negotiation between story logic and gameplay systems. Neither could win at the expense of the other. The solution had to serve both, which meant building shared frameworks that let different disciplines contribute without undermining coherence. I learned to translate high-level creative vision into clear constraints and shared tools that keep teams aligned while shipping at scale.

This work clarified something: the most valuable creative skill isn't execution speed. It's judgment. Knowing which rule to break, when surprise serves story versus when it just creates confusion, how to protect intent through revision.

// 02 — Scribbler's Toolbox: Systems as Pedagogy

The diagnostic tools I built for myself became The Scribbler's Toolbox, a public-facing practice where I publish frameworks, essays, samples, experiments and craft tools. These address recurring creative problems: how to build playable objectives, maintain emotional rhythm across scenes, diagnose structural issues without rewriting blindly.

They're not aesthetic mandates. They're diagnostic instruments that help scribblers identify what isn't working and make specific revisions.

The frameworks come from solving actual production problems under deadlines. They've been tested in rooms where story decisions have budget implications and network notes come at midnight before a production meeting.

// 03 — Modular Storytelling: Matching Method to Market

Traditional feature development demands 110-120 pages before you know if the narrative engine works. Writers commit to full drafts before the structure's been proven. Many stall in the middle where proof is distant and momentum collapses.

My Modular Storytelling Method breaks features into four self-contained units (Reels), each designed to stand as a complete narrative with its own turn and payoff while feeding a larger arc. You can test, revise, and share a single Reel as proof-of-concept. If the engine works, you've got validation. If it doesn't, you've invested 25-30 pages instead of an entire screenplay.

The same structure expands into episodic or adapts to interactive without tearing the story apart. In games, each Reel can become a decision node where player agency changes information flow or consequences, but emotional architecture stays intact. This reflects how contemporary development works: proof-of-concept material often moves further than completed scripts, stories increasingly need to function across multiple formats from inception.

// 04 — AI Tools and Creative Labor

I use AI as a bounded development aid: diagnostics, iteration, stress-testing structure, consistency checks. My interest is understanding how these tools reshape process, collaboration, and taste, and what creative labor remains valuable as automation increases.

Early findings: execution speed matters less than people assume. Tools can generate alternatives quickly, but they can't determine which alternative serves the story's emotional logic. They can identify structural inconsistencies, but they can't weigh whether breaking a rule creates meaningful surprise or just confusion. The creative value lives in those judgment calls, in leading teams through ambiguity, in taste refined through experience rather than computed through pattern matching.

If entry-level execution tasks automate, the value shifts toward leadership, collaboration, conceptual thinking, and the ability to protect intent through revision. This shift affects both professional practice and how craft gets taught.

// 05 — The Questions Driving the Work

My creative practice centers on building narrative engines that can survive scale, collaboration, and change without losing emotional truth. I'm drawn to stories that move across formats, audiences that participate rather than consume passively, and systems that allow meaning to emerge through consequence and choice.

The questions driving my work:

1. How do narrative frameworks enable teams to build at scale while maintaining coherence?
2. How does story function when audiences have agency?
3. What creative labor remains valuable as computational tools automate execution?
4. How can development processes better match contemporary production and distribution realities?

These questions aren't theoretical. They're practical challenges I've encountered across decades of professional production, and shape my creative research.

THE AI MANIFESTO

Fifteen working rules for making things with AI without letting it make you. How I keep the tools bounded, the craft sharp, and the joy intact.

1. Your process IS your product. That flow state when you're deep in the zone? That's not inefficiency. That's where imagination catches fire. Don't let AI optimize away the journey just to reach the destination faster.
2. Keep your hands dirty. There's something irreplaceable about typing until your fingers ache, scribbling notes at 2am, sketching half-formed ideas. Your body and brain are biological partners. Voice commands to LLMs can't replicate the neural pathways and kinesthetic sense that physical creation engages.
3. Embrace productive friction, but prototype fast. Every breakthrough came from wrestling with problems, not sneaking around them. But there's value in generating versions quickly to see what's sticky and what's garbage. Use AI to fail faster so you can find the problems worth solving. Let AI lay bricks. You do the architecture.
4. Build your frameworks first, then amplify with AI. The scribblers who benefit from LLMs already had diagnostic systems before the tools arrived. AI multiplies existing expertise. It doesn't generate it from nothing. If you don't know your craft's deep patterns, AI just gives you faster access to mediocrity.
5. Diversify your curiosity diet. Remember browsing magazine racks? Quantum physics next to motorcycle magazines. Random collision of ideas. That's what algorithms are designed to eliminate. Seek out the weird adjacent stuff that has nothing to do with your current project.
6. Question everything at least twice. When AI gives you research or suggestions, that's your launch pad, not your destination. Deploy the Five Whys. Research the opposite. Dig into peripheral industries. Demand novelty from your LLM. The algorithm's comfort zone isn't where the best stories live.
7. Protect your discovery process. Take meandering walks without podcasts. Sit in diners and eavesdrop. Browse physical bookstores. The best material comes from unexpected encounters that can't be prompted or predicted. Strolls, not scrolls. Embrace serendipity.
8. Share the journey, not the performance. Document your process, but the moment your social media about making things takes longer than actually making things, you've lost the plot. I'm guilty of this too.
9. AI is your research assistant, not your co-scribe. It can gather info and suggest structures. It can't give you the lived experience that makes characters breathe or the cultural insight that makes stories resonate with relevance.
10. Build creative sanctuaries. Carve time and space for just you, your imagination, and a notebook. Your unassisted brain needs room to make those weird, uniquely human connections the algorithms miss. Pen and paper. No substitute.
11. Slow down when it counts. Speed isn't the enemy. Some ideas need time to marinate. Some problems need to be endured and lived with before they're solved. Scribble, ignore, revisit, revise, execute.
12. Watch your cognitive load. AI can reduce the mental weightlifting that keeps your creative muscles strong. Heavy LLM reliance might weaken recall and pattern recognition. If you're not rewriting at least two-thirds of what comes back, you're outsourcing reps you need to stay sharp. Scribbling is training. Don't let AI turn you into a Matrix battery.
13. Your voice is your fortress. We're drowning in AI slop that nails the story math but lacks story soul. Your specific, weird, human perspective is shaped by every conversation you've overheard, every painful failure you've survived. That's the unique stuff LLMs can't replicate.
14. Use AI like a scribble room, not an oracle. Break big problems into smaller questions. Frame questions with context only you can provide. Iterate with follow-ups that sharpen constraints. Filter ruthlessly with professional judgment. Creativity comes from human filters, not machine generation.
15. Joy is the only metric that matters. If a new tool or process is killing your creative spirit, dump it into the molten pit along with Cameron's T-1000. Efficiency without fulfillment is the engine of misery.