DESEN is an open protocol and Web/React reference implementation for a model in which designers author production interfaces as validated data—rather than handing static design files to developers for reimplementation.

Why the name DESEN?

The name comes from DESign ENvironment. It expresses the long-term vision behind the project: design should not end as a static artifact waiting to be rebuilt. DESEN is intended to be the shared environment where designers compose production experiences and applications safely execute them through capabilities defined by developers.

Traditional workflow

Design file → Handoff → Frontend rebuild → Drift

DESEN

Product capabilities → Authoring → Validated bundle → Application runtime

The designer owns the experience composition. The developer owns the trusted components, operations, and platform.

We are building one deliberately narrow vertical slice:

A sign-in surface is authored, validated, published, and activated in a separately built React application—without recreating the same screen as a second React component tree.

Status: public, early-stage implementation.

DESEN 0.1.0 is frozen as the current proof baseline, not a stable standard.

See the architecture · Read the protocol · Challenge an assumption

The framework-neutral runtime core is currently under construction. Progress below is synchronized from the public implementation repository.

Overall: ██████████████░░░░░░░░░░░ 80 / 145 tasks complete (55%)

M06 complete: ███████████ 11 / 11 tasks complete (100%)

Proof gates: 7 / 13 complete · Active infrastructure: none · Next implementation: M07-T07 (NOT_STARTED)

Follow the detailed task board

The repository is open for scrutiny before it is ready for adoption. Questions, counterexamples, and challenges to the model are welcome.