Private Pro implementation · v0.5.0
The code-aligned local materializer is implemented, not released.
The deterministic v0.5.0 payload contains 300 source-aligned contracts, 138 editable component sets and 2,588 editable variants, including 1,728 pattern variants. Only v0.5.0 has been run in the live file; current-version founder review and export remain pending.
Release contract
A real release must include useful code-aligned components and patterns, light and dark variables, states, properties, responsive and auto-layout guidance, token annotations, documentation, version notes, checksums, clean export verification, protected delivery, backup, and restore evidence.
Current boundary
External materialization is current-version-materialized-export-restored-founder-review-pending and manual QA is pending. Editable design source belongs only in the private Pro repository. The public site may later publish founder-reviewed screenshots and boundary-safe metadata, never the paid design file or reconstructable source.
What code-aligned means
The materializer translates maintained component, state, token, and pattern definitions into editable Figma structures. Names and properties are designed to make implementation discussions traceable, but a generated design node is not automatically proof that the React component, browser rendering, or product content is correct. Design and code remain separate artefacts with separate review evidence.
Teams should use the kit to explore flows, responsive intent, theme choices, and component composition before handing decisions to implementation. They still need to supply real copy, imagery, data states, authorization rules, and product-specific accessibility requirements. Detaching or renaming components may be useful in a consuming file, but it also ends any simple correspondence with later source-aligned updates.
Why release remains gated
The current payload must be run in the approved live Figma file, then inspected for variant integrity, variable binding, auto layout, responsive instances, dark themes, direction, text overflow, and editing ergonomics. A clean export must be restored independently and compared with the reviewed file before a protected archive can be versioned. Until that evidence exists, the figures above describe an implemented local contract rather than a downloadable customer product.