This artifact records a successful lockstep browser-fabric run of the reconfigurable ripple-adder QFG proof. A 64x64 Cartilage GLSL fabric was driven through 525,568 cycles by external edge I/O, streamed 7,956 parsed QFG frame declarations, and finished with 704 browser-side expectations passing.

The visible timeline is deliberately small: 20 committed renderer states sampled from cycle 0 through cycle 525,568. It is a verification artifact, not a cinematic demo of every configuration bit moving through the fabric.

The Artifact Bundle

The media and source note are preserved together under cartilage/codex5.5/. The short video is the easiest way to inspect the sampled run; the contact sheet makes the exact sampled cycle labels visible on one page.

quadflow-cartilage-525568-timeline.mp4 - 10-second H.264 video, 20 sampled states at 2 states per second.
quadflow-cartilage-525568-timeline.gif - small looping web preview from the same frames.
quadflow-cartilage-525568-timeline-contact.png - all 20 sampled states on one sheet.
quadflow-cartilage-525568-timeline.md - the short local note that states what the run shows and what it does not show.

Video Timeline

Twenty committed visual states sampled evenly from a 525,568-cycle lockstep Cartilage/QuadFlow run.

Contact Sheet

Twenty sampled committed Cartilage fabric states labeled from cycle 0 through cycle 525,568 — The contact sheet is 20 labeled frames from cycle 0, then roughly every 27,661 to 27,662 cycles, through cycle 525,568.

What Ran

The run used a 64x64 Cartilage GLSL fabric with external lockstep edge I/O. In this context, the important claim is not that the picture changes dramatically. The important claim is that the browser-side fabric was stepped through a long, externally driven reconfiguration run and reached the expected final state.

The run streamed 7,956 parsed QFG frame declarations. It ended with 704 browser-side expectations passing. The final visible state is the committed result after the 2-bit to 3-bit to 2-bit reversible ripple-adder reconfiguration proof.

What The Frames Hide

The renderer exposes committed cell/body state. It does not expose every hidden in-flight configuration shift-register bit. That matters because most of the timeline can look nearly still while the lockstep driver continues advancing the fabric, shifting configuration, and checking boundary behavior.

Read the timeline as evidence of a completed run and a way to audit the sampled committed states. Do not read it as a frame-by-frame visualization of all internal configuration traffic.

Why This Belongs With Cartilage

The existing Cartilage nested-instantiation article explains the model: local ports, bounded daughter regions, serial configuration streams, tile roles, composability, and no global magic controller.

This timeline is a narrower evidence page. It shows that the same family of ideas can be driven as a long, checked browser-fabric run rather than only as a static explanation or a manually inspected demo.

Tradeoff

A compact renderer is useful for making committed fabric state visible, but it is not a logic analyzer. The next useful publication layer would expose more of the driver, QFG frame stream, boundary checks, and internal configuration path so the run can be reproduced and audited at a deeper level.