[ogasurfproject-jpg]

Adds integrations/horizonshield-musubi-trace-terms/, community tier, as described in agentrust-io discussion #66.

What it is: musubi-trace-terms-v0 reads PIC/TRACE authorizations and Trust Records unchanged and judges them against a contract and terms two parties signed, per call and overall (within_terms, outside_terms, undetermined, refused). Each authorization is checked by agentrust-trace's own intent_bridge.verify_bridge.

• Pinned to agentrust-trace==0.11.0 (tested_against). The 55 vectors run under pytest.
• The README notes that the JSON Schema in agentrust-trace 0.11.0 is older than trace-spec main (Implementation report: six verifiers written from the v0.2 text alone, run over 2,816 inputs (four findings) trace-spec#591); every result here is against the 0.11.0 release.
• Role record-consumer, Level 0, meaning only this: the two Trust Records the vectors consume unchanged (from agentrust-io/trace-registry, CC BY 4.0, attributed in NOTICE) pass trace-tests verify --level 0 with agentrust-trace-tests 0.6.2, which the tests run. It emits no Trust Record. If you would classify it differently, tell me and I will change the manifest.
• .github/workflows/horizonshield-musubi-trace-terms-conformance.yml: fixed (tested_against) and floating (latest releases), Python 3.11 to 3.13, on changes and weekly.
• The vendored files are byte for byte horizon-shield at 05b4924 (SHA-256 in the README, checked by a test). License MIT.

Run locally: pip install -e "integrations/horizonshield-musubi-trace-terms[test]" && pytest integrations/horizonshield-musubi-trace-terms/tests -q gives 75 passed (Python 3.11, 3.12, 3.13 and 3.14). validate_integrations.py, the index and catalog checks, the ruff gate and actionlint pass.

[github-actions]

🔴 Contributor Check: HIGH

Check	Result
Profile	HIGH
Credential	LOW
Overall	HIGH

Automated check by AgenTrust Contributor Check.