sprezzature-video

🇫🇷 LISEZMOI.md · 🇬🇧 README.md

A film about a project makes claims about that project — how many chart kinds, how many tests, how many packages — and burns them into pixels, where nothing ever reads them again. Prose in a README gets re-read. A number in a keyframe does not.

So this package is not a renderer. Its centre is a checker that holds a film's assertions against the code they describe, in both directions, and the renderer sits behind a seam because which tool grabs the frames is the least interesting decision here.

Part of the sprezzature suite.

Why it exists

The five films that served on sprezzature.ai said "127 chart kinds". The catalogue had held 167 since September. The number was baked into ten compositions and five rendered MP4s, so nothing short of a re-cut could correct it — and nothing, anywhere, was watching. That is this package's whole subject.

What's here

Both directions, and why the second one matters

from sprezzature_video import Claim, ClaimSource, verify, undeclared_numbers

claim = Claim(
    text="167 kinds, every one hand-authored.",
    value=167,
    source=ClaimSource(
        path="sprezzature-figures/sprezzature_figures/catalog/figures.json",
        method="json_len",
    ),
)
verify(claim, root).ok  # does the code still agree?
undeclared_numbers(html, [claim])  # is anything on screen unaccounted for?

Checking only declared claims protects the numbers somebody remembered to declare — never the one typed into a keyframe at midnight and left to go stale.

Install

pip install sprezzature-video                    # the checker and the ledger
pip install 'sprezzature-video[voice,post]'      # plus narration and ffmpeg work

Boundaries

Which package owns what, between this suite and ai-helpers, is written down in BOUNDARIES.md. The short version: ai-helpers owns the primitive, sprezzature owns the opinion. Voice arrives through sprezzature-audio[narrate], ffmpeg through video-helper, and rendering through Hyperframes behind a seam.

Status

0.2.0. The checker, the asset ledger, the captions, the post-processing, the YAML spec loader and all five surfaces are written and tested — 46 tests, with CI on 3.10/3.11/3.12. The renderer seam is still out of band: Hyperframes is driven directly, and renderers/ returns in the commit that gives it a module.

License

BSD-3-Clause.