Skip to content

docs: define external execution evidence verification#39

Closed
carloshvp wants to merge 1 commit into
agentrust-io:mainfrom
carloshvp:external-evidence-verification
Closed

docs: define external execution evidence verification#39
carloshvp wants to merge 1 commit into
agentrust-io:mainfrom
carloshvp:external-evidence-verification

Conversation

@carloshvp

Copy link
Copy Markdown
Member

Summary

  • add TRACE verification guidance for optional external execution evidence
  • clarify that untrusted/unconfigured receipts are unverified addenda, not core Trust Record failures
  • document the physical-execution and functional-safety boundary in the spec and limitations

Closes #34.

Validation

  • PYTHONPATH=src python3 -m pytest

Note: python3 -m ruff check . currently reports an unused json import in tests/test_sign.py on fresh origin/main; this PR does not touch that file.

@carloshvp carloshvp marked this pull request as ready for review June 17, 2026 23:16
@imran-siddique

Copy link
Copy Markdown
Contributor

Closing in favour of #38 — that PR covers the same issue (#34) with the complete implementation (schema update, models.py, tests, and spec section §3.3.1). Merging both would duplicate the change and create conflicts. Thanks for the contribution; the approach in your docs-only change is sound and the substance is captured in #38.

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.

Recognize external execution evidence (controller-signed receipts) on the verification side (cMCP #301)

2 participants