What round-trips, and what doesn't
The honest boundary: presentation round-trips between design and code; behaviour does not. What a designer or an agent can change and have flow back — and what stays in your hands.
How it works
Inkbridge models the presentational layer — structure, styling, variants, states, tokens — and never behaviour. That draws a clean line for what can round-trip. A token edit, a colour, a spacing value, a corner radius, a variant swap, a text style: all presentational, all expressible in the model, all able to flow back to code. Validation logic, data wiring, new interactions, animation timing: behavioural, never reconstructed. This is a feature, not a gap — a designer in Figma can only change things on the presentational side, which is exactly the subset that is safe to round-trip, and an agent writing code is held to the same line by the conformance gate. Do not expect Inkbridge to regenerate behaviour; expect it to keep the look of every state honest.