The docs show Graph Compose has DAG execution, conditions, polling, timeouts, retries, and error boundaries. That is exciting for enterprise action workflows, b

The docs show Graph Compose has DAG execution, conditions, polling, timeouts, retries, and error boundaries. That is exciting for enterprise action workflows, but we would want Konekti to remain the semantic brain: process definitions, business rules, evidence, health, and process correctness should live there. Where do you draw the product boundary? What kinds of logic should absolutely stay outside Graph Compose, especially when the upstream system is a semantic process platform like Konekti rather than just a simple API?