Documentation Index
Fetch the complete documentation index at: https://docs.leapter.com/llms.txt
Use this file to discover all available pages before exploring further.
Sync & Suggestions
Every Blueprint in Leapter has two sides:- Descriptions — the project description, Blueprint descriptions, section titles, and the comments around each node, all written in plain language.
- Logic — the diagram of decisions, assignments, calls, and returns that actually executes.
The two sync directions

| Icon | Direction | What AI proposes |
|---|---|---|
| Book | Logic → Descriptions | Updated descriptions that match what the current logic actually does |
Code </> | Descriptions → Logic | Updated logic that does what the current descriptions say |
The Suggestions panel
When AI finds drift, it produces a suggestion — a diff that shows what it would change. Suggestions land in the Suggestions tab in the right sidebar of the editor. Open it (sparkles icon) to review. Each suggestion is presented as a side-by-side diff. You can:- Apply the suggestion — the changes are written into your Blueprint.
- Reject the suggestion — nothing changes; the suggestion is dismissed.

When to use which direction
Logic → Descriptions (Book icon)
Reach for this when the logic is the source of truth and you want the descriptions to catch up. Common cases:- You just refactored a Blueprint and the section descriptions still describe the old shape.
- A teammate added new branches and the project description doesn’t mention them yet.
- You want a fresh, accurate description for a Blueprint that someone outside your team is about to read via a public share.
Descriptions → Logic (Code icon)
Reach for this when the descriptions are the source of truth and you want the logic to match. Common cases:- A domain expert updated the spec text to reflect a new business rule and you want the diagram to follow.
- You drafted a Blueprint description in plain language and want AI to convert the changes into structured logic.
- You’re reviewing a project that was AI-generated and the descriptions clearly state intent that the logic doesn’t yet implement.
How sync compares to AI editing
| AI Editing | Sync & Suggestions | |
|---|---|---|
| You provide | A free-text instruction (“add a discount for orders over 200 EUR”) | Nothing — AI inspects what’s already there |
| AI considers | Your prompt plus the current Blueprint | The current descriptions, the current logic, and the gap between them |
| Result lands as | A Review-mode diff on the canvas | A diff in the Suggestions panel |
| Best for | Adding new behavior or making a specific change | Catching drift between description and logic |
Tips
- Run sync after big edits. After rewriting a section description or restructuring a diagram, click the relevant sync button to check the other side hasn’t fallen behind.
- Use sync before sharing. Before sending a public link to a stakeholder, sync descriptions from logic so the spec they read matches what runs.
- Reject freely. AI’s suggestions are proposals, not commands. If a suggestion changes something you didn’t intend to change, reject it — the original stays intact.
- Sync one Blueprint at a time. The sync buttons are scoped to the maximized Blueprint, which keeps the diff focused and easy to review.
What to do next
- AI Editing — make targeted changes with a natural-language prompt
- Inline Editing — edit titles, descriptions, and expressions in place
- Specification view — read the descriptions and the diagrams together