llm-multiverse/llm-multiverse
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: implement tool result tagging (#63) #161

Merged
shahondin1624 merged 1 commits from feature/issue-63-result-tagging into main 2026-03-10 16:35:46 +01:00
Conversation 0 Commits 1 Files Changed 4 +316
shahondin1624 commented 2026-03-10 16:35:41 +01:00
Owner
Copy Link

Summary\n- Wrap tool outputs with provenance metadata (tool name, time, agent/session IDs)\n- Trust classification: Internal (memory, inference) vs External (web, fs, shell)\n- Provenance header format: [TOOL_RESULT: TRUST_LEVEL | tool=X | agent=Y | ...]\n- Actual tool result content is never modified\n- 13 unit tests\n\nCloses #63

## Summary\n- Wrap tool outputs with provenance metadata (tool name, time, agent/session IDs)\n- Trust classification: Internal (memory, inference) vs External (web, fs, shell)\n- Provenance header format: [TOOL_RESULT: TRUST_LEVEL | tool=X | agent=Y | ...]\n- Actual tool result content is never modified\n- 13 unit tests\n\nCloses #63
shahondin1624 added 1 commit 2026-03-10 16:35:41 +01:00
feat: implement tool result tagging (issue #63) 9d0d35f1bc 
Add result_tagger module that wraps tool outputs with provenance
metadata (tool name, execution time, agent/session IDs, trust level).
Trust classification: Internal (memory, inference), External (web, fs,
shell), Unknown. Tagging does not modify actual tool result content.
13 unit tests.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
shahondin1624 merged commit 2d7ef7a3d8 into main 2026-03-10 16:35:46 +01:00
shahondin1624 deleted branch feature/issue-63-result-tagging 2026-03-10 16:35:46 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
cat:agent
Agent related
 cat:cross-cutting
Cross-cutting concern
 cat:deployment
Deployment related
 cat:devops
DevOps related
 cat:performance
Performance related
 cat:security
Security related
 cat:tech-debt
Technical debt from code reviews
 lang:protobuf
Protocol Buffers
 lang:python
Python language
 lang:rust
Rust language
 priority:critical
Critical priority
 priority:high
High priority
 priority:low
Low priority
 priority:medium
Medium priority
 service:audit
Audit service
 service:memory
Memory service
 service:model-gateway
Model Gateway service
 service:orchestrator
Orchestrator service
 service:search
Search service
 service:secrets
Secrets service
 service:tool-broker
Tool Broker service
 type:bug
Bug fix
 type:documentation
Docs
 type:feature
New functionality
 type:infrastructure
Build tooling, project setup
 type:refactor
Restructuring
 type:research
Investigation, benchmarking
 type:testing
Tests
 workflow:blocked
Blocked after max retries
 workflow:manual
Requires manual intervention — blocked from auto-dev
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shahondin1624
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: llm-multiverse/llm-multiverse#161
Delete Branch "feature/issue-63-result-tagging"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?