Vawe

Quality gates

The checks you can run by name, and the ones that advise.

A gate is a script in quality/gates/. Run one by name:

bin/vawe check                              # list the gates
bin/vawe check anim-traps films/<name>/page.html

The gates are: anim-traps, code-quality, dead-branch, doc-refs, impeccable, no-emdash, page-check, provenance, rule-length, seo-surface, site-build-check, skill-reach and threshold-provenance.

Checks advise. Only determinism and a missing waiver reason refuse. A rule broken for cause is declared in the page. See The page.

Gates for a film

anim-traps finds the traps of a seeked CSS or Web Animation that never throw an error: fill collisions, a missing end keyframe, var() in the animation shorthand, a selector that matches nothing, a delay past the end, one easing across three or more keyframes, and a later animation that overrides an earlier one. It also searches the source for a live clock and an unseeded Math.random. It reports. --strict turns a finding into a failing exit code. See When it looks wrong.

page-check measures what a rendered page film shows, so your eye judges only what a number cannot. The exit code is always 0. Findings include:

  • dead-stop: a fast move that stops within one frame
  • text-unreadable-hold: words that leave before they were still long enough to read
  • quiet-before-spectacle: the 0.4 s before <meta name="spectacle"> is not quiet
  • cue-not-heard, cue-onset-drift, sound-off-hit: audio cues that do not land
  • cut-off-beat, cut-off-reference: a cut early or late against the beat grid or the reference
  • text-low-contrast, text-clipped, font-fallback: text that is hard to read or in the wrong face
  • loop-seam: with <meta name="loop" content="true">, the last frame does not flow into the first

bin/vawe critique <page> runs it.

no-emdash scans for an em dash, which the project never allows.

Gates for the repo

code-quality, dead-branch, doc-refs, rule-length, seo-surface, site-build-check, skill-reach, provenance and threshold-provenance check the repository itself, not a film. A film author does not need them.

The order

While you write: bin/vawe dev <page>, then anim-traps. Then bin/vawe critique <page> in a fresh session. Before the final: bin/vawe ship <page> renders, checks the final and runs a fresh judge. A judge pass is never recorded by the author.

Green checks do not mean the film is good. Look at the frames. See Reading your film.

On this page