This walkthrough demonstrates how TSMM semantics become executable Trust Infrastructure Schemas artifacts without losing governance meaning.
A relying-party verifier is asked to allow Example Agent Beta to submit a bounded status update. The verifier must not treat registry publication or identity-state evidence as automatic runtime authorization.
Use examples/cross-repo/trust-decision-system.graph.json to identify:
The sponsor-to-agent authority edge is projected into 01-authority-boundary.example.json. This constrains scope and requires revocation checks.
The evidence set is packaged in 02-evidence-bundle-manifest.example.json. This makes evidence replayable and auditable.
The verifier records assessment output in 03-evaluation-envelope.example.json. This captures controls checked, result, assurance level, semantic bindings, and authority boundary context.
The relying-party result is recorded in 04-decision-receipt.example.json. This is the audit pivot because it binds policy, authority, evidence, result, effect, and timestamps.
The discoverable registry state is published in 05-registry-entry.example.json. The entry makes the artifact chain discoverable but does not authorize future runtime action by itself.
The TIS repository validates the composition artifacts through tools/validate-conformance.js and the artifact coverage manifest. TSMM validates the graph and binding artifacts through the repository validation scripts.