Visualizer Specification Families¶
Organization and authority¶
VisualizerKind provides the organizational parent for Visualizers. It classifies semantic subject shape; VisualizerSlot is a local composition boundary defined by a Dancer or Visualizer. A slot's owner supplies its subject binding, required contract, context, and participation constraints. A selected Visualizer fulfills that contract and owns its internal experience.
Kind specifications describe classification and established shared promises. They are not substitutes for owner-defined slot contracts. A Visualizer that fulfills multiple contracts still has one authoritative design specification, referenced from other applicable families.
Specification family¶
Kind specifications are normative for their semantic boundaries and common promises. Path Inspector owns its design and adjacent interaction grammar. Holon Inspector owns concrete Node composition and responsive presentation. Table Collection owns tabular interaction; Collection kind owns shared subject and mutation semantics. Underspecified accepted types remain explicit open details.
- Structure
- RootedNavigation
- Node
- Collection
- PropertyMap
- Value
- String
- Path Inspector
- Holon Inspector
- Table Collection
Graph and Geospatial remain peer specializations of Structure alongside RootedNavigation. Create kind directories on demand only, when a concrete documentation need establishes meaningful subject semantics or behavior to specify. Do not preallocate a directory tree from every ValueType or for symmetry. This index is not the full kind registry.
Property and value composition¶
PropertyMap owns set-level layout, visibility, personalization, and label/value pairing. It may compose String Visualizers for PropertyName labels alongside ValueType-specific Visualizers for values. Property is not a separate kind or selection layer. The DAHN design and kind specs use this model. Historical planning descriptions and concrete extraction sources are tracked for reconciliation in the ledger.