@aicopycoders/exodus 2026.11.1100-beta.3 → 2026.11.1100-beta.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: exodus-video
3
- description: Make a video ad with Exodus from the terminal. One sentence ("swipe this ad as a microdrama for my brand", "make this a UGC video") is walked through the template door stop by stop, with a yes asked before each paid step. A competitor's video ad (a file, a link, or an ad in Exodus) is swiped with `exodus video swipe`, as Swipe a video does on the dashboard: broken down, matched to a kind of ad, written for the brand and started, a yes before each paid step. The main path is script-first: run a saved video workflow with `npx @aicopycoders/exodus workflow run`. You read and approve the storyboard, pull every finished piece (per-scene clips, the narration track and per-scene voice, keyframes, cast identity stills, word timings, the music bed) into a folder with `exodus video pull`, and upload a finished cut for approval. Exodus makes the pieces; the cut is made outside it, in whatever editor the user wants — this skill hands over the pieces and the facts about them, it does not prescribe an editor. Use it whenever the user has invoked Exodus and wants anything to do with a video ad, an ad run's clips or storyboard, "pull the pieces", "stitch it together", "make the cut", "upload my cut", or checking on a video run ("exodus, make a video ad from this script", "exodus, is my video run done", "exodus, pull the clips for run X and cut them", "exodus, what's wrong with scene 3", "exodus video status"). Also use it when the user ran an `npx @aicopycoders/exodus video` command or the `exodus` hub skill routed here. Admins get every video command; beta testers with video switched on get start, swipe, status, storyboard, approve, voices, retry-frame, pull and upload on their own brands (see "Beta testers"). "video isn't enabled for this key" means the run id is wrong, the command is admin-only, or video isn't switched on for that dashboard user, so check the id and then say so; do not retry. Never claim generic video-editing asks ("edit this mp4", "add captions to my reel") without Exodus context; in shared folders those belong to the user's other tools. Running or authoring workflows generally is `exodus-workflow`; static image ads are `exodus-image`; copy is `exodus-write`.
3
+ description: Make a video ad with Exodus from the terminal. One sentence ("swipe this ad as a microdrama for my brand", "make this a UGC video") is walked through the template door stop by stop, with a yes asked before each paid step. A competitor's video ad (a file, a link, or an ad in Exodus) is swiped with `exodus video swipe`, as Swipe a video does on the dashboard: broken down, matched to a kind of ad, read first, then one sheet of choices and one yes for the write and the whole video (or, when the member asks, step by step with a yes before each paid step). The main path is script-first: run a saved video workflow with `npx @aicopycoders/exodus workflow run`. You read and approve the storyboard, pull every finished piece (per-scene clips, the narration track and per-scene voice, keyframes, cast identity stills, word timings, the music bed) into a folder with `exodus video pull`, and upload a finished cut for approval. Exodus makes the pieces; the cut is made outside it, in whatever editor the user wants — this skill hands over the pieces and the facts about them, it does not prescribe an editor. Use it whenever the user has invoked Exodus and wants anything to do with a video ad, an ad run's clips or storyboard, "pull the pieces", "stitch it together", "make the cut", "upload my cut", or checking on a video run ("exodus, make a video ad from this script", "exodus, is my video run done", "exodus, pull the clips for run X and cut them", "exodus, what's wrong with scene 3", "exodus video status"). Also use it when the user ran an `npx @aicopycoders/exodus video` command or the `exodus` hub skill routed here. Admins get every video command; beta testers with video switched on get start, swipe, status, storyboard, approve, voices, retry-frame, pull and upload on their own brands (see "Beta testers"). "video isn't enabled for this key" means the run id is wrong, the command is admin-only, or video isn't switched on for that dashboard user, so check the id and then say so; do not retry. Never claim generic video-editing asks ("edit this mp4", "add captions to my reel") without Exodus context; in shared folders those belong to the user's other tools. Running or authoring workflows generally is `exodus-workflow`; static image ads are `exodus-image`; copy is `exodus-write`.
4
4
  ---
5
5
 
6
6
  # Video: make the pieces, cut the ad, hand it back
@@ -320,7 +320,7 @@ What Swipe a video does on the dashboard, from the terminal. Exodus breaks the
320
320
  competitor's ad down, matches it to the closest kind of ad and look it makes
321
321
  (the template), writes the brand's version, and starts the video on the kind
322
322
  the swipe wrote. The run is the same one Swipe a video starts on the
323
- dashboard, Guided unless the member asks for `--one-shot`.
323
+ dashboard.
324
324
 
325
325
  These steps need Video switched on for the member's account. Without it every
326
326
  swipe command answers "Not found on this brand. The id is wrong or is another
@@ -331,13 +331,409 @@ them, and stop.
331
331
 
332
332
  This path has no picks stop and no pilot clip. The run goes from the start
333
333
  straight to the storyboard (stop 3), and approving the storyboard makes every
334
- clip. Making the video from one of our formats (`--adapt`, "From one sentence
335
- to a film") keeps the picks stop and the pilot clip.
334
+ clip. A run started with `--one-shot` approves its own storyboard when its
335
+ checks pass. Making the video from one of our formats (`--adapt`, "From one
336
+ sentence to a film") keeps the picks stop and the pilot clip.
337
+
338
+ By default a swipe is one round: you read the ad, send the member one sheet,
339
+ and on their one yes write the brand's version and make each video they
340
+ picked. A member who asks to say yes before each paid step gets "Step by
341
+ step" below.
342
+
343
+ **Long waits.** The CLI waits up to 25 minutes for a breakdown, 10 for a
344
+ template, 15 for a write (the write always waits; it has no `--wait`), and 60
345
+ for `swipe start --wait`. Run these in the background, or leave `--wait` off
346
+ and check in, so the shell's own time limit does not cut them off. A wait that
347
+ was cut off or timed out is not a failure: the work goes on. Follow it by the
348
+ id it printed, with the command the CLI names, and never by running the paid
349
+ line again: a second run buys it a second time.
350
+
351
+ ### 1. Read the ad
352
+
353
+ First, free: `exodus video swipe products`. When it answers "This brand has
354
+ no products yet. Add one in the dashboard first.", tell the member and stop
355
+ before any read.
356
+
357
+ **Reading the ad, without asking.** Read each ad the member named before the
358
+ sheet, and only those. Say so in one line, in words like: "I read the ad
359
+ first; that costs a little, on the team's keys and on your model key." Then:
360
+ `exodus video swipe --file <ad.mp4> | --url <link> | --ad <swipeAdId> --yes --wait`
361
+ (the breakdown, on the team's keys), `exodus video swipe status <breakdownId>
362
+ --full` (what it read: each shot, the script with who says each line, the
363
+ cast; free), and `exodus video swipe template <breakdownId> --yes` (the kind
364
+ of ad and look it matched; one model call on the member's own Anthropic or
365
+ OpenRouter key). The CLI's next lines say "ask first": here the one line
366
+ above covers the read, and the sheet's yes covers the writes and the starts.
367
+ When the breakdown prints "Still reading after 25 minutes", it is not done:
368
+ wait once more with `exodus video swipe status <breakdownId> --wait`, and if
369
+ it is still reading, stop and tell the member.
370
+
371
+ **The limit: $0.50 for the read.** The CLI prints no price before a read, so
372
+ keep to the limit with what it prints after. Count each breakdown once, from
373
+ the lines it ends with: those of the `exodus video swipe --file | --url |
374
+ --ad … --wait` command, or, when that wait was cut off, those of `exodus
375
+ video swipe status <breakdownId>` once it says the breakdown is done:
376
+
377
+ - "It cost $…, on the team's keys." is that breakdown's cost. Part of it may
378
+ be an estimate: "It cost $… (partly an estimate), on the team's keys."
379
+ - A first line "This ad already has a breakdown: <id>. It cost nothing." is
380
+ zero, even when a later line repeats what it cost the first time. "It
381
+ reused answers bought before, so it cost nothing." is zero too.
382
+ - No cost line at all is unknown.
383
+
384
+ Every later `exodus video swipe status <breakdownId>` repeats the cost: count
385
+ it once only. The template is the member's own money in the read, and its cost is
386
+ never printed: "This template was already made, so it cost nothing." is
387
+ zero, and a new template is unknown.
388
+
389
+ Read one ad at a time: its breakdown, then its template. Before each read
390
+ after the first (a template, or the next ad's breakdown), stop and ask the
391
+ member once when the costs counted have reached $0.50, or when any read so
392
+ far is unknown: an unknown cost counts as reaching the limit. Say what is
393
+ left to read. A new template is always
394
+ unknown, so with several ads you read the first and ask before the rest. The
395
+ check comes before each read, so the total can pass $0.50 by one read.
396
+
397
+ A breakdown or a template that fails prints why. With one ad, tell the
398
+ member and stop. With several, leave that ad out, say so in the sheet's first
399
+ line, and go on with the others. Reading again is paid too, and needs their
400
+ yes.
401
+
402
+ ### 2. Read the choices
403
+
404
+ Free, and no yes: `exodus segment personas` (the saved personas; leave out
405
+ the ones marked `[archived]`) and `exodus primer show` (its MECHANISM
406
+ section; with no primer saved, say so once and offer only the member's own
407
+ words or none). The products came in step 1.
408
+
409
+ ### 3. The sheet, once
410
+
411
+ Send this in one message, in this order, then stop and wait:
412
+
413
+ > I read your ad as <kind of ad>, <look>, <n> lines, about <s> s. The swipe
414
+ > makes that kind of ad. Say "show me" for the shot list and the script.
415
+ > One sheet, answer once (my picks are marked):
416
+ > 0. **Let it run** (I pick every row) or **I choose**.
417
+ > 1. **Persona** (noted; the video writer does not read it yet): <your three best fits, each with a short reason>, show all <N>, or none. Pick several for one video each.
418
+ > 2. **Mechanism** (noted; the video writer does not read it yet): <the primer's mechanisms>, your own words, or none.
419
+ > 3. **How close:** 1 Mirror, 2 Close, 3 Same beats, 4 Same arc, 5 Pattern only.
420
+ > 4. **Characters:** the tool picks them (your saved characters: not yet).
421
+ > 5. **Run:** one shot, or stop at the storyboard.
422
+ > 6. **Finish:** music on or off (captions, speed, cuts: not yet).
423
+ > **How many:** <n> videos = <a> ads × <p> personas:
424
+ > - Video 1: <ad> × <persona>
425
+ > - Video 2: <ad> × <persona>
426
+ > **Cost:** the CLI prints no price for a swipe.
427
+ > **My picks:** <one line, with the reason>. **It buys:** <n> scripts and <n>
428
+ > whole videos, on your keys. Say go, or change a row. (Above 6 videos, end
429
+ > with "Say yes to <n> videos, or change a row." instead.)
430
+
431
+ **The yes covers only the list the member last saw.** Before any write or
432
+ start, the member has seen the list and the count, and said yes to them.
433
+ This holds also when their first message says "just do it" or "let it run":
434
+ "Let it run" fills the rows with your picks, and the yes still comes from
435
+ the member.
336
436
 
337
- Four steps cost money, and the CLI prints no price for any of them. Run each
338
- one first without `--yes`: it sends nothing and prints what the step buys and
339
- who pays. Tell the member both, say the CLI prints no price, never guess one,
340
- and run the same line with `--yes` only after their yes.
437
+ - A reply that makes the buy bigger is not the yes, even with "go" in it:
438
+ more videos, another ad, music on where the sheet said off, or "one shot"
439
+ where the sheet said "stop at the storyboard". Send the new list and count,
440
+ and wait.
441
+ - A reply that changes a row without making the buy bigger, together with
442
+ "go", is the yes: how close, music off, or leaving out videos it names
443
+ ("drop video 3, go"). Say the change in one line and start. "Fewer" with
444
+ no say in which ones is not the yes: send the shorter list and wait.
445
+ - Anything else is not the yes: a question, "show me", "maybe", "looks
446
+ good?", or a reply you are not sure of. Answer it and wait. Above 6 videos,
447
+ only a yes that names the count is the yes ("yes to 8 videos", "8, go"); a
448
+ bare "go" or "yes" gets the count asked again.
449
+ - On a sheet of 1 video, "1: Anna, Ben and Cara. Go." is 3 videos: send the
450
+ list of 3 and wait.
451
+
452
+ The rows:
453
+
454
+ - **The kind of ad.** The swipe writes the kind the template read and no
455
+ other. When the member asks for another kind ("make it UGC instead"),
456
+ leave this path for "From one sentence to a film", with the ad's words
457
+ from `status --full`.
458
+ - **Persona.** Offer the three saved personas that fit the ad best, each with
459
+ a short reason, then "show all <N>" (every persona not marked
460
+ `[archived]`). Several may be picked: one video for each.
461
+ - **Persona and mechanism.** The video writer reads neither. When step 5's
462
+ path is open, the text swipe bot writes them into each video's lines, and
463
+ the rows say so (step 5). When it is closed, and for a video the bot does
464
+ not write, they are noted, not read: in
465
+ **My picks**, a persona or a mechanism always carries "(noted, not used
466
+ yet)", the primer's lead mechanism included, and videos for two personas
467
+ differ only as two writes of the same request differ. In that case, when
468
+ more than one persona is picked, say this in your reply before the yes, so
469
+ the member does not pay for several videos expecting a script for each
470
+ persona. Two other ways make a persona real without step 5. The member
471
+ writes their own script for that persona, and the write takes it with
472
+ `--mode their-format --script <file>`, made the way their ad is made. Or
473
+ the member swipes the words with the `swipe` skill and makes the film from
474
+ one of our formats (its "Make it a video"). That path asks a yes before
475
+ each paid step, and it makes the film in the format they pick, not in the
476
+ ad's own kind and look.
477
+ - **Characters.** A swiped run takes no saved characters and draws no new
478
+ faces yet, so the row offers only "the tool picks".
479
+ - **Run.** With "stop at the storyboard", the line reads **It buys:** <n>
480
+ scripts, and <n> storyboards with their pictures; the voices and clips
481
+ wait for your yes at each storyboard.
482
+ - **Finish.** `swipe start` takes `--music` and nothing else for the finish.
483
+ Music is made on the member's own ElevenLabs key. Caption style, speed,
484
+ jump cuts and the end card come with a later update.
485
+ - **How many.** Ads × personas, with none counting as one persona and the
486
+ characters counting as one today. Show the multiplication, as in "4 videos
487
+ = 2 ads × 2 personas". Above 6 videos, say the count and ask for the yes on
488
+ that count in so many words: "That is 8 videos. Say yes to 8 videos."
489
+ - **Cost.** The CLI prints no price for a swipe, so the sheet says exactly
490
+ that: no number, no range, no guess. The Director block of `exodus video
491
+ status` prints "Spent: $… of $12.00": the $12.00 is the Director's limit
492
+ for its redos on that video, not a price and not a ceiling for the first
493
+ pass. Never quote it as the cost.
494
+ - **Product.** Add a row **Product:** only when `swipe products` lists more
495
+ than one. With one, write for that one.
496
+ - **Anything else.** Add a row only when the member's ask carried a note. A
497
+ note that names what to swipe (hook only, their format with their own
498
+ script, a new look) sets `--mode` (step 4), and **My picks** says the mode
499
+ back. Say back any other note as noted, not used yet.
500
+ - **Several ads.** One sheet covers every ad the member named: list what you
501
+ read from each in the first line. The count and the warning above 6 hold.
502
+
503
+ **The videos, in a fixed order.** List them one per line: the ads in the
504
+ order the member gave them, and for each ad the personas in the order the
505
+ sheet shows them. The same picks give the same list.
506
+
507
+ **A bare number.** Read a reply of only a number ("3") as the count of
508
+ videos, and say so in the list's first line: "I read 3 as 3 videos." Pick
509
+ one video for each ad, in the order given, before a second persona for any
510
+ ad; then the next persona in the order shown for each ad, and so on, until
511
+ the count is reached. List the videos in the fixed order and wait for the
512
+ yes. When the picks cannot make that many, say how many they can make.
513
+
514
+ When the member says "just do it": no persona, the primer's lead mechanism
515
+ (noted, not used yet), closeness 2, the tool picks the characters, one shot,
516
+ no music. With more than one product and none named, ask that one row first.
517
+
518
+ ### 4. On the yes
519
+
520
+ The yes covers the writes and the starts, and the bot calls when step 5
521
+ applies; nothing else. The breakdown and the template are once per ad, and
522
+ are done already. For each video, in the listed order, run steps 1 and 2;
523
+ step 3 comes once every video has started:
524
+
525
+ 1. `exodus video swipe write <breakdownId> --product <id> --mode whole-ad
526
+ --closeness <n> --yes`. A mode set from a note changes the line:
527
+ `hook-only` takes `--closeness` as `whole-ad` does. `their-format` takes
528
+ the member's own script: save it to a file and pass `--script <file>`,
529
+ with no `--closeness` (the CLI refuses one). `new-look` takes `--look
530
+ <slug>`; no command lists the looks a swipe can take, so ask the member
531
+ for the exact look name and never invent one (the writer refuses a look
532
+ it does not make). When step 5 applies, its write line takes the place of
533
+ this one. The write takes four to nine minutes. Show the member the
534
+ script, the direction, Kept and Changed, and what it cost. When a persona
535
+ or a mechanism was picked and step 5 does not apply, add one line: "The
536
+ persona and the mechanism are noted, not used: the video writer does not
537
+ read them yet."
538
+ The write's last line says "Start the video (paid; ask first)": the
539
+ sheet's yes was that ask, so start now, with the line below, not the
540
+ write's own, which leaves out `--one-shot`. Note the swipe id it printed
541
+ for that video.
542
+ 2. `exodus video swipe start <swipeId> --one-shot --yes`, without
543
+ `--one-shot` when the member chose to stop at the storyboard, and with
544
+ `--music` when they chose music. Give the member the `Watch it:` link at
545
+ once. Then go on to the next video.
546
+ 3. When every video has started, follow each run with `exodus video status
547
+ <runId>` and do what it prints. A one-shot run that waits for a cut goes
548
+ to "End: watch and approve" (pull, cut, upload, the run page). A run that
549
+ stopped at the storyboard goes to stop 3, then the end.
550
+
551
+ **Never start the same swipe twice.** Each start is a second, paid video.
552
+ Before any second start of a swipe, run `exodus video swipe show <swipeId>`:
553
+ when it prints "It started run <runId>", the run started, so follow it with
554
+ `exodus video status <runId>`. Before writing again after a write whose wait
555
+ was cut off, run `exodus video swipe list`. It lists the newest first, and
556
+ the writes run one at a time, so a row for that ad above the last swipe id
557
+ you noted (any row for it, when you noted none), with no run and not marked
558
+ refused, is that write. Show it with `exodus video swipe show <swipeId>` and
559
+ start it instead of writing again. A row marked refused is that write's
560
+ refusal: report it as a refused write. When no such row is there yet, the write may
561
+ still finish: check again later.
562
+
563
+ At the end, report each video on one line: its ad and persona, its run id
564
+ and its `Watch it:` link, or why it stopped.
565
+
566
+ **The final approve** is asked for each video as at "End: watch and
567
+ approve". It is one way. A redo of a clip there needs its own yes.
568
+
569
+ **A refusal or a failed check stops that video only.** The others go on, and
570
+ every video is in the report at the end. A refused write prints the writer's
571
+ sentence, its swipe id, what it cost, and "Nothing was started.": report all
572
+ of it for that video. Writing again is paid again and needs the member's
573
+ word. A refused start prints its sentence: report it for that video. A
574
+ one-shot run whose checks find a problem stops for the member: show what
575
+ `status` prints and ask.
576
+
577
+ ### 5. With a persona or a mechanism: the text swipe bot
578
+
579
+ The video writer reads no persona and no mechanism. The `swipe` skill's bot
580
+ does: it writes the ad's lines again with them in, and the write then makes
581
+ those lines the way their ad is made.
582
+
583
+ **When the path is open.** Before the sheet, check these three, all free:
584
+
585
+ - `.claude/skills/genesis-bots/scripts/genesis-stream.mjs` is in the folder.
586
+ - `exodus keys status` (it prints key names, never values) shows
587
+ `GENESIS_API_KEY`, and `ANTHROPIC_API_KEY` or `OPENROUTER_API_KEY`, as
588
+ "local ✓". When it cannot reach the dashboard, this does not hold.
589
+ - `grep -l '^GENESIS_BASE_URL=' .env .claude/skills/genesis-bots/.env`, run
590
+ in the folder that holds `.claude/`, names at least one file. It prints
591
+ file names only, never a value. The helper needs this address, and
592
+ `exodus keys status` does not show it.
593
+
594
+ When one does not hold, the path is closed and everything stays as above:
595
+ the rows keep "(noted; the video writer does not read it yet)" and every
596
+ write is the one "On the yes" gives.
597
+
598
+ **Which videos take it.** With the path open, the bot writes a video's lines
599
+ when all three hold for that video, and "step 5 applies" means that video:
600
+
601
+ - The member picked a persona for it, or a mechanism. The primer's lead
602
+ mechanism that "just do it" picks stays noted only.
603
+ - How close is 1, 2 or 3.
604
+ - The write would be `--mode whole-ad`. A note that sets `hook-only`,
605
+ `their-format` or `new-look` keeps that write, and the persona and the
606
+ mechanism stay noted only: the bot never takes the place of the member's
607
+ own script.
608
+
609
+ Every other video is made as "On the yes" says, with the persona and the
610
+ mechanism noted only.
611
+
612
+ **On the sheet, when the path is open.**
613
+
614
+ - Rows 1 and 2 read "(used through the text swipe bot)" in place of
615
+ "(noted; …)".
616
+ - Row 3 reads "1 Near-clone, 2 New scene, same beats, 3 Same idea, new
617
+ drama, 4 Same arc, 5 Pattern only (with 4 or 5, the persona and the
618
+ mechanism are only noted)". Levels 1 to 3 are the `swipe` skill's levels
619
+ (its section 2), not the dial's: say so when the member asks. A video the
620
+ bot does not write takes the same number as its `--closeness`.
621
+ - **It buys** adds, when the picks give the bot any video: "and a text swipe
622
+ call for each video (two at level 2 or 3), on your own Genesis and model
623
+ keys." When only some videos take it, name them ("for videos 1 and 3").
624
+ - A reply that adds bot calls makes the buy bigger, so it is not the yes: a
625
+ persona or a mechanism added where the sheet had none, or, while a persona
626
+ or a mechanism is picked, how close moved from 1 to 2 or 3, or from 4 or 5
627
+ to 1, 2 or 3. A reply that moves how close to 4 or 5 while a persona or a
628
+ mechanism is picked is not the yes either: say that they will then be only
629
+ noted, and wait. One persona changed for another, with the same count, is
630
+ not a bigger buy.
631
+
632
+ **For each video the bot writes, on the yes:**
633
+
634
+ 1. The ad's lines: the Script part of `exodus video swipe status
635
+ <breakdownId> --full` (free), with who says each line. Keep each video's
636
+ files in a folder of its own, `swipes/<slug>/video-<n>/`, so no video
637
+ reads another's lines, and save the options answer as `options.md`, apart
638
+ from the lines.
639
+ 2. The PRODUCT block, built as the `swipe` skill's section 3 says, with that
640
+ video's persona and the mechanism. Begin it with the line `exodus video
641
+ swipe products` prints for the product being written (its name and
642
+ description).
643
+ 3. The bot, called as the `swipe` skill's section 4 says, with LEVEL from
644
+ row 3, one stream at a time, under that skill's "Security" rules. At level
645
+ 2 or 3 its options call comes first; its options are short scenes, one
646
+ line each. The one round has no stop for the pick: take option 1 and send
647
+ its full SCENE text, as section 4 says. Section 4's retries and section
648
+ 5's count and FIX call are each another paid call, and are not part of
649
+ this path. Run the helper so the shell's own time limit cannot cut it off
650
+ (a long timeout, or in the background), and wait for its "Done:" line or
651
+ its error.
652
+ 4. Save the bot's lines to a file, each line with its speaker label exactly
653
+ as the bot wrote it ("Alex: …"). Drop blank lines, a line "---", and a
654
+ first line that starts "Value mismatch —". When that first line comes,
655
+ tell the member in one sentence: it says why the scene and the product do
656
+ not fit, and may name a better level.
657
+ 5. `exodus video swipe write <breakdownId> --product <id> --mode their-format --script <file> --yes`.
658
+ No `--closeness`: the CLI refuses it with `their-format`, and the bot's
659
+ LEVEL carried the closeness. The write keeps each line word for word, and
660
+ its cast follows the file's speakers.
661
+ 6. The check below, then the start, as "On the yes" does.
662
+
663
+ At level 2 the bot may give the lines to a new speaker named after the
664
+ persona, in place of the ad's own; the cast follows the script. Say so in
665
+ one line of the report for that video. For an ad with one speaker it still
666
+ wrote one speaker, even when its options had several people in them.
667
+
668
+ **The check is yours.** The write keeps the script's lines as they are and
669
+ checks none of their claims, so after each write and before its start, read
670
+ every line of the script it prints, and its Direction, against (1) that
671
+ video's persona, when one was picked, (2) the mechanism, when one was
672
+ picked, and (3) the product's own facts. The facts are only these: the line
673
+ `exodus video swipe products` prints for that product, and the product
674
+ facts in the PRODUCT block you sent for that video. Never the ad's own
675
+ claims (they were made for another product), and never the bot's. A picked
676
+ mechanism's own words count as a fact for a line that says only what they
677
+ say; a result beyond them needs a product fact.
678
+
679
+ - The persona is in when the lines speak as that person or to them (their
680
+ situation, what they want). The mechanism is in when the lines name it or
681
+ explain it.
682
+ - A line holds only when one of those facts says the same thing. A line that
683
+ goes further does not hold: a result the facts do not name, a bigger
684
+ number, a shorter time, "cures" where the facts say "helps". When you are
685
+ not sure, it does not hold.
686
+ - Each of these needs a fact that says it: a health or body result (sleep,
687
+ pain, weight, energy, skin, treating or curing anything), a money result
688
+ (earning, saving), a guarantee or a refund, any number (a percent, a time,
689
+ a count, a price, a rating, how many customers), and a named result (a
690
+ named person's result, a review, a doctor or an expert, a study, an award,
691
+ "the #1").
692
+
693
+ When a picked persona or mechanism is missing, or a line promises something
694
+ the product's facts do not hold (a result, a health benefit, a number), do
695
+ not start that video: show the member that line and ask. The other videos go
696
+ on. Show each such line with the fact it would need, and offer three ways
697
+ on: start it as written, leave that video out, or the member's own words for
698
+ those lines, written again with `--mode their-format --script <file>` (a
699
+ second paid write, on their word) and checked again. This is the one stop
700
+ this path adds, and it comes only when the check finds something. The write
701
+ may still refuse a name, price or code from their ad, or a cast the kind of
702
+ ad cannot take (more speakers than it holds, or speakers where it takes a
703
+ narrator only): a refused write stops that video only, as above. A write
704
+ whose wait was cut off and is found again with `exodus video swipe show
705
+ <swipeId>` (as "On the yes" says) gets this check too, on the script `show`
706
+ prints, before its start.
707
+
708
+ **Run so far.** Levels 1 and 2 of this path have been run for real, as far
709
+ as the write. Level 3 has not.
710
+
711
+ **A bot call that fails** (the helper prints an error, or "stream completed
712
+ but produced no content") stops that video only. Report it. Calling the bot
713
+ again is paid again and needs the member's word, even when the helper's own
714
+ error says "retry". Never use the partial lines a failed call leaves in its
715
+ file. These count as failed calls too: a "Done:" line with
716
+ `finish_reason=length`, which means the lines were cut short; an answer with
717
+ no speaker lines in it; and a call the shell cut off before "Done:" or an
718
+ error, which may have been paid all the same.
719
+
720
+ Some failures stop every video the same way. The helper stops before it
721
+ sends anything, and charges nothing, with "ERROR: GENESIS_BASE_URL is not
722
+ set", "ERROR: GENESIS_API_KEY is not set" or "ERROR: no provider key found".
723
+ A wrong model key prints `ERROR: provider_error: 401 …` and charges nothing.
724
+ A Genesis key it refuses, a limit reached or a server fault prints `ERROR:
725
+ HTTP 401`, `HTTP 429` or `HTTP 5…`. On one of these, make no further bot
726
+ call. Tell the member what went wrong, and ask whether to fix it and go on,
727
+ or to make the rest as "On the yes" says, with the persona and the mechanism
728
+ noted only.
729
+
730
+ ### Step by step: a yes before each paid step
731
+
732
+ For a member who asks for stops. Four steps cost money, and the CLI prints no
733
+ price for any of them. Run each one first without `--yes`: it sends nothing
734
+ and prints what the step buys and who pays. Tell the member both, say the CLI
735
+ prints no price, never guess one, and run the same line with `--yes` only
736
+ after their yes.
341
737
 
342
738
  1. **Get the ad.** One of a video file, a link (Meta Ad Library, TikTok,
343
739
  Instagram or YouTube), or an ad in the brand's swipe library by the `id:`
@@ -382,6 +778,8 @@ and run the same line with `--yes` only after their yes.
382
778
  member.
383
779
  6. **Then** stop 3 (the storyboard) and the end, as above.
384
780
 
781
+ ### Every swipe command
782
+
385
783
  ```operator-guide
386
784
  exodus video swipe --file <ad.mp4> | --url <link> | --ad <swipeAdId> [--yes] [--wait]
387
785
  break the ad down (team's keys); one read before costs nothing
@@ -395,6 +793,7 @@ exodus video swipe show <swipeId> one swipe again
395
793
  exodus video swipe list the brand's newest swipes; a refused one shows what it cost
396
794
  exodus video swipe start <swipeId> [--style <look>] [--title "<name>"] [--music] [--one-shot] [--yes] [--wait]
397
795
  start the run on the kind the swipe wrote
796
+ exodus video swipe run --sheet <file> [--status] [--persona <name>] [--yes] [--retry-refused] [--wait] every video of a sheet saved as a JSON file
398
797
  ```
399
798
 
400
799
  ## Before anything
@@ -431,7 +830,9 @@ CLI words it the way the run page does. On their own brands they can:
431
830
  file"). `--stop-at-script` prints that script and starts nothing.
432
831
  - `video status <runId>`: where the video is, in plain words (waiting in line,
433
832
  planning, drawing, storyboard ready for review, filming, ready with its link,
434
- or stopped and why). `--json` prints the server's answer as it came.
833
+ held for a scene they must make again or keep as it is on the video's page,
834
+ or stopped and why). `--json` prints the server's answer as it came; a held
835
+ video says `"stage": "failed"` with the held scenes in `cutHolds`.
435
836
  - `video storyboard <runId>`: each scene's line and picture, while the
436
837
  storyboard waits for review.
437
838
  - `video approve <runId>`: approves the storyboard. Nothing else.
@@ -668,7 +1069,12 @@ under it:
668
1069
  it instead (`stop.missingScenes` in `--json`) and approval is refused until
669
1070
  it has one. A scene whose picture the video service refused needs
670
1071
  `retry-frame --note` before `retry-clip`; the clip redo alone resends the
671
- refused picture.
1072
+ refused picture. On a video started from the dashboard, the app makes the
1073
+ cut itself; when a scene's clip still has a drawing fault after it was made
1074
+ again, the stop block says `Held:` and names the scene
1075
+ (`stop.heldScenes` in `--json`). No cut is made until each held scene is
1076
+ made again with `retry-clip`, or kept as it is on the video's page (the
1077
+ link it prints). Keeping the last one starts the cut.
672
1078
  - paused: a builder checkpoint neither video verb resolves —
673
1079
  `exodus workflow checkpoint <runId>` is the verb for that one.
674
1080
  - failed: `status` shows how far it got, and a `--wait` that was running exits
@@ -118,7 +118,7 @@ On "make this a video", hand over to the `exodus-video` skill's "From one senten
118
118
 
119
119
  From there the walkthrough runs as written: a yes before each paid step, with its price where the CLI prints one, and the user's own picks at each stop.
120
120
 
121
- A video ad to swipe as it is made, from its file, its link or its id in Exodus, skips this skill: it goes to the `exodus-video` skill's "Swiping a video ad".
121
+ A video ad to swipe as it is made, from its file, its link or its id in Exodus, skips this skill: it goes to the `exodus-video` skill's "Swiping a video ad": it reads the ad, asks one sheet (persona, mechanism, how close, characters, run, finish, and how many videos), and makes the videos on one yes. With a persona or a mechanism, and the keys this skill needs, it calls this skill's bot as sections 3 and 4 say, then makes the video from those lines.
122
122
 
123
123
  ## Security
124
124
 
@@ -42,7 +42,9 @@ export interface CustomerRun {
42
42
  canRetry: boolean;
43
43
  stopReason: CustomerStopReason | null;
44
44
  detailsPath: string | null;
45
+ cutHolds?: string[];
45
46
  }
47
+ export declare function customerCutHeld(run: CustomerRun): boolean;
46
48
  export interface ScriptTidied {
47
49
  setAside: string[];
48
50
  added: {
@@ -1,3 +1,14 @@
1
+ export function customerCutHeld(run) {
2
+ return (run.cutHolds?.length ?? 0) > 0;
3
+ }
4
+ function heldLines(holds, page) {
5
+ const one = holds.length === 1;
6
+ return [
7
+ `Held: the final video wasn't made yet. ${one ? "This scene needs" : "These scenes need"} you first:`,
8
+ ...holds.map((hold) => ` ${hold}`),
9
+ `${one ? "Make it again" : "Make each one again"}, or keep it as it is, on the video's page: ${page}`,
10
+ ];
11
+ }
1
12
  export function customerAnswer(data) {
2
13
  return typeof data === "object" && data !== null && data.view === "customer"
3
14
  ? data
@@ -98,7 +109,7 @@ export function customerStageLines(run, page) {
98
109
  `Download the pieces for your own cut: exodus video pull ${id} --out ./video-${id}`,
99
110
  ];
100
111
  case "failed":
101
- return stoppedLines(run, page);
112
+ return run.cutHolds?.length ? heldLines(run.cutHolds, page) : stoppedLines(run, page);
102
113
  case "cancelled":
103
114
  return ["This video was stopped."];
104
115
  }