Skip to main content

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.

A team manager is checking in on the processes they own. The assistant should produce a concise, evidence-backed brief — not a feature dump.

​
Example prompts

  • “Give me a state-of-the-team report on the processes we own.”
  • “What’s changed in our P2P team’s processes this quarter?”
  • “Onboard a new joiner to how this team runs.”

​
End-to-end recipe

1

Confirm the workspace

Call list_accessible_workspaces and switch if needed.
2

Pull the team's slice of the index

Call get_process_hierarchy_tree rooted at the team’s value-stream node.
3

Find recent changes

Call get_recent_process_changes — what versions have been edited recently across the workspace, filtered to this team’s tree.
4

Find recent deviations

Call get_recent_process_observations — what exception patterns are emerging.
5

Drill into the top processes

For each high-volume or recently-changed process:
6

Spot-check emerging deviations

Call get_observation_activity_timeline on the top two or three observations for primary-source detail.
7

Generate diagrams (optional)

Call generate_process_diagram on processes the manager will share in a 1:1 or team meeting.
8

Synthesize

“Your team owns N processes. M changed in the last 30 days. K are showing deviation patterns worth your attention. Here are the top 3 with evidence.”

​
Ramp a new joiner

The same chain works for onboarding a new person (or a fresh agent): walk the team’s part of the hierarchy, fetch the top processes, surface dependencies and recent changes. Ground the joiner in the team’s actual operational reality, not in generic role-based assumptions.

​
Prove control coverage

For audit-readiness questions (“where is control X supported?”, “what’s our evidence for policy Y?”), pull the relevant processes, surface the policies attached to the current version, and cite the supporting observations and activity timelines. get_attribute_configurations shows the workspace’s custom compliance attributes if the user asks about a specific control type.