Preserve workflow context for admitted LLM tool writes - #580
Merged
Conversation
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
1 participant
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.
Durable LLM steps lost their workflow and state metadata when constructing the internal tool loop. Ontology writes consequently arrived as unlabelled agent effects and failed with
ontology_agent_delegation_required, despite being admitted by the workflow mutation ceiling.Preserve the trusted workflow context and use the existing workflow ontology invocation binder after tool admission. Each LLM tool call gets a distinct effect identifier. Canonical live actor/target/scope checks and denied-write gates remain in force.
Validation: 164 targeted workflow and ontology-authority tests passed, including metadata propagation, distinct effect IDs, denied-call non-execution, cross-context authority checks and reserved-governance checks. One unrelated pre-existing advisory-versus-hard-timeout fixture was deselected. Real slideshow workflow replay follows activation.