> ## Documentation Index
> Fetch the complete documentation index at: https://developers.klarity.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Process Index

> Discover and navigate the hierarchy of processes the organization runs.

Use these tools when [`search`](/tools/entry-points) results feel sparse, or when you need richer process metadata than [`fetch`](/tools/entry-points) returns.

| Tool                         | When to use                                                                                                                                                                                                                                                                                                                                                                                                       |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `search_processes`           | Ranked process search combining keyword matches (name, objective, team, value stream) with semantic similarity. Returns mixed hierarchy-node + process results — use when a top-level value stream or department might be a better starting point than a leaf process.                                                                                                                                            |
| `get_process_hierarchy`      | Browse the whole index structure. Use when `search` misses, or to orient before drilling in. Cap depth with `max_depth`; the response flags truncated branches and points you at the next call.                                                                                                                                                                                                                   |
| `get_hierarchy_node_details` | Inspect a single hierarchy node — parent, children, linked process, attributes. The right call for a folder / group / value stream key.                                                                                                                                                                                                                                                                           |
| `get_process_details`        | The rich nested payload for a process: `current_version`, `dependencies`, `hierarchy_node`, `attributes`, optional version history. Default returns a summary with operational attributes; pass `scope` to include `tasks`, `observations`, `dependencies`, `linked_artifacts`, `policies`, or `history`. This is what [`fetch`](/tools/entry-points) reshapes — use directly when you need the structured shape. |

## Choosing among the lookup tools

* **Semantic + keyword, broad** → `search` (entry point) or `search_processes` (richer, mixed results)
* **You have a resource key** → `get_process_details` (for processes) or `get_hierarchy_node_details` (for folders / groups / value streams)
* **Browse / orient** → `get_process_hierarchy`, then drill in with `get_hierarchy_node_details` or `get_process_details`
* **Drill further** (what actually happened on a specific process) → [`get_process_observations`](/tools/observations-and-changes) → [`get_observation_citation`](/tools/observations-and-changes). See [Process observations](/tools/observations-and-changes) for the full toolset.

## Common chains

* "What's in this value stream?" → `get_process_hierarchy` (broad) → `get_hierarchy_node_details` on the relevant node → `get_process_details` on each leaf
* "Pull every dependency of process X" → `get_process_details` with `scope=["dependencies"]` → walk the `dependencies` list with further `get_process_details` calls
* "I have a resource key, give me everything" → `get_process_details` with the scopes you care about (`tasks`, `linked_artifacts`, `history`)
* "What actually happens when this process runs?" → `get_process_details` → [`get_process_observations`](/tools/observations-and-changes) → [`get_observation_citation`](/tools/observations-and-changes) on a representative deviation