AI-native design editor. Open-source Figma alternative.
FIG package architecture
These documents explain the .fig reader and its editing/export contracts.
They are package implementation documentation, not a release-status log.
Reading order
| Document | Question |
|---|---|
| Architecture | Which package owns each stage? |
| Source model | What are records, resources, and identities? |
| Instance evaluation | How do bindings and overrides resolve? |
| Materialization | How do occurrences become editable nodes? |
| Document sessions | How do incremental loads and recovery work? |
| Export | How are runtime identities and claims encoded? |
| Validation | What constitutes compatibility evidence? |
archive -> source model -> instance evaluation -> materialization
|
document sessions + editor actions
|
export
|
Figma validation
Status vocabulary
- Required invariant: a correctness constraint, whether or not all cases satisfy it yet.
- Implemented: behavior present in the linked modules and covered by the cited tests.
- Known limitation: a boundary not yet implemented or validated; not a supported fallback.
Every consumer uses this reader; the previous importer and its repair pipeline are gone, so there is one interpretation path, not a legacy mode. Remaining work is fidelity and performance acceptance against Figma, tracked per document as known limitations.
Keep temporary file keys, benchmark runs, experimental findings, and current blockers in
ignored scratch/ notes or the integration PR. Fixture provenance belongs alongside fixtures.
The public roadmap owns product-level direction.