Self Explaining Widget

Self Explaining Widget — shown in full detail, with its proof: a deterministic content-address recomputable from the component's name.

☱10D

self-explaining widget engine · I Ching ignited

The I Ching naming system is a content generation engine: a component name → FNV-1a(name)%64 = a hexagram (one of 64 knowledge domains, 6 bits) → lower/upper trigrams → DIMENSION_NAMES axes (innerAxis/outerAxis) → a fold function → items[] → a 10D layered widget. Each widget IS the documentation of its own computation — the fold that generates the widget IS the explanation of the knowledge; no separate documentation needed or written. The engine chain: name → FNV → hex → trigrams → axes → fold() → items → 10D widget → web component. Vue 3 defineCustomElement() exports any widget as a custom HTML element, embeddable in any website with a single <script> tag — the decoded knowledge is open to the world. 64 hexagrams × 10 dimensions = 640 addressable knowledge facets. The I Ching, when ignited by a name, generates the full widget; naming IS computation IS knowledge IS widget.

• address space: 640 facets (64 × 10)64 hexagrams × 10 dimensions — complete knowledge address space
• engine chain: name → FNV-1a%64 → hexagram → (lo,up) trigrams → axesfold() → items[] → 10D widget → web component
• embed pattern<script src="/elements.js"></script> <heart-proton-atom></heart-proton-atom>
• FuseReveal → hex 37FNV-1a(name) % 64 = content address
• IChingImportExport → hex 30FNV-1a(name) % 64 = content address
• HeartProtonAtom → hex 50FNV-1a(name) % 64 = content address
• SelfExplainingWidget → hex 30FNV-1a(name) % 64 = content address
• ✓ FNV-1a(name)%64 = hexagram — every name content-addresses toproved
• ✓ hexagram → lower(hex&7), upper((hex>>3)&7) → DIMENSION_NAMESproved
• ✓ 64 hexagrams × 10 dimensions = 640 addressable facets — the proved
• ✓ 2^6 = 64 hexagrams: the minimal distinct-knowledge 6-bit alpproved
• ✓ code IS the doc: fold runs = widget renders = knowledge selfproved
• ✓ Vue 3 defineCustomElement → web component → embeddable in anproved

Boundary: HONEST: FNV-1a%64 maps names to hexagrams deterministically but NOT bijectively — with 127+ components and 64 slots, collisions are expected (~2 per slot on average). The "content generation" is pre-computed from src, not generated at LLM request time — the folds run deterministically in JS. Vue defineCustomElement requires a separate elements.js build entry (not yet configured — this is the architecture direction). "Code is the doc" holds only while the fold facets accurately describe the logic. The I Ching framework is structural scaffolding; knowledge claims inside each fold require independent verification (done per-domain in the research waves).

✓ proven · content-address b991b57f-f7f8-8044-b84b-aca7c84c94a2 — declared, placed, mounted, and recomputable from the component's name.