Repository navigation
Validate Mathieu replay and assemble MP4 through shared Kitchen - #2
Merged
Merged
Conversation
Collaborator
Author
|
Scope correction (user, 2026-10-21): Movie generation is one cross-project pipeline, not a separate Mathieu video feature or a reason to proliferate Mathieu PRs. Authoritative shared SUN assignment: FP #250 — WIGGLE-VIDEO-01. Preserve worthwhile manifest/permutation/frame validation from this branch, integrate generic verification at the shared boundary and Mathieu-specific state replay into the existing Mathieu app PR #3 as appropriate. Do not merge this draft as an independent Mathieu movie subsystem; retire it as superseded once those pieces and their evidence have been carried forward. Kitchen remains the only ordinary stills→MP4 encoder. No acceptance or merge claim is made by this comment. |
This was referenced Oct 22, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mathieu's offline capture boundary now uses checked Ithon and the existing shared planned-movie system. All newly maintained capture source/packages/tests are .pi; the three first-party .py files are removed. Typed validation retains the compatibility manifest, event order, bijections, word composition, frame hashes and atomic output replacement.
The migration fixed a real defect: FFmpeg recovery could conceal corrupt compressed PNG input. Strict source decoding plus the actual source decoded-frame count now rejects that input before Kitchen encoding. Previous public output survives failures. The Kitchen source revision is checked, rather than merely trusting KITCHEN_ROOT.
capture/shared.piinvokes the pinned registered FPwiggle-video-01operation. It reuses the native Mathieu engine/renderer/session, independent AI-CI verification and the canonical Kitchen encoder. It refuses wrong FP sources and reused/interrupted output. No private renderer, encoder or competing group engine is introduced. The shared FP controller and the Ithon host substrate remain explicit inherited runtime boundaries; their source is not copied or newly generated in Mathieu.Published source:
338e1a54f656834d10987d5095621a50a678222d.Exact-head hosted Ithon verification: PASS, with the exact source-head checkout witnessed in the job log. All 16 media cases execute with real Kitchen/FFmpeg output and complete decoding; no dependency silently skips a test. The suite verifies the actual imported exporter source hash in Ithon's checking receipt. Shared source/reused-output refusals also pass.
Actual shared production through this new entrypoint completed all five registered stages in run
wiggle-video-01-20261022T015847.849611Z: timeline tests, real production, independent verification, adversarial cases and sealing. It generated all four configured examples; Mathieu used the genuine 18-second grid → rosette → octad → ATLAS action film at 288×288 for this qualification run. No verifier assertion was weakened. The initial 256×144 attempt was rejected by the existing clear-viewport assertion and is retained as failed evidence, not acceptance.This merges the implemented offline command-line capture path. It does not claim application export/share UI, on-device recording/cancellation, the 24 Griess book operations, current APK/update acceptance, or protected-service deployment. Those retain their own obligations; they do not redefine this scoped offline path.
Assignments and acceptance: isomorphisms/flexible-pipes#243 ; isomorphisms/ai-ci#312 . Shared route: isomorphisms/flexible-pipes#250 . Generated-Python regression notes: isomorphisms/ai-ci#320 , isomorphisms/flexible-pipes#257 , isomorphisms/kitchen#77 .