> ## 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.

# Specification View

> The document in the middle of the Blueprint Editor — read and edit your whole project as a structured document, with every Blueprint's diagrams embedded inline.

The **Specification view** is what the middle of the [Blueprint Editor](/editor/introduction) shows in **Design** mode — area **3** on the [Overview](/editor/introduction#find-your-way-around). It presents your entire project as a structured document: the Type Definitions, then each Blueprint as a chapter with its inputs and outputs and its interactive diagrams embedded inline.

This page covers the document itself: what is in it, how to move around in it, and what you can edit in it. When you want to focus on one Blueprint's diagram, you maximize it in place — see [Diagram view](/editor/diagram-view).

<img src="https://mintcdn.com/leapter/6WaSHiQVGWUADy2e/images/spec-view-document.png?fit=max&auto=format&n=6WaSHiQVGWUADy2e&q=85&s=1f62b9528b40f64f6945d59daefb399e" alt="The Specification view of the Loan Application Scorecard project — the project title and description, then the Type Definitions with their Name, Type, and Details columns" width="734" height="800" data-path="images/spec-view-document.png" />

## What you see

The document is organized top to bottom:

| Section | What it contains |
| :- | :- |
| **Project header** | Project name and description |
| **Type Definitions** | All types defined at the project level, grouped by kind, with a **Details** column for their rules — see [Type Definitions](/editor/type-definitions) |
| **Public** and **Private** | Each Blueprint as a numbered chapter, under a **Public** or **Private** divider (see [Public and private Blueprints](/release-and-integrate/releases#public-and-private-blueprints)) |

Each Blueprint chapter contains:

* The Blueprint's name and description
* Its **Inputs**, **Outputs**, and **Locals**, each with its type and a **Details** column for descriptions, defaults, and rules — see [Inputs and Outputs](/editor/inputs-and-outputs)
* **Calls** and **Called by** pills, linking to the Blueprints it calls and the ones that call it
* Its numbered sections, each with a description and an embedded interactive diagram

The **Contents sidebar** on the left mirrors this structure as a navigable table of contents. Click any entry to scroll to it; double-click to maximize.

## Navigating the document

### Scroll, click, or jump

* **Scroll** through the document to read your project end to end.
* **Click** an entry in the Contents sidebar to jump to that section. The view scrolls smoothly and the entry is highlighted as the active section.
* The minimap docked to the right edge of the document gives you a compact overview of the whole project — click anywhere on it to jump to that location.

### Maximize a Blueprint

Each Blueprint section has a **maximize** icon in its header. Click it (or double-click the Blueprint's entry in the Contents sidebar) to fill the canvas with that Blueprint's diagram.

While maximized:

* The Blueprint's name appears at the top of the canvas.
* Zoom, **Center Diagram**, undo / redo, and canvas settings are in the [top toolbar](/editor/toolbars-and-panels#top-toolbar) — see [Diagram view](/editor/diagram-view).
* Click **Minimize** in the top toolbar to return to the full document.

## Editing in the Specification view

The Specification view is **fully editable**. You can:

* **Edit titles and descriptions** directly in the document — the project title, Blueprint and section headings, descriptions, and node labels are all click-to-edit.
* **Edit nodes inside the embedded diagram** — every diagram in the document is interactive. Click a node to select it, double-click to edit. See [Inline editing](/editing/inline-editing).
* **Add, edit, and delete inputs, outputs, and locals** — see [below](#edit-inputs-outputs-and-locals).
* **Add and delete sections and error handlers** — see [below](#add-and-delete-sections).
* **Point the Lab Agent at an element** — select it and press **Ctrl+I** (or **Cmd+I** on Mac) to drop it into the agent chat. See [Lab Agent](/editing/lab-agent#point-the-agent-at-a-node-with-ctrli).
* **Build or edit with the Lab Agent** — open the **Agent** tab and describe the change in plain language; the agent can build across Blueprints and run your tests. See [Lab Agent](/editing/lab-agent).

While the Blueprint is running or while AI is proposing changes, the document switches to read-only mode to prevent conflicting edits.

### Edit inputs, outputs, and locals

Each Blueprint chapter lists its **Inputs**, **Outputs**, and **Locals**. To add one, click the **+** line below a group (**Add an input**, **Add an output**, or **Add a local**) and give it a name. To change one, click the chevron (**Edit definition**) at the end of its row: a card opens where you rename it, change its type, describe it, and set its rules and default — or delete it. Undo works as usual.

See [Inputs and Outputs](/editor/inputs-and-outputs) for what each setting means.

### Add and delete sections

Every heading has a **⋮** menu:

<img src="https://mintcdn.com/leapter/qMwjK3KQYippi7Jz/images/spec-view-blueprint-menu.png?fit=max&auto=format&n=qMwjK3KQYippi7Jz&q=85&s=d9582543800a9175af31b1eaec519829" alt="The Blueprint actions menu next to the Loan Application Scorecard heading, with Section — At the end of this blueprint, Make private, and Delete blueprint" width="694" height="189" data-path="images/spec-view-blueprint-menu.png" />

| Menu | Entries |
| :- | :- |
| **Blueprint actions** (on a Blueprint chapter) | **Section** — add a section at the end of the Blueprint; **Make public** / **Make private**; **Delete blueprint** |
| **Section actions** (on a section) | **Section** — add a named group of steps inside this one; **Handle an error** — add a handler for when this section fails with an error; **Delete section** |

To add a section between two others, hover over the gap between them and click **Add a section here** → **Section here**. Give the new section a name; you then build its logic in the diagram.

When you delete a section that contains steps, Leapter asks what to do with them: delete them together with the section, or **Keep steps** to move them up into the surrounding section.

## Running Blueprints from the Specification view

Each Blueprint section has its own run controls. After a run, the **Outputs footer** at the bottom of the section shows the resulting output values, and the trace controls in the [top toolbar](/editor/toolbars-and-panels#top-toolbar) become active so you can step through the execution.

Leave **[Live mode](/test-and-validate/test-your-blueprint#live-mode)** running in the top toolbar and Leapter re-runs your Blueprints automatically every time you change inputs or logic — the Outputs footer of every Blueprint updates as you edit.

## When the Specification view is most useful

| Use case | Why the Specification view helps |
| :- | :- |
| **Onboarding to an existing project** | Read the project end to end as a document, with descriptions next to logic |
| **Reviewing logic before deployment** | The numbered sections make it easy to verify each rule |
| **Working across multiple Blueprints** | The Contents sidebar and Dependencies graph let you jump around without losing context |
| **Sharing with stakeholders** | Generate a [public read-only link](/workspace/sharing) — non-technical readers see the same document you do |
| **Keeping spec and logic aligned** | Run `/review` in the [Lab Agent](/editing/lab-agent#commands) — it checks that descriptions and logic still tell the same story |

## What to do next

* **[Diagram view](/editor/diagram-view)** — focus on a single Blueprint's diagram
* **[Type Definitions](/editor/type-definitions)** — define reusable types for your project
* **[Lab Agent](/editing/lab-agent)** — build and edit by chatting with AI
* **[Sharing](/workspace/sharing)** — share your project as a public read-only link


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.