1 viewer
Component · Visualization
HyperEdge3D
One n-ary relation over an authoritative member SET of Node3D ids; optional ordered parts preserve offer/want or hop semantics without pairwise expansion.
- Category
- Visualization
- Slots
- 1
- States
- 0
- Writer
- Legacy
Preview
HyperEdge3D · Multi-Party Settlement
<Scene
height={280}
projection="isometric"
title="HyperEdge3D · Multi-Party Settlement"
>
<Camera focus="node_contract" mode="orbit" />
<Node3D
id="node_alice"
kind="account"
label="Alice (Account)"
weight={1.0}
/>
<Node3D id="node_bob" kind="peer" label="Bob (Validator)" weight={1.2} />
<Node3D
id="node_contract"
kind="crystal"
label="Escrow Contract"
weight={2.0}
/>
<Node3D
id="node_vault"
kind="settle"
label="Settlement Vault"
weight={1.8}
/>
<HyperEdge3D
id="edge_settlement"
kind="settlement"
members={["node_alice", "node_bob", "node_contract", "node_vault"]}
parts={[["node_alice", "node_bob"], ["node_contract", "node_vault"]]}
weight={2.5}
/>
</Scene>Variants
Anatomy
The named parts of the rendered markup. Recipes style these hooks, and every renderer keeps them stable.
| Slot | DOM class |
|---|---|
| root | .primitive-hyperedge3d |
States and platforms
The states the contract publishes, the platforms it declares, and the style recipes that dress it.
States
Platforms
Recipes
Renderers
The example above still needs shared writers for: Scene, Camera, Node3D, HyperEdge3D.
Declared adapters. A status is the manifest's declaration, not a measured parity result.
| Target | Renderer | Status |
|---|---|---|
| web | react | experimental |
| native | native-adapter | experimental |
Accessibility
Semantic structure must stay available without visual styling.
- Expose meaningful names for interactive controls.
- Keep keyboard and pointer behavior equivalent where the platform supports it.
- Publish state with native semantics and data attributes where the adapter supports them.