troid & robby

A photograph in the gallery, chosen by the user. The compiler reads its bytes, builds the recipe's reverse, and binds them together — the obverse stays sacred; the reverse is born. Right of the obverse, the Teppanyaki Counter shows every visible stage as it runs: Intake MEASURED, Read VERIFIED with C2PA PRESENT, Measure MEASURED, Split DERIVED.

What you see is the working mechanism — not a simulation. The compiler's eight stages drive the right panel in real time; the palette swatches and palette K slider above are the controls; the button below turns the photograph to its inverse.

Robby extends a thesis first articulated in [Tech.City.Night.Work.Man]: a compiler can be a beautiful instrument whose visible working mechanism becomes part of the object it produces.

"I am now once again surrendering control to the compiler which picks apart my world and makes sense of it so that I can reassemble a new fictional world more representative of reality than dull reality itself." <br />— Mahesh Shantaram, Ulster MFA PHT 805, 2022

A real robby session: the obverse on the left, the Teppanyaki Counter on the right. The counter shows the live status of every visible stage — Intake MEASURED, Read VERIFIED with C2PA PRESENT, Measure MEASURED, Split DERIVED — and a one-line provenance statement: This reverse belongs to the active obverse, recipe, evidence policy, and compiler runtime.

Every photograph in the gallery is a candidate for an orio cookie. The user selects one. The compiler reads its bytes, builds the recipe's reverse, and binds them together — the obverse stays sacred; the reverse is born.

Troid is the Reverse-Obverse Image Duality: the format, the concept, and the two-sided image-object itself. Robby is the explainable compiler and working museum that produces and displays it.

The gallery gives the compiler corporeality — before compilation it is a calm photo viewer; after an intentional request, it becomes a laboratory.

The user writes a compact, human-readable program. It is not a fake settings panel — the compiler submits the authored text verbatim.

A recipe edit makes an earlier reverse visibly stale until the user compiles again. Invalid drafts are not silently fixed or guessed by the UI.

Once all eight stages run, the inverse appears. This is the same photograph from slide 5, flipped to its reverse: a palette grid at K = 8, arranged from the photo's dominant colours by a deterministic seed. The image is born — and it carries a binding to the original obverse, recipe, evidence policy, and runtime.

Act I · Read the source.
01 Intake — record the source artifact and its byte identity.
02 Read — extract EXIF / IPTC / XMP evidence + C2PA status.
03 Measure — compute canonical pixel identity.

Act II · Author the program.
04 Split — extract deterministic palette weights.
05 Declare — lower the authored recipe to canonical IR.

Act III · Produce the artifact.
06 Bind — form the reproducibility binding.
07 Resolve — run the deterministic renderer.
08 Marry — bind obverse + reverse into the session's orio cookie.

Robby source flows through a Rust lexer, parser, validator, and canonical IR — then through measurement, palette split, and binding, before a deterministic renderer produces the reverse image and runtime record.

The IR wire format stays intentionally stable as robby-ir-v1 while the compiler and execution contracts evolve behind it.

The user picks a palette size K. K = 24 means twenty-four distinct dominant colours are sampled from the obverse and arranged by a deterministic seed. The grid grows denser, more nuanced — closer to the source's actual chromatic material. Same source, same K, same seed, same recipe — identical pixel hash.

When the source has fewer distinct colours than K, Robby clamps honestly and explains why — rather than fabricate swatches or duplicate colours. The palette is not a mood board. It is traceable.

Robby forms a deterministic object binding from real compile inputs: source bytes, canonical pixels, the recipe, the canonical IR, the disclosure policy, the approved evidence, and the runtime versions.

The binding answers one question — does this reverse belong to this exact source, recipe, policy, and runtime? It does not claim copyright, authorship, ownership, or metaphysical truth.