Skip to content

docs: add ScopeBlind integration guide (signed decision receipts for tools)#1548

Closed
tomjwxf wants to merge 1 commit intokyegomez:masterfrom
tomjwxf:docs/scopeblind-integration
Closed

docs: add ScopeBlind integration guide (signed decision receipts for tools)#1548
tomjwxf wants to merge 1 commit intokyegomez:masterfrom
tomjwxf:docs/scopeblind-integration

Conversation

@tomjwxf
Copy link
Copy Markdown

@tomjwxf tomjwxf commented Apr 20, 2026

Summary

Adds an integration guide at docs/integrations/scopeblind.md for scopeblind-swarms — a Python package that wraps any Swarms tool with Ed25519-signed, tamper-evident, offline-verifiable decision receipts in the Veritas Acta format.

The same receipt format is used by:

15 implementations in total on the draft-02 IETF Implementation Status appendix. This PR brings Swarms into that cross-verifying ecosystem.

What's in the PR

Doc-only. One new file: docs/integrations/scopeblind.md. No changes to Swarms core or to any existing file.

The guide covers:

  • One-liner install (pip install scopeblind-swarms swarms)
  • Quick start (3 code blocks: create chain, wrap tool, use in Agent)
  • Receipt payload shape (tool_name, action_ref, result_hash, policy_id, previousReceiptHash, Ed25519 signature)
  • Offline verification (npx @veritasacta/verify receipt.json --key operator.pem)
  • Composition with other ecosystem components (sandbox backends, policy engines, transparency logs)
  • Thread-safety note for async Swarms agents

Design note on the extension point

Swarms does not expose pre/post tool hooks. The canonical interception point per upstream guidance (BaseTool's _execute_single_function_call discussion in existing tool docs) is wrapping the tool callable before passing it to Agent(tools=[...]). scopeblind-swarms uses that extension point exactly; it does not patch Swarms internals, subclass Agent, or modify any Swarms code path.

Related

Test plan

  • Markdown renders correctly (local preview)
  • All cross-links resolve
  • Python examples are copy-pasteable and match the installed scopeblind-swarms@0.1.0 API
  • Companion package has 17/17 tests passing (receipt signing, chain linkage, tamper detection, thread-safety under concurrent signing, decorator form, bulk wrapping, embedded-key rejection)

Cc @kyegomez — the receipt-layer primitive composes cleanly with existing Swarms tool machinery. Happy to iterate on scope, style, or framing if there's anything you'd like adjusted. The only ask is a doc link; the adapter itself lives on PyPI and the ScopeBlind monorepo, not in swarms-core.


📚 Documentation preview 📚: https://swarms--1548.org.readthedocs.build/en/1548/

… Swarms tools

Adds docs/integrations/scopeblind.md documenting how to wrap Swarms
tools with Ed25519-signed decision receipts via the scopeblind-swarms
Python package (pip install scopeblind-swarms).

Receipts use the Veritas Acta format (draft-farley-acta-signed-receipts
IETF Internet-Draft), the same envelope used by Microsoft Agent
Governance Toolkit, protect-mcp, sb-runtime, hermes-decision-receipts,
and Signet. Any Swarms operator can now produce tamper-evident,
offline-verifiable audit trails of every tool their agents call,
with no fork of Swarms required.

Design note inlined in the doc: Swarms does not expose pre/post
tool hooks; the canonical interception point per upstream guidance
is wrapping the tool callable before passing it to Agent(tools=[...]).
scopeblind-swarms uses that extension point exactly; no patches to
Swarms internals.

No changes outside docs/integrations/scopeblind.md.
@github-actions
Copy link
Copy Markdown

Hello there, thank you for opening an PR ! 🙏🏻 The team was notified and they will get back to you asap.

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Apr 20, 2026
@kyegomez kyegomez closed this Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants