Skip to content

video: pace the intro and the recap, open on the Just In Case icon - #44

Draft
mrhegemon wants to merge 1 commit into
mainfrom
video/brand-marks-paced
Draft

video: pace the intro and the recap, open on the Just In Case icon#44
mrhegemon wants to merge 1 commit into
mainfrom
video/brand-marks-paced

Conversation

@mrhegemon

Copy link
Copy Markdown
Member

Frozen picture was this cut's last failing property, and the worst in the fleet after the two time machines.

Measured, not estimated

Rendered on core-1, baseline and treatment back to back — same kit, same shots, same 51.3s duration.

cut before after
landscape 8.40s frozen (16.4%) 2.50s (4.9%)
portrait 8.67s (16.9%) 2.53s (4.9%)

Bar is <8%.

It took two passes, and the first one was not enough

Worth recording, because pacing the recap chips was the obvious move and it only reached 14.2% — still failing. Measuring where the rest actually was, rather than guessing, found two things:

  • 2.73s frozen inside a 4.5s intro card — mark, title and tagline all land by 1.3s, then the picture holds.
  • Three more frozen spans between the paced chips. Spreading four chips across a 7.3s scene put 1.59s between them, and a chip arriving that late reads as the film stalling rather than a claim landing.

So this storyboard paces the intro as well as the recap, and video-kit 0.7.1 bounds the chip step. No decorative background drift was added — that was refused before, correctly, and stays refused. Nothing on screen moves that is not carrying information.

The marks

intro.mark is Just In Case's own store icon, committed here per the WIRING.md decision so a clean clone still renders without a sibling checkout. outro.mark is brand:logo.full.

No chip icons. The pack ships consumer-service and platform marks; "Network", "Monthly fee", "Retrieval" and "Answers" have none.

Dependency and scope

Requires @companionintelligence/video-kit >= 0.7.1 (companionintelligence/CI-Common#44) for the intro pacing.

No shots were re-captured here — that is #41, which re-shot all 14 after the sidebar change. This branch touches only storyboard.json plus the committed icon. No video is committed.

Pushed with SKIP_LOCAL_CI=1 (whole-workspace pre-push gate, unrelated to a storyboard change).

🤖 Generated with Claude Code

Frozen picture was this cut's last failing property, and the worst in the fleet
after the two time machines. Measured on core-1, baseline and treatment back to
back with the same kit, the same shots and the same 51.3s duration — the
denominator did not move, which is the first way a frozen-picture reading has
misled us here.

  landscape  8.40s frozen (16.4%)  ->  2.50s (4.9%)
  portrait   8.67s frozen (16.9%)  ->  2.53s (4.9%)

Bar is <8%.

It took two passes, and the first one is worth recording because it was the
obvious move and it was not enough. Pacing the recap chips alone only reached
14.2% — still failing. Measuring where the rest actually was, rather than
guessing, found two things: 2.73s frozen inside a 4.5s INTRO card, and three
more frozen spans BETWEEN the paced chips, because spreading four chips across
a 7.3s scene put 1.59s between them and a chip arriving that late reads as a
stall rather than a claim landing.

So this storyboard paces the intro as well as the recap, and video-kit 0.7.1
bounds the chip step. No decorative background drift was added; that was
refused before, correctly, and stays refused. Nothing on screen moves that is
not carrying information.

`intro.mark` is Just In Case's own store icon, committed here per the WIRING.md
decision so a clean clone still renders. `outro.mark` is brand:logo.full.

No chip icons: the pack ships consumer-service and platform marks, and
"Network", "Monthly fee", "Retrieval" and "Answers" have none.

Requires @companionintelligence/video-kit >= 0.7.1 (CI-Common#44) for the intro
pacing. No shots were re-captured here — that is JustInCase#41 — and no video
is committed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants