Verification and limits
Project and exports
A separate copy of the downloadable project was installed with npm ci, then
type-checked and tested. The phase tests cover duration extension, invalid
ordering, oversized copy and isolation of sequence timing from content props.
The recording-alignment tests use synthetic fixtures and reject invalid tail
windows, overlaps and inadequate holds; no real recording was synchronized.
All thirteen individual compositions and the complete 1,500-frame / 50-second sequence were rendered in Remotion 4.0.520. Every actual MP4 was fully decoded and checked: 1280 × 720, 30/1 fps, H.264, yuv420p, BT.709 and one video stream with no audio. The default browser-install command also completed, followed by a short CLI render without a custom browser path. Remotion Studio launched and exposed all fourteen compositions.
Frame-oriented checks compare actual decoded exports, not only timeline data:
ChapterReturn: the task before and after the title remains the same.PunchCut: adjacent frames contain a substantial crop discontinuity.CameraPush: an intermediate frame differs from both endpoints.CaptionCut: the caption region remains unchanged within compression tolerance while the underlying shot changes substantially.ScrollMask: the header remains unchanged while the document moves.- Every export: first and last frames of the final hold differ by less than 0.2 mean RGB levels on a 0–255 scale. The sequence's ending comparison is exactly zero. This endpoint measurement is not an exhaustive frame-by-frame optical-flow or human-comprehension test.
The machine-readable export report records durations, frame counts, checksums, checkpoints and measured differences. Encoded bytes may vary across supported browser/OS versions; identical MP4 hashes are not required of another environment.
Source and site checks
Fourteen bounded source excerpts completed actual 1× browser playback, with presented-frame callbacks. The thirteen primary technique windows have 404 decoded consecutive frames in their native subsets; an additional recent film has 60. Annotated frames and written observations identify which exact cuts were visually confirmed. Decoded counts are not a claim that every film in the source inventory was watched frame by frame.
All eleven cited official film pages returned HTTP 200 and the expected video and OpenAI channel identity in a fresh metadata check. Their publication timestamps remain separate from the timestamp of that verification.
The initial chapter browser check passed ten mobile/desktop layouts, actual playback of every original export, phase seeking and decoded-frame stepping, plus a no-JavaScript handoff check. The final staged and deployed artifact checks are recorded separately; an initial draft check is not a live-release claim.
The release builder preserves the 3,886 pre-existing public files. Changes to the 119 existing HTML pages are restricted to an editing navigation entry and one playbook crosslink; removing those additions recovers each original hash. Existing assets, recipes, evidence and downloads remain byte-identical.
Remaining boundaries
The collection has 421 in-period uploads; only eleven have a new close inspection in this task. This is not an exhaustive editing census, a recovered OpenAI style specification, or evidence of current product capabilities. Source font files, authoring tools, exact easing, motion-blur settings, unedited waiting times and soundtrack timing are not recovered.
The examples use original neutral graphics. They do not reconstruct branded knot geometry or letter deletion, promise submission behavior absent from the inspected typing interval, or claim a geometric morph where source frames show a cut. Detailed differences are documented alongside every example.
Final presentation production still requires the actual recording, verified product captures, real manual playback calibration, a genuine ending buffer, agreed export settings and one consolidated storyboard/demo approval.