ContractSpec docs

OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

graph.suggest_evolution — proactive graph evolution suggestions

Ranks structural and semantic improvement suggestions for a graph: missing reviewer, missing retry, weak path, isolated node, naming inconsistency, missing feedback loop, circular dependency, high fan-out. Budget: 2 500 in / 1 000 out / $0.028.

field.key.label
graph.suggest_evolution — proactive graph evolution suggestions
field.version.label
field.type.label
field.title.label
graph.suggest_evolution — proactive graph evolution suggestions
field.description.label

Ranks structural and semantic improvement suggestions for a graph: missing reviewer, missing retry, weak path, isolated node, naming inconsistency, missing feedback loop, circular dependency, high fan-out. Budget: 2 500 in / 1 000 out / $0.028.

field.tags.label
automation,agent,execution,graph,ai,evolution,suggestions,m5
field.owners.label
field.stability.label
public

Analyses the current graph and returns ranked proactive improvement suggestions. Suggestions are **read-only** — nothing is applied automatically.

Suggestion kinds

| kind | Description | |---|---| | `missing_reviewer` | A node or flow has no assigned reviewer / approval step | | `missing_retry` | An error path has no retry or back-off edge | | `weak_path` | A critical path has only one route (no redundancy) | | `isolated_node` | A node has neither incoming nor outgoing edges | | `naming_inconsistency` | Labels diverge from the dominant naming style | | `missing_feedback_loop` | A workflow has no feedback or notification branch | | `circular_dependency` | A cycle exists that may indicate a design issue | | `high_fan_out` | A node has an unusually large number of outgoing edges |

focusArea

Narrow the scan to reduce cost and noise:

`"reliability"` — retry, redundancy, failure-path coverage

`"coverage"` — reviewer presence, approval steps, feedback loops

`"connectivity"` — isolated nodes, weak paths, high fan-out

`"naming"` — label consistency

`"all"` — full scan (default)

Acting on suggestions

Each suggestion includes a `suggestedFix` string. Pass that text back to `graph.edit` or `graph.compose` to apply the fix after confirming through the AI suggestion UX (W7.4).

Budget (M5 P2/W2.4)

maxInputTokens=2 500 · maxOutputTokens=1 000 · hardCapUsd=$0.028