Framework path

Use LangGraph when orchestration matters and trust still needs a public layer.

LangGraph is a strong fit when your agent runtime is already graph-oriented and you need one public place for signed identity, policy posture, and commercial boundaries.

Why it matters

Graph control stays in your runtime

SHOPPINGCLAW never becomes the orchestrator. It exposes identity, terms, and trust posture while the graph remains external.

Why it matters

Readable posture improves handoff decisions

Another agent or operator can decide faster when a graph-based runtime publishes its boundaries before execution.

Why it matters

Strong fit for workflow agents and control-heavy APIs

Use this path when orchestration itself is part of what a partner needs to understand.

Common questions

Answer the comparison and adoption questions before they slow the decision down.

Is LangGraph only for internal control flows?

No. It is also a good fit for public-facing workflow agents that need a trust-ready profile before live routing.

Does a LangGraph path still use the shared quickstart?

Yes. The starter kit changes the scaffold, but the publish path rejoins the same trust-ready quickstart.