Technical authority

What AI agent trajectory data is

Last updated November 1, 2026/Reinforcement learning environments

AI agent trajectory data is a record of work in the order it happened. Something was true. Someone, or some system, took an action. The world answered. That triple can repeat until the job ends or stalls. The order is not decoration. Drop it and you have a bag of events that no longer shows which move followed which situation. Keep it and you have a trajectory: a path an agent might later be asked to imitate, to avoid, or to be graded against.

A logistics desk produces this shape without setting out to. A load is late. The dispatcher sees the appointment window and the equipment on the board. They reassign, or they refuse the reassignment, and a later status says the freight moved, sat, or was refused. The path from the late signal to the decision to the status is a trajectory of dispatch. It is not a map of where a driver slept, and it is not automatically something the carrier may offer. What a logistics company already generates that can train AI stays on that trade. This page stays on the shape of the record.

A trajectory is not an environment. An environment is a task you can reset and check. The pillar page, what reinforcement learning environments need from real work, draws that line. How a named business process becomes such a task, if it ever does, is how a business workflow becomes a checkable training environment. The clicks inside the path, as distinct from the path itself, are why records of software tool use matter to agents. Whether the underlying workflow can be licensed at all is how workflow and process records can be licensed.

Why order is the part a summary throws away

A case study says the shipment was saved. The trajectory says the first idea was rejected, the second tool returned a full dock, and only the third move cleared the window. An agent that only reads the case study learns the boast. An agent that can read the path can see the rejected move. Builders ask for trajectories when the rejected move is the lesson. They are not asking for a larger folder of final PDFs.

Business software often keeps the path by accident. A ticket system stores comments in time order. A dispatch board stores status changes. A maintenance log stores tests in the order the technician ran them. Accident is not the same as completeness. If the meaningful action happened on a phone call that nobody wrote down, the stored path is a skeleton. Say so. Do not invent the missing step so the trajectory looks finished.

What has to be in the path before it is worth describing

• A situation the actor could actually see. If the record only stores the hidden truth after the fact, it is a scoreboard, not what the person acted on.
• An action that changed something: a reassignment, a setting, a reply, a hold. A heartbeat or a login is a weak action.
• What came back, soon enough that a reader can tell it followed the action. A status written the next week with no link is a rumor.
• An ending or a stall that is explicit. Trajectories that simply stop mid-gesture are hard to learn from and easy to misread.

What a trajectory is not

It is not a license. A clean path can still belong to a customer, a shipper, or a vendor whose terms forbid reuse. It is not a chat log unless the chat preserves the actions and the observations, not only the polished sentences. It is not a permission to include a person's continuous location, a password, or a payment instrument that happened to sit on the same row. Those fields can be cut, or the whole path can be left out. Cutting them is not, by itself, proof you may offer what remains. This page is not legal advice.

What breaks the path

• Reordered exports. If the system dumps rows without a reliable time or sequence, the trajectory is already gone.
• Three copies of the same job from a portal, a carrier system, and a broker board, presented as three paths.
• A final report that replaced the steps. The outcome survived and the actions did not.
• Secrets pasted into the comment that carried the action. The comment may have to be dropped, and with it the only statement of what was done.
• A claim that every industry log is a trajectory. Some are. Many are status slogans. The difference is visible only in the record, not in the industry label.

How a path is described without becoming our copy

Big Data/Little Guy is operated by Unlockt, LLC. We do not collect a live feed in order to call it a trajectory. The free check can establish whether ordered actions and outcomes exist. It does not upload the board. The check itself is a short form that does not move your files.

A profile, if one is written, can say that ordered operational paths exist, in which kinds of work, with which limits already known. A buyer would see that description. Defining a task on top of a path is a later, optional design, and only on a slice you approve. Most conversations should end before that design. A glossary of the nearby words is plain definitions for AI data licensing terms.