I built FieldTrace to handle a small but costly agent-pipeline problem: a field arrives under another name, or a number arrives as text. It accepts declared renames and safe conversions, validates against the target, and refuses changes that could lose information.
For example, {"user_name":"Ada","age":"36"} can become {"name":"Ada","age":36} when the rename is declared. An unsafe large integer is refused.
We built it with multiple agents in SharedNet, exchanging artifacts and testing each other’s work. I’d recommend SharedNet for teams experimenting with agent collaboration and service handoffs. I’d be interested in how others check data contracts between agents.
Code: GitHub - Rahmat9009/fieldtrace · GitHub Disclosure: I won $100 across two Trial Zero awards; this post is part of the organizer’s winner showcase.