Accepted LDD UI Standard
Purpose: preserve the UI decisions that are accepted enough to execute, while the larger LDD system plan continues through approval.
The older status-color proposal was useful as exploration. This page records the pieces that are now part of the V2 direction.
Accepted Pieces
Sidecar data
Use site/assets/ldd-index.json as the static site's lightweight source of truth for LDD IDs, category, lifecycle, wiki slug, source file, pilot metadata, and future hierarchy fields.
Category navigation
Group the LDD sidebar by working categories instead of a flat numeric list. Keep LDD numbers as stable historical IDs.
Semantic chips
Use status chips as visible summaries, but store meaning in data attributes: data-signal-kind, data-resolution-state, and data-wiki-block-id.
Stable block IDs
Every important decision block should receive a predictable ID so comments, signals, proposed patches, and future wiki records can target it directly.
Status & history
Every major LDD or header page should expose lifecycle state and revision history in a structure close to future wiki document revisions.
No canonical rewrites by default
UI/data wrappers are allowed. Direct LDD prose rewrites remain under the Claude LDD lock unless David explicitly overrides it.
Status Vocabulary
The status system should not imply sequence or permission. It describes current reliability and attention needed. A pending item can still be explored.
Current Implementation
- LDD-29 Gym Systems has the first semantic decision-chip pilot.
- LDD-30 Mech Core has the first lock-ready mechanical-core pilot.
- The shared sidebar now reads the sidecar index when available.
- The old Page Design + Status Colors proposal remains archived as the origin note.
Not Yet Accepted
The larger multi-level hierarchy, Input → Logic / Analysis → Output workflow, worldbuilding/atmosphere layer, and wiki import model still need approval through the LDD System Plan.