reclayfiles, understood by experimentBlock editor ↗
Files stay in this browser.First computation downloads a pinned Python runtime from jsDelivr. No files are uploaded. Powered by Pyodide.

AN EDIT CAN MOVE EVERYTHING.

Keep the
connections.

Change the size of a field without leaving its pointers behind. Mark the same field in related files; learn the byte relationships; inspect every rewrite.

Local files. Separate downloads. No format database.

Independently produced image files, including the large observation that resolves a misleading short-field interpretation.

01 Observations

0 files

Choose related files where only the marked field changes. Start is inclusive, end is exclusive; include any required terminator, exclude alignment padding. These spans are your supplied evidence.

2–8 files · 1 MiB each · 4 MiB total

What this can establish

One marked span, byte-count fields, zero padding and absolute pointers into an unchanged suffix. All other bytes must fit an invariant envelope. Unchanged or unprobed dependencies can remain undiscovered. Passing a fit does not recover a complete format.

02 Interpretation

Examples can support several explanations. A selection is an explicit assumption.

Learned pointers will connect their stored addresses to the bytes they refer to.

Evidence & next experiment
No observations yet.

03 Reshape

no file

A fresh file must pass the selected model's guards, including its unchanged content. Arbitrary new images may not fit.

Ordinary Python. No Reclay installation, server or inference dependency needed. The exported editor repeats the file and pointer guards.

Load the experiment or add related observations.