Skip to content

feat(agent): add strict tool-state mode with isolated views and deterministic merges (T37) - #265

Open
XianReallyHot-ZZH wants to merge 3 commits into
agentic-ai-java:mainfrom
XianReallyHot-ZZH:feat/issue-140-strict-core
Open

XianReallyHot-ZZH wants to merge 3 commits into
agentic-ai-java:mainfrom
XianReallyHot-ZZH:feat/issue-140-strict-core

Conversation

@XianReallyHot-ZZH

Copy link
Copy Markdown
Contributor

确认 (Acknowledged) contribution to ARGI: add the opt-in strictToolState mode delivering read-only tool state views, patch+result update units with a hard failure-discard rule, KeyStrategy-honoring sequential merges, and strategy-explicit conflict handling for parallel merges across the graph and ReAct paths as the second T37 slice for #140.

Opt-in strictToolState on the graph path: tools receive a read-only
state view (store preserved), failed calls never contribute state via
the shared StrictPatchAdmission, sequential merges go through the
declared KeyStrategies via a shared mergeEntry, and parallel merges
enforce declared-strategy rules for every conflicting key before
mergeAll. Default off: legacy behavior pinned by tests.

Refs agentic-ai-java#140
Opt-in strictToolState on the independent ReAct path: tools receive a
read-only view of the invocation state (writes escape only through the
patch channel) and the shared StrictPatchAdmission enforces the hard
failure-discard rule plus policy validation. Sequential merging stays
last-write-wins by design - documented in the builder javadoc - since
the ReAct state is invocation-local and execution is sequential.

Refs agentic-ai-java#140
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant