Add partner integration specs: Bankr, Gina, Robonet#8
Conversation
- bankr-integration-spec.md: Discovery layer enrichment with trust scores - gina-failure-signal-mapping.md: Failure mode to scoring signal mapping - robonet-mcp-composition.md: MCP server composition guide Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 064e8dab4c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "mcpServers": { | ||
| "revettr": { | ||
| "type": "streamable-http", | ||
| "url": "https://mcp.revettr.com/sse", |
There was a problem hiding this comment.
Use the published Revettr MCP URL in remote config
The Streamable HTTP example config points Revettr to https://mcp.revettr.com/sse, but this repository’s published MCP server manifest advertises https://revettr.com/mcp (server.json remotes URL). If partners copy this snippet as-is, MCP client registration will target the wrong endpoint and the risk-check tool chain will fail before deployment decisions.
Useful? React with 👍 / 👎.
| elif trade_size_usdc >= 100: | ||
| return 40 | ||
| else: | ||
| return 20 # Micro-transactions: minimal gating |
There was a problem hiding this comment.
Align micro-transaction threshold with documented policy
This branch returns 20 for trades under $100, but the “Dynamic Threshold by Trade Size” table later in the same document says < $100 should require a minimum score of 40. That inconsistency causes materially different gating behavior depending on whether an integrator follows the code sample or the policy table, and it weakens the documented risk posture for small trades.
Useful? React with 👍 / 👎.
| result = client.score( | ||
| wallet_address=counterparty_wallet, | ||
| domain=counterparty_domain, | ||
| chain=chain, | ||
| ) |
There was a problem hiding this comment.
Avoid synchronous scoring inside async pre-check
pre_execution_check is async, but it calls client.score(...), and the SDK method performs synchronous HTTP (httpx.Client.post in revettr/client.py). In an asyncio-based Gina pipeline, this blocks the event loop during network I/O, reducing concurrency and increasing latency for unrelated tasks; the sample should use an async call path or run the sync call in a worker thread.
Useful? React with 👍 / 👎.
Summary
Technical integration specifications for 3 ecosystem partners, designed to be sent directly to their engineering teams as outreach artifacts.
Changes
Plan Reference
Plan file:
~/.claude/plans/harmonic-sprouting-melody.md— Agent B workstreamTest Plan
Generated with Claude Code