Repository navigation
How a call's key and a claim's number reach the server; a single-value item is the deciding agent's message - #18
Merged
Merged
Conversation
…is one value is the deciding agent's message The help for same-request-key: said the call's own place in the run is "sent to the server as the request's idempotency key" and left how to each host; claim-lasts: said nothing of when a claim is taken or of the number that makes a late write refusable. Agreed with Bud Agent Flow, which already sent the first in production: Idempotency-Key as a header on a url: tool and dev.pact/request-key in the request's _meta on a connected one; Pact-Fence with Pact-Claim, and dev.pact/fence with dev.pact/claim, for a claim taken from a store — both or neither, never as an argument. A claim is taken when the call is let through, after a person has said yes, and not while anybody is asked. PACT's reference harness records the token (Ledger.fences) and sends neither; a host does. rung.agent: an item that is one value and not a set of fields is the agent's message. A for-each over a list of texts handed the sorter the stage's says: and nothing about the text (workflow_runtime.given_to; found by Bud Agent Flow implementing the rule). Two shared cases in tests/conformance/workflows.json, on trees/sorted-notes. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows #17. Mostly words in the schema's help, plus one gap in
workflow_runtime.given_to.What a runtime must match
same-request-key: the-call): theIdempotency-Keyheader on aurl:tool;dev.pact/request-keyin the request's_metaon a connected one.Pact-FencewithPact-Claimon aurl:tool;dev.pact/fencewithdev.pact/claimin_metaon a connected one. Both or neither, only for a claim taken from a store, never as an argument. PACT's reference harness records the token (Ledger.fences) and sends neither; a host does.message. Afor eachover a list of texts handed the sorter the stage'ssays:and nothing about the text. Found by Bud Agent Flow while implementing the rule from Held to a second runtime: what reviewing Bud Agent Flow found in PACT, and the shared conformance cases #17.Agreed with Bud Agent Flow, which already sends
Idempotency-Keyin production.Checked
scripts/test-all.shexits 0: 4871 tests (1623 Rust + 3248 adapter), was 4869. Two new shared cases intests/conformance/workflows.jsonontests/conformance/trees/sorted-notes; no existing case'sexpectchanged.mkdocs build --strictbuilds.newest-pydantic-aifails onmasterwith the same five failures and is not touched here.🤖 Generated with Claude Code