AI in the Creative Industry

FROM IDEA
TO RESULT

How I actually use AI in creative work — hands-on, not theory.

Obai Sukar — Co-Founder at NHJ
TechTown × aiSalon — Sunday, August 2, 2026 — 5:00 PM — Damascus

ASK THE ROOMHands up — who has already released something made with AI?

QR code to save Obai Sukar's contact card

Scan to
save my
contact

Good evening, and welcome to TechTown. I want us to start with a simple agreement: this session won't be a lecture defining artificial intelligence, it won't be a list of tool names, and I won't show you polished results I prepared in advance and then claim we made them together. We're going to do something harder and more useful. We'll start with a completely new idea from this room, and try to turn it into a short project with image, motion, sound and music. We'll see what works, what fails, how we tell the difference, and how we fix the result when it's weak. I've worked in audio and production for more than twenty-five years, and today I run my creative work with a mix of human experience and AI tools. So I won't talk about the tool as a miracle, and I won't treat it as an enemy. I'll talk about it the way I actually use it: a powerful tool inside a working system — not a replacement for the person holding the vision.

Before We Start

If you don't know how to use
something — ask AI.

If you don't know how to ask AI —
ask AI.

That's it. That's the whole skill tonight.

Who's Talking

Twenty-Five Years, Then Two With AI

25+ years

Audio engineering and media production — studio, broadcast, live sound, post.

762K subscribers · 333.9M views

Karazah Channel — co-founder, MBR Arabic Language Award 2023.

500K daily listeners

Radio Al-Kul — co-founder, coverage by NPR and Al Jazeera.

AI joined the practice two years ago. It didn't start it.

What I Believe

Ten Things About AI — Part One

01AI can make you smarter — if you use it correctly.

02It can help you think better — or trap you in a rabbit hole with no bottom.

03The first answer is a draft, not a verdict.

04A vague prompt returns a random result — you can't call random "yours."

05Confidence is not evidence — it can be completely sure and completely wrong at once.

Ten things I actually believe about this stuff — not theory, lessons I paid for. Five now, five right after. One: AI can make you smarter, if you use it correctly. That "if" is doing all the work in that sentence, and most of tonight is about what goes inside it. Two: it can help you think better, or it can trap you in a rabbit hole with no bottom — ten tabs open, every one a plausible detour, and you look up and the hour is gone and you have nothing to show for it. Three: the first answer is a draft, not a verdict. We'll come back to this exact idea later with a real example. Four: a vague prompt returns a random result, and you can't honestly call random "yours." This is the whole ownership argument of tonight, in one line. Five: confidence is not evidence. An AI can sound completely sure and be completely wrong in the same sentence — sounding right and being right are different skills, and only one of them is the model's.

What I Believe

Ten Things About AI — Part Two

06One AI agreeing with itself isn't proof — it's an echo.

07Consistency isn't talent. It's a reference you locked down before you asked for anything.

08The tool executes. It doesn't know what's worth making — that part's still on you.

09Thirteen patches never finish a system. One honest rebuild does.

10Every corner AI lets you cut shows up again at review — pay for it up front, or pay for it twice.

Six: one AI agreeing with itself isn't proof of anything — it's an echo with better grammar. This is exactly why review has to come from somewhere else, not from asking the same model again. Seven: consistency isn't talent, it's a reference you locked down before you asked for anything. We'll hit this again hard in the mistakes section — a real story about a character that changed in every scene. Eight: the tool executes. It doesn't know what's worth making — that judgment call is still entirely yours, no matter how good the tool gets. Nine: thirteen patches never finish a system. One honest rebuild does. I've lived this one the expensive way, more than once. Ten: every corner AI lets you cut shows up again at review — you pay for it up front by doing it right, or you pay for it twice by fixing it later, angrier, with less time. Keep these ten in your head — everything else tonight is just proof.

The Shift

I Stopped Managing Tools. I Started Managing a Team.

For twenty-five years, every tool in the studio did exactly what I told it — nothing more, nothing less. I was the only variable.

AI broke that. The output got good enough, fast enough, that treating it like a plain tool stopped making sense. So I stopped. Every AI I use now gets treated like an internal hire — a role, a scope, something it's accountable for, same as anyone else on the team.

That's the real shift. Not that AI got powerful — that I changed how I manage it.

[Presenter reminder: this is the seed for the council idea later — plant "internal hire, a role, accountable" here, don't explain the mechanism. Just the shift in mindset.] This is the piece I actually want you to walk away with tonight, more than any single tool. For twenty-five years, every tool in my studio did exactly what I told it — a mixer, a camera, an editor — nothing more, nothing less. I was the only variable in the equation, for better or worse. AI broke that pattern. Somewhere in the last two years, the output got good enough, fast enough, that I couldn't keep treating it like just another tool. So I changed how I manage it — not what I use, how I manage it. Every AI in my workflow now has a role, a scope, and something it's accountable for, the same as anyone else on a real production team. That's the actual shift underneath everything I'm about to show you. Not "AI got powerful" — that's obvious. The shift is that I changed my own management model to match. And that raises the real question for the room tonight —

One More Thing

Most of This Runs on My Own Machines

Tonight's pipeline isn't just cloud subscriptions. It's a full local AI system — dozens of tools, several models running entirely offline, built specifically for media production.

More on that when we close.

?

What has actually changed?

The Landscape

Four Real Shifts

Reaching the first version

What used to take days can now start within hours.

Team size at the experiment stage

A small team can test an idea that used to need more specialties.

The cost of trying

Prototyping and testing alternatives is far cheaper.

The value of creative judgment

The faster execution gets, the more selection, review and rejection are worth.

ASK THE ROOMWhich of these four actually changed how you work?

I see the real change in four places. First, the time needed to reach a first version collapsed. I don't mean the final version — I mean the first thing we can see or hear and discuss. That matters, because an idea in our heads never reveals its flaws; a first version does. Second, a small team can now test ideas that used to require more specialties. A writer can see a visual concept, a designer can hear a sound concept, and a director can build a quick model before spending a production budget. Third, the cost of trying dropped. We can now test three angles or five styles before choosing. But cheap attempts can also produce a huge pile of mediocre material if we don't know when to stop. Which brings us to the fourth shift: the value of creative judgment went up. When execution is available to everyone, the advantage is no longer pressing the button — it's knowing which result deserves to stay, which must be rejected, and why.

?

Does AI create the idea?

The Pivot

The Tool Executes What You Can Describe — and Judge

Vision

What do you want the audience to feel?

Craft knowledge

Which decisions produce that result?

Judgment

What worked, what failed — and why?

Execution & iteration

This is where AI expands your reach and speed.

AI doesn't read your mind; it works on the decisions and references you give it.

ASK THE ROOMYour last prompt: were you deciding — or just hoping?

My answer: the tool doesn't execute what we imagine inside — it executes what we can turn into decisions, and then judge. Vision comes before the prompt. Before I describe a lens or a light or a style of music, I have to know what I want the audience to feel. Tension? Calm? Should the image feel human and close — or engineered and decisive? Then comes craft knowledge. In music, it's not enough to say "I want something sad." I need to know how rhythm, arrangement, harmony, space and performance create that feeling. In image, "cinematic" isn't enough; I have to understand composition, lens, light direction, color, and camera movement. Then judgment. The tool may give me a beautiful result that doesn't serve the idea — or a less flashy one that's more honest. The tool cannot make that call for me unless I can see the difference myself. Execution and iteration is where these tools genuinely excel: generating possibilities fast, compressing repetitive work, getting me from idea to reviewable material. That's why I say: without a visual, sonic or narrative vocabulary of your own, you'll mostly get surprises. Some of them beautiful — but not necessarily extensions of a vision that existed before the result.

The Method

Creativity Is a Loop, Not a Flash

01Idea

02Questions

03Prototype

04Review

05Release

06Learn ⟲

Then we return to the start — as a better version of ourselves.

ASK THE ROOMWhere does your process usually stall?

The Working System

The Council: A System of Roles, Not One Answer

The Maestro

Sets the plan and splits the task.

The Executor

Builds the file, the code, or the model.

The Critics

Test the idea from opposing angles.

The Verifier

Checks the details before anything ships.

ASK THE ROOMWho — or what — is the critic when you make something?

I don't treat AI as one person I ask, who then hands me the truth. I treat it as a set of roles. There's the Maestro: understands the goal, splits the work, decides what happens first. The Executor: writes the code, builds the file, makes the model. The Critics: one hunts for gaps, another argues the opposite position, a third asks whether the idea is even clear to an audience that doesn't share its context. Then the Verifier — who doesn't care how beautiful the idea is, only that the numbers are right, the files work, and the claims don't outrun the evidence. These roles might live inside one tool, or be spread across several. What matters is that the voice producing the work is never the same voice approving it without resistance. This is how good production houses work: the writer doesn't review alone, the editor doesn't lock the first cut, and the sound engineer doesn't mix and deliver without checking on more than one listening system.

Not Hypothetical

Seven Real Seats, Each With a Veto

Acoustic engineer

Vetoes physics, formulas, units, accuracy claims.

UX / UI

Vetoes every new surface, onboarding, information density.

Consumer / tester

Ship or no-ship — can a non-expert finish the task unaided?

The exact rules behind it — how the seats actually run — is a longer conversation than tonight.

[Presenter reminder: share the WHAT and the scale here — seat titles, the number seven, that it's real. Don't walk through the actual review protocol, the veto rules, or the gate sequence — that's the masterclass, not a free session. If someone asks live "how exactly does that work," it's completely fair to say "that's exactly what the masterclass covers."] This isn't a metaphor I made up for tonight. In my actual practice, the council is seven standing seats, each one owning a specific domain — an acoustic engineer, a UX seat, a consumer-tester, and four more. Real people's job titles, mapped onto how AI output gets checked before it ships. I'm not going to walk through the exact rules tonight — how the seats actually run, what makes one override another — because that's a longer, denser conversation than a one-hour room. What I want you to take from this is simpler: this isn't one AI you trust blindly. It's a structure, and the structure is what makes the output trustworthy, not the model.

?

How many questions do I ask before accepting a result?

The Habit

AI Is a Drilling Tool, Not an Oracle

01 — What is this idea missing?

02 — Where could it fail?

03 — What's the opposite angle?

04 — What's the evidence, and how certain is it?

The first answer is material for review — not a final verdict.

ASK THE ROOMBefore you trusted the AI — what did you ask it last?

There is no sacred first answer. I use the tool to drill deeper into an idea, not to stop at the first clever-sounding phrasing. I ask it: what's missing here? Then I ask it to imagine the ways this could fail. Then I demand the completely opposite angle — because these tools tend to agree with however you framed the question. And when the topic involves a fact, a number, or a technical judgment, I ask for the evidence and the degree of certainty, then verify with a proper source. There's an important distinction between error and uncertainty. An execution error means I asked for something specific and it wasn't delivered as asked — that needs fixing. Declared uncertainty means the tool doesn't have enough evidence and says so clearly — that's not a scandal; it's a signal that the decision belongs to a researcher or a specialist. The more important the result, the more it needs a second or third voice reviewing it. Not because AI is bad — but because review is a core part of any professional work, machine or no machine. There's a version of this I say in my own practice: a client can plan around a stated margin. Nobody can plan around a number that was quietly wrong. That's the whole reason the distinction matters.

?

Where do we start — the tool, or the idea?

Before Any Tool

First — Write the Scenario

A man stands alone in an old city street at dusk. The day is ending; shops are closing behind him. He isn't crying, and he isn't broken — just still, deciding whether to go home or begin again. Feeling: quiet sadness, with a thread of resolve. Length: 15–20 seconds, three beats — stillness, a breath, a first step.

One idea. Three crafts will now serve it: sound, image, motion.

ASK THE ROOMThink of one scene you'd want to make — hold that thought for the live project.

?

What separates describing a mood from a musical decision?

Case Study · Sound

Clear Words, Missing Decisions

The generic prompt

A sad song, but not typical — no clichéd nostalgia.

What didn't we specify?

The key or mode.
Meter and tempo.
The chord progression.
Instrumentation and arrangement.
Performance style and spatial texture.

The result: the machine will make most of the decisions for you.

ASK THE ROOMWhat's the first thing you'd put back into this prompt?

This sentence sounds specific: we want a sad song, but not a typical or cheaply sentimental one. Yet it contains not one musical decision that can be executed precisely. We didn't specify a key or a mode. We didn't set a meter or a tempo. We didn't say what the progression is, how the notes are voiced inside the chords, what the instruments are, what the space feels like, or how it should be performed. The tool will fill those gaps with its own expectations. We might like the result — it might even be more beautiful than what we imagined — but let's be honest: most of the decisions in that case were not ours. That doesn't make generic prompts wrong. They're fine for exploration, for discovering an unexpected direction. But there's a difference between exploring by chance and steering the work toward a vision whose elements you actually know.

Case Study · Sound

The Knowledge That Makes the Difference

The key

D Major

The progression

Gmaj7 → Dmaj7 · IVmaj7 → Imaj7

The voicing

A low root on beat one, then the upper chord on beats two and three. F# is the shared anchor tone.

The rhythm

3/4, very slow. One chord per bar.

The progression does reach the tonic — but Dmaj7 keeps the landing open and translucent.

Now we turn the mood into decisions. The piece is in D Major. The progression repeats between Gmaj7 and Dmaj7 — the fourth degree to the first, both as major-seventh chords. Let's be precise: this motion does arrive harmonically at the tonic chord, so it's wrong to say it never resolves. But it never gives a hard, triumphant cadence either, because Dmaj7 contains the note C#, which keeps the color open and translucent. The voicing starts with a solitary low root on beat one: G, then D. The upper chord follows on beats two and three: B–D–F# over G, then A–C#–F# over D. F# stays on top as the shared tone, binding the two chords and softening the transition. The meter is 3/4, very slow, one chord per bar. And the space in time between the bass note and the upper chord is part of the expression — not a gap that needs filling. This is what craft knowledge means: we're no longer saying "sad and beautiful." We now have something we can attempt, evaluate by ear, and correct.

Case Study · Sound

Turning Knowledge into Executable Instructions

[Intro] [D major] [3/4, very slow] [Instrumentation: sparse cello and piano] [Harmony: Gmaj7 to Dmaj7, one chord per bar] [Voicing: low root on beat 1, upper chord on beats 2–3] [Mood: melancholic, suspended, understated] [Vocals: distant, wordless choir]

A precise prompt increases your steering power — it doesn't guarantee literal musical execution.

With these instructions, the tool now holds far more decisions: key, meter, tempo, instruments, progression, harmonic rhythm, voicing, mood, and the nature of the human voice. But let's not oversell it. A music generator is not notation software, and not a DAW executing MIDI literally. It may honor the mood and the instruments, then change the progression or the voicing. So I listen to the result as an attempt — not as proof that the prompt was executed to the letter. If I need a specific harmony that must not change, the right path is to build it in the DAW or via MIDI, and use AI in the spaces that welcome chance: color, performance, an initial arrangement, exploration. The point isn't that longer prompts are always better. The point is that every detail should represent a decision I can explain. That was sound. Now let's test the same principle on the still image, then on motion — the rule stays the same; only the craft changes.

Live Break

Now — Try It in Suno

VPN on. Open suno.com. Paste the prompt. Hit generate.

▶ suno.comPaste the prompt

⏱ TWO MINUTES

What did it keep — and what did it rewrite without asking?

Quick Break

Music's Done — Image and Motion Next

Stretch, refill your coffee, or grab me directly. Back in a few minutes.

Scan to save my contact

?

What separates describing a mood from a visual decision?

Case Study · Image

Clear Words, Missing Decisions

The generic prompt

A sad, cinematic photo of a person standing in the street — nothing clichéd.

What didn't we specify?

Camera angle and height.
Focal length: compress the background, or open it up?
Light direction and temperature.
Depth of field.
Composition: centered, or leaving negative space?
The reference color palette.

The result: the machine decides for you — "cinematic" only in the generic sense.

Case Study · Image

The Knowledge That Makes the Difference

Composition

The figure on a third of the frame, negative space opposite the gaze — the emptiness itself carries the feeling.

Lens

85mm, shallow depth of field — separating the figure without fully isolating it.

Light

A cool rim light drawing only the edge, no fill — the mystery is part of the feeling.

Color grade

Low contrast, desaturated broken tones; not black-and-white, not vivid.

ASK THE ROOMLook at this image: what did we still leave to chance?

This is craft knowledge in the image — the exact counterpart of what we did in music. Composition is a decision, not an outcome: I place the figure on a third of the frame and leave the empty space opposite the direction of the gaze, because in this kind of picture the emptiness carries as much feeling as the figure. I choose an 85mm lens with shallow depth of field, so the figure separates from the background without being cut out of it. I decide the light is a cool rim from behind, drawing only the edge: what the image doesn't show is part of what it means. And I choose a desaturated, low-contrast grade — because untheatrical sadness doesn't shout in color, and doesn't collapse into ready-made black-and-white either. Every one of these items can be reviewed, criticized and changed. That is the difference between describing a mood and making a visual decision.

Case Study · Image

Turning Knowledge into an Executable Prompt

A photorealistic image of a single figure, back three-quarter view, standing in a quiet old-city street at dusk. Compose on the rule of thirds, negative space toward his gaze. 85mm look, shallow depth of field. Cool rim light only — no fill, low-key. Desaturated, broken tones, low contrast. Melancholic and restrained: no visible tears, no rain cliché.

A precise prompt increases your steering power — it doesn't guarantee literal visual execution.

Live Break

Now — Make the Image

ChatGPT or Gemini — paste the prompt. Generate.

▶ ChatGPT▶ Gemini

⏱ TWO MINUTES

Which choice did the model steal from you?

?

What separates describing a mood from a motion decision?

Case Study · Motion

Clear Words, Missing Decisions

The generic prompt

Animate the image of the person standing in the street — make it cinematic and emotional.

What didn't we specify?

The type of move: push in, pull out, slide — or hold still?
Speed and duration.
Which element stays locked as the anchor?
The easing curve.
Does the move serve meaning — or is it just decoration?

The result: the camera moves — but the meaning doesn't necessarily change.

Case Study · Motion

The Knowledge That Makes the Difference

Move type & function

A very slow push-in builds quiet tension; total stillness is sometimes stronger than any move.

The anchor

One element in the frame stays visually locked for the whole shot.

The motion curve

Soft ease-in and ease-out; robotic linear motion is what exposes a generated shot.

Shot duration

Measured in seconds — not in vague description.

Case Study · Motion

Turning Knowledge into Executable Instructions

Animate this image: a slow push-in, from wide to medium. Keep the figure centered as the anchor; let the background drift subtly. Four seconds, ease-in and ease-out — no linear motion. No pan, no rotation: one axis only. The motion should build quiet tension, not spectacle.

A precise prompt increases your steering power — it doesn't guarantee literal motion execution.

Live Break

Now — Animate It

Gemini — or Magnific, and let it pick its best video model. Still + prompt. Generate.

▶ Gemini▶ Magnific

Did the move carry the idea — or just dress it up?

?

When does the result become an extension of my vision?

The Standard

More Decisions, Less Chance

Direct

Define what you want — and why.

Compare

Test several options against a clear standard.

Reject & revise

Don't let liking a result erase your vision.

A standard for creative contribution — not a legal ruling on ownership or copyright.

ASK THE ROOMWhich decisions should always stay yours?

For me, my relationship to a result isn't measured by how many words I typed into the prompt — it's measured by how many conscious decisions I made along the way. Did I define the emotional goal? Did I choose the reference? Did I know why I rejected the first version? Did I compare results against a standard, or just pick the flashiest one? Did I revise until the result approached a vision that existed before it appeared? The more of those decisions there are, the less the outcome owes to chance — and the closer it comes to being the extension of a clear human vision. But this is a conversation about creative contribution, not law. Commercial ownership, terms of use, and copyright eligibility are separate questions that vary by tool, paid plan, country, and the share of human contribution. We shouldn't confuse the two. And I'm not saying simple prompts are wrong — they're great for exploration. I'm only saying: let's be precise about the role we played, and the role we left to the machine and to chance. A vague instruction to any tool returns a random result, and a random result cannot honestly be called yours. Twenty-five years of banked visual and sonic vocabulary isn't made obsolete by these tools — it's the only thing separating authorship from a lottery ticket.

?

What did my mistakes teach me?

Confessions

Four Mistakes That Built My System

I built the same system six times

Fix: one central registry; every retired system formally archived.

I believed the first answer

Fix: independent reviews; a clear line between error and uncertainty.

The character changed every scene

Fix: a locked reference, locked specs, every consistency tool available.

The voice was so perfect it died

Fix: deliberate variance, natural pauses, a human take when needed.

ASK THE ROOMWhich of these four have you already done?

Mistake one: I built the same work-organization system six times, each time under a new name, each time convinced it was final. The problem was never the tool — it was that I loved the moment of building more than the discipline of using. The fix is one central registry showing what's active, what's paused, and what's archived. An old system doesn't linger as an open ghost, and doesn't get deleted on a whim; it's retired by an explicit decision. Mistake two: I believed the first answer. It looked tidy and confident, so I skimmed past it — and discovered precise errors later, at a much higher price. So now I separate who executes from who reviews, and I distinguish an execution error that must be fixed from a declared uncertainty that needs a source or an expert. Mistake three: my first multi-shot generated video — the character looked different in every scene. Similar wording was not enough. I needed a locked reference image, exact unchanging specs, and Reference or Seed or character-consistency features wherever the platform supports them. And even then, visual review stays mandatory. Mistake four: I used a generated voice that sounded perfect — clean diction, even rhythm, zero errors. It sounded dead. Life in a performance isn't chaos, but it isn't machine symmetry either. I added uneven pauses, small shifts in intensity and tone, and sometimes recorded a human take and blended it with the generated material. The lesson: a mistake isn't the opposite of a good system. Very often, it's the raw material a good system is built from.

The Chain

The Real Production Pipeline

01Idea

02Script

03Storyboard

04Design & animation

05Sound & music

06Edit & review

Every stage has a right tool — and every tool has a failure to know before delivery.

ASK THE ROOMHonestly — which stage do you usually skip?

?

Can we build a new project in front of you — right now?

Yes — from zero, with no hidden pre-made result.

Live · 50 Minutes

The Live Project

01Pick the idea & write the creative brief5 min

02Build a 3–4 scene storyboard10 min

03Produce & animate the key shot10 min

04Design the sound & music10 min

05Fix the weak version10 min

06Edit & screen it5 min

ASK THE ROOMCall it now: how much of what we're about to make will be AI — and how much us?

We'll split the work into six stages, each with a time limit. The goal is not to produce a broadcast-ready ad in fifty minutes. The goal is to watch an idea being translated into decisions — and to watch each stage expose a new problem. Stage 1 — idea and brief (5 min): I'll take only three words or moods from the room. Then we write, in front of everyone: "We're making a 15–20-second visual piece about [the idea], aimed at [the audience], that must leave the feeling of [the intended effect], through 3–4 connected scenes, without long dialogue." That sentence is our standard: if we produce a beautiful shot that doesn't serve it, we reject the shot — even if we love it. Stage 2 — storyboard (10 min): I give the tool the duration, audience, effect, scene count and constraints, and ask for three different structures with a comparison. Let the room vote A / B / C between the feasible ones — I keep veto on feasibility — then cut scenes that don't change meaning. Stage 3 — key shot and animation (10 min): one reference image defines the character, wardrobe, color, lens and light; every other shot uses the same reference and the same locked specs. I separate content (changes per scene) from style (never changes). For motion, I define what moves, what stays, the camera direction and speed, the start and end. Stage 4 — sound and music (10 min): the music's function first — does it drive rhythm, build tension, leave room for sound design? Then tempo, meter, instrumentation, density, and the shape of the beginning and end. I listen critically, and I don't claim the generator executed anything literally. Stage 5 — fixing the weak version (10 min): we name the problems before touching any tool — at most three, ordered by impact. There's no good repair without a clear diagnosis. Stage 6 — edit and screening (5 min): a simple honest cut; we delete anything that adds no meaning.

Diagnosis First

What Will We Fix When the Version Fails?

A generic idea

No clear shift, no specific angle.

Beautiful frames, no story

Every shot works alone — none together.

Weak visual consistency

Character, color, lens or place keeps changing.

Motion without function

The camera moves; the meaning doesn't.

Music bigger than the project

Huge trailer music smothering the idea.

A perfect, lifeless voice

Rhythm too even, diction too polished.

ASK THE ROOMWho's had an AI piece rejected by a client — and why?

Takeaways

Six Ideas I Want You to Keep

01Creativity is a system, not a flash of inspiration.

02The first answer is the start of review, not the end.

03Craft knowledge turns mood into decisions.

04Consistency comes from reference and discipline.

05Mistakes are raw material for a better system.

06AI speeds up execution — it doesn't excuse the human from judgment.

ASK THE ROOMWhich ONE idea from tonight hits your work on Monday morning?

Not Just Tonight

This Pipeline Already Shipped

Required Field · الحقل المطلوب

Ninety seconds, no dialogue, no human face until money arrives — the antagonist is a validation error. Twenty-eight storyboard stills, first scenes animated, two cuts from one spine.

Sixty-plus systems, one council, one standard — tonight is one room in a bigger house. The how lives in obaisukar.com and the masterclass, not in a one-hour talk.

[Presenter reminder: this is the generous-but-protected close. Give them the scale and the proof it's real — not the mechanism. The gap between "impressive" and "I could just do this myself" is exactly where the masterclass lives.] One more thing before we close. What you saw tonight — idea, storyboard, image, motion, sound, edit — isn't a demo I built for this stage. It's the same pipeline I used on a real short film called Required Field: ninety seconds, no dialogue, no human face until the money arrives, and the antagonist is a validation error. Twenty-eight storyboard stills, the first scenes animated, released as two cuts from one spine. That's one piece of a larger practice — sixty-plus catalogued systems, one council, one standard applied across all of it. Tonight was one room in that house. If tonight was useful, the deeper version — the actual rules, the actual prompts, the actual review protocol — is what the masterclass is for. It's at obaisukar.com.

Before We Wrap

Tonight Was the Quick Version

One idea, pushed through sound, image and motion — plus a live look at what breaks and what to check before you trust a result. That local AI system I mentioned earlier? One piece of a much bigger practice.

Build your council

Structuring AI advisors that actually check each other.

Claude Code sessions

Real setup — rules, memory, how a working session runs.

Rules & lessons learned

The best practices, and the mistakes that were expensive.

The tool stack

The many AI tools, local and cloud, actually in use.

That's the masterclass. Tonight was one room in the house.

[Presenter reminder: this is the explicit recap + syllabus moment. Today is a session, not the masterclass — say that plainly. List what the masterclass covers at the WHAT level only (these four lines), don't start teaching any of them now.] Quick recap before we close. Tonight was the fast version: one idea, pushed all the way through sound, image and motion, with an honest look at where it breaks and what I actually check before I trust a result. Tonight was not the masterclass — it's the intro. If you want the deeper version, that's a separate session, and it's structured around four things: building your own council of advisors, setting up real working sessions in Claude Code, the rules and best practices behind all of it, and hands-on time with the actual tools — local and cloud — including that local AI setup I mentioned earlier.

Closing

AI Speeds Up the Work

Vision and signature stay human.

Thank you — let's open the floor for questions.

Obai Sukar — Co-Founder at NHJ · obaisukar.com
techtown. × aiSalon — Sunday, August 2, 2026 — Damascus

BEFORE YOU GOShow your favorite result from tonight to someone near you — and say what you'd change next.

One Last Thing

Tell Me What Landed

Two minutes. Shapes the next session — and if you opt in, how I follow up with you.

Scan to leave feedback

FROM IDEATO RESULT

If you don't know how to usesomething — ask AI.

If you don't know how to ask AI —ask AI.

Twenty-Five Years, Then Two With AI

Ten Things About AI — Part One

Ten Things About AI — Part Two

I Stopped Managing Tools. I Started Managing a Team.

Most of This Runs on My Own Machines

What has actually changed?

Four Real Shifts

Does AI create the idea?

The Tool Executes What You Can Describe — and Judge

Creativity Is a Loop, Not a Flash

The Council: A System of Roles, Not One Answer

Seven Real Seats, Each With a Veto

How many questions do I ask before accepting a result?

AI Is a Drilling Tool, Not an Oracle

Where do we start — the tool, or the idea?

First — Write the Scenario

What separates describing a mood from a musical decision?

Clear Words, Missing Decisions

The Knowledge That Makes the Difference

Turning Knowledge into Executable Instructions

Now — Try It in Suno

Music's Done — Image and Motion Next

What separates describing a mood from a visual decision?

Clear Words, Missing Decisions

The Knowledge That Makes the Difference

Turning Knowledge into an Executable Prompt

Now — Make the Image

What separates describing a mood from a motion decision?

Clear Words, Missing Decisions

The Knowledge That Makes the Difference

Turning Knowledge into Executable Instructions

Now — Animate It

When does the result become an extension of my vision?

More Decisions, Less Chance

What did my mistakes teach me?

Four Mistakes That Built My System

The Real Production Pipeline

Can we build a new project in front of you — right now?

The Live Project

What Will We Fix When the Version Fails?

Six Ideas I Want You to Keep

This Pipeline Already Shipped

Tonight Was the Quick Version

AI Speeds Up the Work

Tell Me What Landed

FROM IDEA
TO RESULT

If you don't know how to use
something — ask AI.

If you don't know how to ask AI —
ask AI.