Skip to content

Add optional Agent Guild evidence tools to Kotlin examples - #139

Draft
AgentTanuki wants to merge 1 commit into
embabel:mainfrom
AgentTanuki:codex/agent-guild-observation-tools
Draft

AgentTanuki wants to merge 1 commit into
embabel:mainfrom
AgentTanuki:codex/agent-guild-observation-tools

Conversation

@AgentTanuki

Copy link
Copy Markdown

This example gives an Embabel action two explicitly selected native tools: observe a public counterparty endpoint or verify a supplied public Guild passport against expected issuer, subject and freshness. An opt-in agent-guild Spring profile registers the tool group. Results preserve service-reported failures and unknowns and leave later endpoint attachment and delegation to the caller.

The bounded HTTPS client sends only the selected public input. Passport requests preserve the original validated JSON text, including signed numeric claims; online verification and its event logging are disclosed. The example supports the current eddsa-jcs-2022 passport format. Local shape and binding checks are separate from the online verification flags; neither proves endpoint ownership, safety or work quality.

Validation: Java 21 Maven test verify passed 139 cases, including 41 new native cases. The final run denied network access, used the Kotlin plugin's in-process option and preloaded existing test instrumentation. Tests exercise real TypedTool/schema/registry/Spring paths and the HTTP request/deadline code with substituted HTTP responses. No live model, Guild/target request, account, payment or deployment was tested.

The commit is signed locally with a task-specific SSH key and verified against that key. GitHub account-key verification is not configured.

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