> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/vex-nx-user-guide-1/labs/observe-validate-present.md).

# Observe, Validate, Present

These modes are for checking and showing work - not for heavy topology editing.

## Observe

Live-status cockpit (read-only):

* Health chips for nodes (running / stopped / failed) and links (up / down / suspended)
* "Updated Xs ago" freshness
* Filters: **All**, **Problems**, **Down links**, **Stopped**
* Clickable **Issues** list to jump to a node or link on the canvas
* Fabric link-state colours and flap pulse when the dataplane reports status

Use Observe after Start when you want to monitor the lab without Operate chrome.

## Validate

1. Switch to **Validate** (or open it after Design changes).
2. Wait for the automatic check, or click **Run checks**.
3. Read the toolbar summary (errors / warnings / passed).
4. Click a finding to select the related node or link on the canvas.
5. Fix issues in **Design**, then re-run checks before **Operate**.

Typical findings: empty lab, orphans, dangling links, missing or quarantined images, duplicate names, capacity notes, failed node status.

## Present

Clean, read-only demo surface:

1. Switch to **Present**.
2. Use **Fit topology** and **Fullscreen** as needed.
3. **Exit present** (or Esc from fullscreen) when finished.

Hide classroom chrome and the template drawer so the audience sees the diagram, not your tooling. Pair with **topology lock** when students should not drag nodes during a demo. Fabric link-state colours can still appear when the dataplane reports status.

## When to use which mode

| Situation                  | Mode     |
| -------------------------- | -------- |
| Add nodes / links / shapes | Design   |
| Boot nodes / consoles      | Operate  |
| Monitor health / problems  | Observe  |
| Pre-flight before class    | Validate |
| Project or share screen    | Present  |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vex-nx.com/vex-nx-user-guide-1/labs/observe-validate-present.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.