Wherever it comes from
One service returns one thing and the next returns something different for the same thing. Making the agent learn both shapes is work that adds nothing.
How it works
One request, start to finish
An agent needs something: a figure, a memory, a tool. What happens between asking and receiving is everything TRACE does — and it is more interesting than it sounds.
Identifies itself · crosses · gets recorded
The path
Four moments, always the same ones
01
It identifies itself
The request arrives with the coordinate of whoever made it. Not paperwork: it is what makes it possible to answer, months later, who asked for this.
02
It crosses the door
One credential and one place to pass through. On the other side there are not twenty different connections, there is one.
03
It gets resolved
The door knows which service it belongs to and in what shape to return it. The agent does not need to know where each thing lives.
04
It gets written down
What was asked, by whom, when and with what result. Without the agent having to bother: if writing the trail were its job, one day it would stop doing it.
What the door does
Receive, filter, normalise, route
Four verbs that sound like little and are almost everything. None of them decides anything for the agent — they sort what the agent will use to decide.
Almost nothing deserves keeping
The temptation is to keep it all just in case. A few months later, searching for anything returns thirty similar results and nothing decisive.
One way of saying the same thing
What leaves here is understood by any agent in the system, including one written six months from now that never saw the source service.
Each thing to its place
Today's state does not go where the log goes, and neither goes where signed doctrine goes. Routing well is what makes retrieval fast.
What goes away
Problems that stop existing
01
Rotating a credential stops being scary
It is in one place. You change it and that is it. Without that single place, changing it means discovering by trial and error how many agents were using it.
02
A changing contract does not break things blindly
When a service changes shape, it gets absorbed at the door. The agents consuming it never find out, which is exactly what they should do.
03
Nobody connects on their own
If a capability is not behind the door, it does not get improvised outside: it gets brought in. Today's shortcut is an invisible piece forever.
04
The system can be audited
Not because someone remembers to write things down, but because the trail writes itself. Human memory is not a compliance strategy.