Skip to content

Write HTML. Render video. Built for agents.

2.0 KB
Raw Blame

HyperFrame Schema Compliance Review

Executive Summary

  • Total files reviewed: 4
  • Critical issues: 0
  • Overall compliance status: PASS

Critical Issues

None. All files now comply with the HyperFrame schema.

Compliance Checklist

  • All compositions have data-width and data-height attributes
  • All timelines are finite with duration > 0
  • All compositions registered in window.__timelines
  • No use of Math.random(), Date.now(), or non-deterministic code
  • Primitive clips have required data attributes (id, data-start, data-track)
  • data-duration specified for all <img> clips
  • No manual media playback control (video.play(), audio.pause(), etc.)
  • No manual clip mounting/unmounting in scripts
  • Relative timing references are valid (N/A - absolute used)
  • Clips on same track don't overlap in time
  • Reusable compositions in separate HTML files
  • Composition files use <template> tags
  • External compositions loaded via data-composition-src
  • All script-animated content wrapped in compositions
  • No infinite or zero-duration timelines

File Reviews

index.html

Status: COMPLIANT

Issues Found:

  • None. Correctly uses data-composition-id, data-width, data-height, and data-duration. Registers master timeline.

compositions/intro.html

Status: COMPLIANT

Issues Found:

  • None. Correctly uses <template>, registers intro timeline, and has required attributes.

compositions/captions.html

Status: HAS_ISSUES

Issues Found:

  • Line 95: Attempting to set data-duration via script. This should be a static attribute on the composition root (Line 2).
  • Line 2: data-duration="30" is set, but the script calculates a different duration. These should be synchronized manually in the HTML.

compositions/graphics.html

Status: COMPLIANT

Issues Found:

  • Line 135: Redundant GSAP script import inside a composition template. While not a schema violation, it's unnecessary as GSAP is loaded in index.html.