Drosophila / optic lobe / machine decoder

The fly is the input device.

Write a note. A reduced 61-column visual model turns its ink pattern into decoder activity, then files it into a local vial. The words are never interpreted.

BCI DECODERLOCAL / VISUAL
Retina field idle
Live specimen interface FLY–MACHINE LINK / IDLE
Drosophila connected to a brain-computer interface A recognizable fruit fly with red compound eye, paired wings, segmented abdomen, six legs and antennae. Two leads connect its optic lobe to a decoder monitor. SPECIMEN VG–01 / LATERAL VIEW SCALE / DIAGRAMMATIC COMPOUNDEYE OPTIC LOBE BCI DECODER LOCAL / VISUAL ONLY
retina occupancy0.00
edge contrast0.00
decoder channel
sample columns61

Illustrated fly + reduced browser model. No live animal, neural recording, handwriting recognition, or full connectome is claimed.

Signal inspection

From eye pattern to motor channel.

The note becomes a 61-cell luminance field. Four labeled decoder channels compete. Their names reference known fly motor pathways; the filing meanings are Vialgrub’s interface choices.

01 / compound-eye sample61 columns / idle
02 / decoder channelsWAITING FOR CARD

Local specimen archive

The vial rack

Click a vial to inspect it. Drag it between bays to overrule the decoder.

0 keep0 incubate0 discard

Saved on this device

Method / honest boundaries

A fly-shaped interface, not a claim of mind reading.

  1. Visible subject. The physical Drosophila drawing shows eye, antennae, thorax, paired wings, six legs, haltere, and segmented abdomen.
  2. Visible connection. Two optic-lobe leads run into the BCI decoder. The moving trace responds when the note changes.
  3. Reduced model. Sixty-one browser cells sample character occupancy and edges. Text meaning is deliberately unavailable.
  4. Human authority. The model suggests a bay; you can move or delete every vial. Local storage is the only persistence.

Unbuilt network boundary

On-chain rack pin / SOON

The note loop, decoder, manual override, local rack, import, and export work here. Publishing a rack hash does not: there is no contract, wallet request, token transaction, or simulated success.