# Call-Level Revision Contracts for LLM-Authored Workflows

DevFeed: [Call-Level Revision Contracts for LLM-Authored Workflows](<https://devfeed.tech/articles/call-level-revision-contracts-for-llm-authored-workflows-120803.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.06967>)

Author: Chenyang Jiang, Benyang Pan, Puqu Wu

Published: 2026-11-06T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Advanced AI workflows](<https://devfeed.tech/topics/advanced-ai-workflows.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [call hierarchy](<https://devfeed.tech/topics/call-hierarchy.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [call](<https://devfeed.tech/tags/call.md>), [change](<https://devfeed.tech/tags/change.md>), [container](<https://devfeed.tech/tags/container.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customer-support](<https://devfeed.tech/tags/customer-support.md>), [digest](<https://devfeed.tech/tags/digest.md>), [durable-execution](<https://devfeed.tech/tags/durable-execution.md>), [engines](<https://devfeed.tech/tags/engines.md>), [execution](<https://devfeed.tech/tags/execution.md>), [expression](<https://devfeed.tech/tags/expression.md>), [failed](<https://devfeed.tech/tags/failed.md>), [gate](<https://devfeed.tech/tags/gate.md>), [history](<https://devfeed.tech/tags/history.md>), [llm](<https://devfeed.tech/tags/llm.md>), [revision](<https://devfeed.tech/tags/revision.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

## AI overview

The revision contract aims to let models repair failed workflows without repaying successful calls or silently reusing results whose payloads changed. It identifies each capability call by callsite, fanout position, and occurrence count; a static gate rejects changes to committed calls before execution, while a runtime digest catches changed payloads and an occurrence ledger tracks repeated paid payloads. The call expression is frozen, but surrounding orchestration code can change. Under three assumptions, accepted repairs replay invoked committed calls, run only new work, and report skipped identities. The abstract reports 22 media-workflow repairs replaying 258 committed identities without duplicates, and a live six-way fanout costing seven calls instead of twelve; a 12-task customer-support study used the same checks on two models. Relocating a call can trigger a pre-spend stop because no local identity is both relocation-invariant and free of wrong reuse.

## Source excerpt

arXiv:2611.06967v1 Announce Type: new Abstract: Durable execution engines replay a recorded history and do not compare activity payloads. When a model repairs a workflow that failed partway through, it must either pay again for calls that succeeded or accept a recorded result whose payload changed. We define a revision contract for workflows whose orchestration code is written by a model. Each capability call carries a structural identity built from its callsite, its fanout position, and its occurrence count, and the identity stays stable under rewrites that leave the call in place, so committed identities form a frozen prefix. The frozen unit is the call expression, and the surrounding code stays writable. A static gate rejects a rewrite that would change a committed call before a container starts. A runtime digest stops a changed payload at a committed identity, and an occurrence ledger names a repeated paid payload. Under three assumptions, a candidate the gate accepts replays every committed call it invokes, executes only new work, and reports the identities it skips. No local identity is both relocation-invariant and free of wrong reuse, so callsite identity turns a relocation into a pre-spend stop. On media workflows, 22 gate-passed repairs replay 258 committed identities with no duplicate, and a live six-way fanout makes seven paid calls instead of twelve. A 12-task customer-support study applies the same identity, replay, and boundary checks on two models.