This package records one complete browser-hosted Cartilage fabric run. A seeded 64x64 fabric is driven through 525,568 committed updates by a QuadFlow/Cartilage QFG stream, while a ripple-carry adder body is reconfigured from a 2-bit body to a 3-bit body and then back to a preserved 2-bit body.

The important engineering claim is the lockstep capture rule: the recorder stores one initial frame, then one video frame after every committed fabric update. The compressed publication MP4 and the local canonical WebM both decode to 525,569 frames.

The Run Claim

This is not a sampled timeline page. The exact-frame package records every committed update in the run: 525,568 fabric updates plus the initial state. The QFG stream contains 7,956 parsed frame declarations and 704 expectations; all 704 passed.

Fabric grid: 64 x 64 cells.
Seed cells: 4,096 explicit primitive cells.
QFG frames: 7,956.
Fabric updates: 525,568.
Recorded frames: 525,569.
Expectation result: 704 / 704 passed.
Final active boundary outputs: right edge positions 16 and 34.

Publication Video

Compressed H.264 publication copy of the exact-frame capture. The verification JSON reports 525,569 decoded MP4 frames, matching the local canonical WebM frame count.

The canonical VP9 WebM is preserved locally in the same package, but it is about 221 MB and is intentionally not committed to this web repository. The committed MP4 is about 25 MB and keeps the same decoded frame count for publication.

Final State

Cropped detail of the final Cartilage fabric state for the exact-frame reconfigurable ripple-carry adder run — Cropped detail from the final committed frame. Open the image for the full 512x512 final render.

What Reconfigured

The QFG source describes a browser/GLSL-native reconfigurable ripple-carry adder proof. The run starts as a stable 2-bit body, streams a physical 187-cell delta component into a root-owned Cartilage subtree, grows the body to 3 bits, and later drives the same region back to the preserved 2-bit body.

The run note identifies the reconfiguration root as (25,28) with parent top and first child (25,29). It reports a maximum tree depth of 57 and a dwell value of 64. The target sequence after the initial 2-bit check is 3 -> 2.

Boundary I/O Discipline

The browser host receives primitive seed cells and boundary/edge value frames. During execution, the driver does not address arbitrary internal cells by global coordinate. It streams values through the exposed edge surface and advances the fabric one committed update at a time.

The key runtime repair for this package is that edgecell pwr/gnd declarations are treated as boundary metal drives, not as whole boundary-cell rewrites. That preserves parent pointers and configuration ownership while still allowing the host to drive the inward-facing Sinew metal bit.

edgecell left 4 pwr parent right
now drives only left.sinew_right[4]
instead of rewriting the whole boundary cell body

Lockstep Timing

For each QFG frame, the driver stages the sparse boundary writes, performs exactly one fabric update, and records the resulting canvas frame. The package note describes the rule as one initial frame before computation plus one frame after each committed fabric update.

That is why the arithmetic is in the counts: 525,568 fabric updates produce 525,569 recorded frames. The video is not a screen recording that happens to show a run. It is a frame-source capture driven by the browser canvas after each committed update.

Checkpoint Frames

The package also includes 20 checkpoint PNGs for quick inspection. These are not a replacement for the exact-frame video; they are convenient stills from the same run.

Checkpoint frame at cycle 276,615 — Cycle 276,615.

Checkpoint frame at cycle 525,568 — Cycle 525,568.

Artifact Bundle

The committed publication bundle is under cartilage/codex5.5/. These links point to concrete files; the oversized canonical WebM is intentionally excluded from git.

package note - human-readable summary of the run, artifacts, counts, and runtime repair.
verification JSON - generated frame counts, byte counts, and ffprobe summaries for WebM and MP4.
full final PNG and cropped final detail - final committed visual state and publication preview crop.
raw run report - browser expectation trace and run metadata.
stdout log and stderr log - the stderr log is empty for this run.
main QFG sample - generated 2-bit to 3-bit to 2-bit stream.
callout surface QFG - publication labels for the final rendered fabric.
edge I/O regression fixture - checks the ownership-preserving edgecell behavior.
QuadFlow Cartilage semantics, substrate map, and browser fabric goals.

Tradeoff

The exact-frame capture is useful because it ties the video frame count to the fabric update count. The cost is file size: the canonical lossier-but-exact-frame WebM is still too large for normal git hosting, and the publication page uses the smaller MP4 copy for browser playback.

The next useful layer is not a more dramatic video. It is tighter reproduction packaging around the QFG generator, host driver, runtime ownership checks, and compact summaries of the 704 expectations.