Skip to main content
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.

​
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

1

Confirm the workspace

Call list_accessible_workspaces and switch if needed.
2

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.
3

Place it in context

Call get_hierarchy_node_details — parent value stream, sibling processes that may share patterns.
4

Read recent changes

Call get_recent_process_changes — version evolution. What has the team been changing? In which direction?
5

Read all observations

Call get_process_observations across versions. Look for repeated deviation patterns, exception types, manual workarounds.
6

Drill into representative timelines

For three to five representative observations, call get_observation_citation — primary-source detail of how the process runs in practice (not how it’s documented).
7

Walk the dependency graph in the index

The dependencies field on get_process_details lists the upstream and downstream processes by ID. For each one, fetch the process, then call get_process_details for the full payload. Read its steps, its own dependencies, and its recent observations.Repeat for as many hops as the thesis needs:
  • Upstream: what feeds this. Root cause / input quality matters for transformation viability.
  • Downstream: blast radius if we change it. Surfacing this early prevents under-scoped proposals.
For high-impact transformation theses, drill the most-affected dependencies one more level — call get_process_observations and get_observation_citation on the dependencies whose behavior shapes your conclusions.
8

Cross-check sibling processes

From the get_hierarchy_node_details payload returned earlier, fetch two or three sibling processes under the same value stream. If they share patterns, controls, or systems with the target, the transformation thesis may need to address them too.
9

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.