A framework showcase that treats state, revision and calm orientation as first-class structure.
Manifest
CLARIFICATION
Orientation
Technology Speaks
The shell turns the design manifesto into route structure, state visibility and calm guidance.
Workspaces
RAW
Work
Raw Workspace
Typed forms become a protected intake surface with revision logs and explicit transitions.
CLARIFICATION
Work
Clarification Queue
Remote data stays meaningful by exposing state, maturity and tension in the same field.
CONDENSED
Context
Condensed Context
Windows and notifications support secondary work without collapsing the main surface.
Reference
ARCHIVED
Reference
Reference Atlas
Component knowledge enters a quiet archived layer without losing live examples.
scala-js-jfx
Clarity-driven framework showcase
Manifest
Technology Speaks when state, tension and revision remain visible.
This showcase is no longer a gallery of unrelated demos. Each route now carries one clear responsibility, so the framework reads as one calm system instead of a pile of isolated examples.
Operating Rules
The shell follows the manifesto structurally, not decoratively.
Navigation, workspaces and reference pages stay calm, direct and intentionally spare.
Separation before beauty
Orientation, work and context are split into explicit surfaces with hard boundaries and soft internal composition.
Clarity before speed
The primary actions stay deliberate. They do not chase stimulation or instant feedback.
Revision before overwrite
The form workspace records revisions, the queue shows maturity, and the docs keep archived knowledge connected to live runtime behavior.
Workspaces
The framework is introduced through roles, not through random feature buckets.
Each route demonstrates one semantic zone of the system while still sharing the same DSL, state model and viewport runtime.
RAW
Work
Raw Workspace
Typed forms become a protected intake surface with revision logs and explicit transitions.
No forced completion, no silent overwrite.
CLARIFICATION
Work
Clarification Queue
Remote data stays meaningful by exposing state, maturity and tension in the same field.
Conflict is a signal, not an error.
CONDENSED
Context
Condensed Context
Windows and notifications support secondary work without collapsing the main surface.
Use motion only when it improves understanding.
ARCHIVED
Reference
Reference Atlas
Component knowledge enters a quiet archived layer without losing live examples.
Archive is stable, but still connected to working examples.
Revision Model
Progress is expressed as explicit continuation.
The showcase keeps the revision concept visible so editing feels like continuation instead of correction.
01
Protected intake
The form workspace starts in RAW so unfinished content can stay incomplete.
02
Clarification
The queue keeps tension and maturity visible instead of flattening every row into one visual treatment.
03
Condensation
The window system gives secondary work its own context without breaking the main surface.
04
Archive
The docs layer turns stabilized knowledge into a readable reference without losing live examples.
What This Proves
The app module now carries more of the framework story.
Routing, dynamic render blocks, typed forms, remote data and the viewport system are all visible as one coherent product language.
ObserveRender in the shell
The chrome reacts to route state directly, so page context is derived from runtime truth instead of hidden UI flags.
ForEach in the workspaces
Revision ledgers and docs listings are rendered through framework primitives instead of manual DOM stitching.
Component docs stay live
The archived layer embeds interactive previews so reference pages remain connected to actual framework behavior.