Reviewing, editing and regenerating

Collider stops after every group and waits. What you do in that pause, whether you accept, edit, regenerate or skip, is the part of the flow that makes the result yours rather than the model's.

Accept is a decision, not a formality

Each group arrives with a preview and whatever the checks found. Accepting folds it into the layer being built. Nothing reaches your Figma file yet.

What can block Accept, and what cannot

Accept is disabled for exactly one reason: the artifact cannot be used. In practice that means an alias pointing at nothing, such as an unresolved, dangling or circular reference, or a document that cannot be parsed at all.

Everything else is a warning you may consciously accept. Contrast below the preferred target, a mode quality note, a literal that still renders a real value, a scale-membership remark, a coverage gap: all of these stay visible and none of them stand between you and your system. The rule is deliberate. A warning that silently removes your ability to proceed is a warning that will be worked around rather than read.

Changing your mind later

An accepted group is not frozen. Any accepted group can be edited, by telling Collider what to change, or regenerated from scratch, without touching the rest of the layer. The groups you were happy with stay exactly as they were.

You can also edit values by hand. Hand edits can be undone.

Skipping

A stage you do not need can be skipped, and skipping is recorded rather than hidden. The layer knows it has no radius scale because you decided so, not because generation failed.

History

The session keeps its own history: the groups you accepted, in order, with the artifact behind each one. Snapshots let you come back to a system later and see how it got its shape.

We use cookies. Necessary cookies keep Isotop secure and signed in. With your consent we also use analytics (Google Analytics) to improve the product. See our Cookie Policy and Privacy Policy.

Reviewing a generated layer | Isotop