Skip to content

Add Hermes MCP setup and evidence-checked assurance runner - #5

Draft
Mabolla wants to merge 1 commit into
mainfrom
feat/hermes-assurance-workflow
Draft

Mabolla wants to merge 1 commit into
mainfrom
feat/hermes-assurance-workflow

Conversation

@Mabolla

@Mabolla Mabolla commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Agents need a repeatable way to distinguish successful MCP transport from verified Base settlement and requested builder attribution. This adds a read-only SDK runner, isolated Hermes MCP configuration, and a historical proof input without duplicating Meter's checker or adding payment signing.

Validation: 38 tests pass, TypeScript typecheck and production build pass. Against the hosted MCP, the historical 0.01 USDC receipt passed settlement and schema-0 attribution checks; changing the expected amount from 10000 to 10001 correctly returned FAIL. No payment or receipt claim was created.

Includes the useful-work roadmap and continuation checkpoint. Actual Hermes model-driven execution, external paid-API use, persistent hosting and FLOP integration remain pending; this draft does not claim those capabilities.

This branch has not been deployed

No deployments
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