How the toolset is organized
Every workflow reduces to: find the right process(es) → fetch detail → gather evidence → traverse relationships → synthesize.| Group | What it covers | When to start here |
|---|---|---|
| Standard entry points | search, fetch | The default starting path for any process question |
| Process Index | Hierarchy navigation, process details, ranked search | search results feel sparse, or you need richer metadata than fetch returns |
| Process observations | Recent changes, observations, activity timelines, sessions | ”What changed?”, “what happened?”, “why does this run this way?” |
| Artifacts | Document search, content retrieval, in-document text search | The user names a document or recording |
| Workspace | List accessible workspaces | Orienting before drilling in |
| Agent Builder | Agent builder instructions and build resources | Building a skill, agent, or automation from your processes |
Before you call
Read Operating principles — the conventions for staying grounded, iterating on search, separating observed from inferred, and avoiding common mis-uses (treatingsearch_* snippets as final answers, exposing internal IDs in user-facing prose).