Every consequential output needs source, time, inputs, transformation, and authorization context.
Why this question matters
Structured outputs improve interoperability, but structure is not provenance. A price quote, identity lookup, or policy decision may be copied into an A2A artifact and later summarized into memory. Each transformation can remove caveats or freshness constraints.
Provenance should remain referenceable without forcing every agent to receive sensitive raw data. A downstream system can validate the source and relevant conditions, then request re-execution when freshness or audience no longer fits.
Signals worth observing
- Outputs circulate without timestamps or originating tool identity.
- Summaries omit confidence, scope, or policy constraints.
- Several agents reuse one result for different principals.
Practical control direction
- Attach immutable source and transformation references.
- Define freshness and audience requirements by output type.
- Re-run high-impact checks at the point of action.
AgentCollusion lensProvenance makes it possible to detect when agents coordinate by recycling the same hidden signal.
