# Your first diagram

Build a small map you can recognize, then attach one useful health check. You do
not need an account, cloud subscription, or YAML experience to start with Desktop.

## 1. Install and open Reticle

[Download Desktop](https://github.com/mannders00/reticle/releases/latest) for your
platform. See [installation](installation.md) for package instructions, checksums,
and system tools. Desktop v1.3.0 is free and GPL-3.0-only; see [licensing](licensing.md).

If your team has already deployed Reticle, open its browser link instead.
Check the status bar: **viewer · read-only** lets you inspect and export;
**editor · live** lets you change the shared map. Team has one fixed topology,
so its workspace label does not open a file picker.

## 2. Choose a workspace

On Desktop, open the workspace menu at the top left:

- Choose a **Sample** to save an editable copy at a location you choose.
- Choose **New workspace…** to create an empty YAML file.
- Choose **Open file…** to edit an existing YAML file in place.

A workspace is one file, not a folder. Put it beside your infrastructure code if
you want to track changes in Git. Canvas changes autosave; Reticle does not commit
or push them to Git. See [workspaces and files](workspaces.md).

## 3. Draw a small system

1. Click or drag **Application** from the palette to add a service.
2. Double-click its title to rename it. Add a **Database** or another dependency.
3. Click a node's port dot, then the target node, to connect them.
4. Double-click the edge to edit its label, or select it and use the Inspector to
   change its kind.
5. Add a **Box** or **Host** around related nodes. Switch to **Tree** to see their
   containment hierarchy.

Use **Fit** to bring the whole diagram into view. Ordinary scrolling pans;
pinching or Ctrl-scroll zooms. The toolbar also has zoom controls.

> A node kind describes the map. Adding a server, Kubernetes node, or an address
> does not automatically discover resources or start a health check.

## 4. Add your first check

Use an HTTP endpoint reachable from the computer running Reticle. HTTP checks
require `curl` on that computer; leave the jq field empty for this first check.

1. Double-click the application node to open its Inspector.
2. In **Checks**, choose **+ add**, then **HTTP**.
3. Enter a name and the endpoint URL, such as `https://example.com/`.
4. Keep **Status** at `2xx`, choose a timeout, and leave **Enabled** on.
5. Choose **Save operations**. Use **Check** to request fresh evidence.

The Inspector shows the check result, observation time, and duration. A failed
check appears as `err`; it can mean an unhealthy endpoint, a missing tool, or a
network/authentication problem. Read the detail before drawing a conclusion.

For SSH checks, first enter the node's `host`, SSH `port`, and `user`, then choose
**Save details**. Add **SSH uptime** or **SSH service** under Checks. These use
non-interactive OpenSSH authentication from the Reticle host.

## 5. Keep context beside the diagram

Add notes for ownership or a runbook link. Resource add-ons such as RAM and disk
are labels you maintain, not discovered measurements. Choose **PDF** to export
the whole map for a review or handoff.

The Desktop window requests health on startup and every 30 seconds while it is
running. Closing the app stops that polling. Team collection runs on the daemon
host independently of browser tabs.

## Next steps

- [Draw and organize](diagramming.md) with notes, pages, and connections.
- [Checks and actions](checks-and-actions.md) explains custom commands and privileged mode.
- [Topology reference](topology-reference.md) documents the YAML format.
- The [Team Daemon](https://reticle.live/team/) keeps a map shared and always on
  for $199/month or $1,999/year per daemon. White-glove installation and initial
  mapping starts at $3,000 one-time; see the [operations guide](daemon.md).

Need help? Start with [troubleshooting](troubleshooting.md) or ask in
[Discord](https://discord.gg/x6hY9GYyph).
