whynot-design/registry/capabilities/capability.design.whynot-system.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.design.whynot-system	Whynot Design System	Framework-agnostic visual language for whynot prototype/market-signal artefacts: design tokens, drop-in CSS, Lit-based web components usable from React/Django/Vue/plain HTML, and Django template adapters.	whynot-design	draft	consumer	design-system web-components frontend	discovery availability current target confidence rationale D3 D4 medium README documents a clear three-layer architecture (tokens, CSS, Lit web components) plus a companion DesignSystemIntroduction.md describing propagation pipeline, versioning, and A1 staging relative to whynot-control. current target confidence rationale A2 A3 high Published as `@whynot/design` (not private: `"private": false` in package.json), ships a CLI (`whynot-design` bin), tokens/CSS/JS source, and Django adapters — genuinely consumable across frameworks today, not just planned.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 low scope_vs_intent_and_consumer_expectations framework-agnostic Lit web components (same `<wn-button>` usable in React/Django/Vue/plain HTML) design tokens as source of truth Django adapter partials package is publicly consumable (not private) level confidence basis known_reliability_risks R1 low consumer_quality_signals cross-framework consumption claims not independently verified in every target framework during this sweep	intent includes excludes assumptions use_cases research_memos Give whynot's prototype and market-signal artefacts a consistent, deliberately-unfinished visual language, consumable identically across any framework via framework-agnostic web components rather than per-framework reimplementation. design tokens (tokens/*.json) drop-in CSS (src/styles/*.css) Lit-based web components (src/elements/*.js) Django adapter partials whynot-control's product/business logic itself (see whynot-control)	current_level target_level current_artifacts target_artifacts consumption_modes A2 A3 `@whynot/design` npm package (public) `whynot-design` CLI library import (npm) cli django template adapter	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md DesignSystemIntroduction.md tests/ test-results/	recommended_for not_recommended_for known_limitations whynot-family apps needing a consistent, framework-agnostic visual language across React/Django/Vue/plain HTML consumers wanting a themed (non-neutral) visual language, or needing whynot-control's business logic itself cross-framework consumption not independently re-verified in every target framework this sweep

Whynot Design System

Overview

@whynot/design is the framework-agnostic visual language for whynot's prototype and market-signal artefacts: design tokens as source of truth, drop-in CSS, and Lit-based web components that work identically across React, Django, Vue, and plain HTML, plus Django adapter partials — publicly published, not a private/internal-only package.

Assessment notes

Discovery

README documents a clear three-layer architecture (tokens, CSS, Lit web components) plus a companion DesignSystemIntroduction.md describing propagation pipeline, versioning, and A1 staging relative to whynot-control.

Availability

Published as @whynot/design (not private: "private": false in package.json), ships a CLI (whynot-design bin), tokens/CSS/JS source, and Django adapters — genuinely consumable across frameworks today, not just planned.

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml