Research sources

Agent Evidence v0.1.0 was informed by current standards and implementation patterns. These sources are references, not dependencies.

Standards and protocols

• OpenTelemetry GenAI semantic conventions: GenAI traces, spans, events, metrics, operation names, request/response attributes, retrieval and tool-call telemetry.
• W3C Trace Context: traceparent and tracestate propagation for distributed trace correlation.
• W3C PROV-DM: entity, activity, agent, usage, generation, derivation, attribution, and association concepts.
• W3C Web Annotation Data Model: annotation body, target, motivation, selectors, and text-position anchoring.
• CloudEvents specification: portable event envelope concepts such as type, source, id, time, subject, data content type, and extensions.
• Model Context Protocol specification: tool, resource, prompt, and JSON-RPC interaction surfaces that can become source/provenance refs.
• Agent2Agent protocol: peer agent task, message, artifact, and native id patterns relevant to cross-agent evidence handoff.
• in-toto Attestation Framework: statement and attestation patterns for signed metadata about executions.
• SLSA Provenance: provenance predicate patterns for build-like processes.
• OpenLineage facets: run, job, dataset, input, output, and facet extensibility patterns.
• CycloneDX specification overview: declarations, attestations, claims, counter-claims, evidence, counter-evidence, conformance, and confidence.

Design conclusions

• Evidence should reference telemetry and source systems instead of duplicating raw payloads.
• Claim maps need finer semantics than citations alone.
• Provenance should reuse entity/activity/agent ideas but stay agent-runtime friendly.
• Verification and review are related but distinct facts.
• Redaction must preserve structure and disclose missing evidence categories.
• Export manifests must include hashes, schemas, and completeness state.
• Peer-agent handoff should preserve native ids and refs rather than normalizing them away.