The user has zeroed in on a target process or value stream and wants the assistant to build a deep, evidence-grounded transformation thesis before recommending changes.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.
Example prompts
- “Build a transformation thesis for our order-to-cash process.”
- “We want to redesign vendor onboarding — give me current state, blast radius, and intervention points.”
- “If we deprecate System X, what breaks?”
End-to-end recipe
Confirm the workspace
Call
list_accessible_workspaces and switch if needed.Pull the target process
Call
search → fetch, or fetch directly if the ID is known. Then get_process_details for the full nested payload: current version, dependencies, hierarchy node, version history.Place it in context
Call
get_process_hierarchy_node_details — parent value stream, sibling processes that may share patterns.Read recent changes
Call
get_recent_process_changes — version evolution. What has the team been changing? In which direction?Read all observations
Call
get_process_observations across versions. Look for repeated deviation patterns, exception types, manual workarounds.Drill into representative timelines
For three to five representative observations, call
get_observation_activity_timeline — primary-source detail of how the process runs in practice (not how it’s documented).Map upstream and downstream
get_upstream_sources— what feeds this. Root cause / input quality matters for transformation viability.get_downstream_dependencies— blast radius if we change it. Surfacing this early prevents under-scoped proposals.
Walk the surrounding network
search_knowledge_graph— find entities (systems, teams, controls) that touch this process.get_entity_details— read the most-connected entities as transformation surfaces.explore_graph_neighbors— map the network.summarize_community_subgraph— orient if the process sits in a meaningful community.
Build on prior Advisor work
Call
list_objective_findings. If there’s prior thinking on this process or value stream, call get_objective_context_bundle to load it and build on it. Don’t restart cold.Produce the visual (optional)
Call
generate_process_diagram to produce a current-state diagram for the thesis document.Synthesize the thesis
Structure the answer as:
- Current state: how the process actually runs (cite observations).
- Blast radius: upstream feeders and downstream dependents.
- Pain pattern: the deviation, manual, or duplication signal — with evidence.
- Intervention points: where to change, ranked by leverage and risk.
- Open questions: what evidence is missing that would strengthen or invalidate the thesis.