Skip to main content

​
Keeping logic and descriptions aligned

Every Blueprint in Leapter has two sides:
  • Descriptions — the project description, Blueprint descriptions, section titles, and the labels around each node, all written in plain language.
  • Logic — the diagram of decisions, assignments, calls, and returns that actually executes.
The Specification view shows both together, description next to logic. When you build a Blueprint the two are aligned, but over time they drift: you tweak a condition without updating the description, you rewrite a description without changing the logic, or a teammate edits one side without touching the other.

​
Bringing the two sides back in line

The fastest way to reconcile them is to ask the Lab Agent in plain language:
  • “Update the section descriptions to match what the logic actually does.” — when the logic is the source of truth and the wording fell behind.
  • “Make the logic follow the description for the bulk-discount section.” — when a domain expert updated the spec text and you want the diagram to catch up.
Because the agent edits both the diagram and the surrounding text, and can run your tests to check the result, it keeps the two sides consistent in one step. For smaller, hands-on adjustments you can also:

​
Tips

  • Reconcile before you share. Before sending a public link to a stakeholder, ask the agent to bring the descriptions in line with the logic so the spec they read matches what runs.
  • Reconcile after big edits. After restructuring a diagram or rewriting a section, check that the other side hasn’t fallen behind.
  • Review before applying. In the agent’s Approval mode you see every proposed change before it lands.

​
What to do next

  • Lab Agent — reconcile descriptions and logic by chatting with AI
  • AI Editing — make a targeted change with a natural-language prompt
  • Inline Editing — edit titles, descriptions, and expressions in place