Type a section name and press Enter. Use “help” for the list.
Cliste experiment
Shared perceptual vocabulary and reconstructible experience — development-preflight
Registered 8 Oct 2026 · Snapshot 12 Oct 2026
The question
Acquire reusable VSA patterns and measure their downstream utility, retained detail and complete storage cost.
Why this experiment?
Reusable patterns could reduce repeated storage and support later operations. The relevant test is useful readback at an honest storage cost, not vocabulary size alone.
How it works
Acquire a bank from encountered visual features and compare storage and readback against simpler vector encodings. Pattern IDs are addresses of acquired vectors, not supplied object categories.
Follow this part of the investigation: Can experience share a vocabulary without losing useful distinctions? →Implementation and comparison details
Study stage: development-preflight. Acquired vector content, compact occurrence references, registered detail policy and full storage accounting; frozen source and dependencies precede execution.
What happened
Attempt failed; retained outputs are incomplete. See execution log.
Results and visual artifacts
Open a figure for its input, comparison, and result. Click an image to enlarge it.
No result figure was produced before this development attempt failed. Its incomplete execution remains recorded; the completed vocabulary comparison is presented separately. There is no visual outcome to infer from the absence of images.
No visual artifacts were available at snapshot time.
Limits and next question
Development preflight selects methods using development evidence only; its outcomes are not final confirmation. The final run uses separately locked methods and inputs. The codec and sensory geometry are supplied machinery; pattern contents are acquired. Compact references are storage addresses, not semantic categories. Count the shared bank, references, structure, fallbacks, versions and model costs. Prototype reuse alone establishes neither object understanding nor integrated milestone 1.3. Rotation, scale, novelty and detail limits remain visible; no checkpoint is installed.
Next question. Use development evidence to specify a separate locked final run; preflight does not establish the final claim.
Inspect the evidence
Download the methods and measurements for this experiment. Large training and saved-state files are not included.