# Golden trajectories vs audit logs | SourceX

Canonical: https://refer.sourcex.si/guides/golden-trajectories-vs-audit-logs
Last updated: 2026-11-04

Ordinary system logs record events: a timestamp, a severity, a message and some technical context. Audit logs add who changed which value. A golden trajectory records a whole task from goal to checked outcome, with each step and the reason for it. Logs can supply pieces of a trajectory, but they rarely say what the task was, why a step was taken, or whether the result was right. An introduction should establish which of those layers a company actually keeps.

## How do golden trajectories differ from ordinary system logs?

They answer different questions. A log answers "what did the software do, and when?" A golden trajectory answers "how should this task be done, step by step, and how do we know it was done right?"

The OpenTelemetry logs data model, a widely used standard for observability data, shows what a log record is built for. Its fields include a timestamp, trace and span identifiers, a severity, a body holding the message, attributes for structured context, and a resource describing the service that produced it. Every one of those fields describes the software's behavior. None describes the business task the software was serving.

A golden trajectory is built the other way around. Appen, one data services firm that produces them, describes golden trajectories as expert, step-by-step demonstrations of completing a task, with each step annotated with the reasoning behind it, and with several paths collected where more than one approach is valid. The unit is the task, not the event. If you want the definition in more depth, our guide to [golden trajectories in enterprise workflows](/guides/golden-trajectories-enterprise-data-referrals) covers it; this page is about telling the record types apart.

## The same ten minutes, recorded three ways (Illustrative)

A fictional 310-person regional logistics company receives an email asking it to change a carrier's bank details before the next payment run. An accounts payable specialist handles it. Here is what each kind of record would hold.

**System log** (the payments application):

| Time | Severity | Message | Context |
|---|---|---|---|
| 10:31:04 | INFO | GET vendor record | service: ap-portal, trace 7f3a |
| 10:42:17 | INFO | PATCH vendor bank details, status 200 | service: ap-portal, trace 9c11 |
| 10:42:18 | INFO | Webhook sent to ERP | service: integration, trace 9c11 |

**Audit log** (the ERP):

| Time | User | Object | Change |
|---|---|---|---|
| 10:42:17 | AP specialist | Vendor 882 | Bank account changed, old value masked, new value masked |
| 10:44:02 | AP manager | Vendor 882 | Change approved |

**Golden trajectory** (reconstructed from the ticket, call note and approval):

| Step | Action | Reason recorded | Check |
|---|---|---|---|
| 1 | Open the change request ticket | Email came from a domain not on file | Flagged as higher risk |
| 2 | Call the carrier on the phone number already in the vendor record | Never use contact details from the request itself | Carrier confirmed the change |
| 3 | Update bank details | Confirmation received | Audit entry created |
| 4 | Ask a second person to approve | Policy requires two people for bank changes | Manager approved |
| 5 | Watch the next payment run | Confirm funds reach the right account | A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.|

The system log proves an update happened. The audit log proves who made it and who approved it. Only the third table shows the task, the callback that made it safe, and the evidence that the outcome was correct. Notice also that the trajectory had to be assembled from a ticket, a call note and an approval, not from either log.

## What each record type can and cannot tell a buyer

| Question | System log | Audit log | Golden trajectory |
|---|---|---|---|
| When did something run? | Yes, to the millisecond | Yes | Yes |
| Who changed which value? | Sometimes, if the user is logged | Yes | Yes |
| Which business task was this part of? | Rarely, unless a ticket ID is logged | Sometimes | Yes, by definition |
| Why was each step taken? | No | No | Yes, recorded with the step |
| Was the outcome correct? | No | No | Yes, a check closes the path |
| Which steps were unnecessary? | No | No | Can be judged against the path |

The last row matters for evaluation. Step-level review, as Appen describes in its trajectory analysis service, labels each step of an agent's attempt as correct, suboptimal, incorrect or unnecessary. That kind of judgment needs a reference path to compare against, which logs alone do not provide.

For audit logging itself, including what an audit trail of AI tool access should capture, see our separate guide to [MCP audit logs](/resources/mcp/mcp-audit-logging).

## What a company introduction should establish

You are not deciding whether a company has golden trajectories. Very few businesses keep anything labeled that way. You are finding out whether its records hold the layers a trajectory needs, and whether they can be joined.

Ask, at metadata level only:

1. **Is there a task record?** Tickets, cases, requests or work orders that name the job being done.
2. **Do the logs carry the task's ID?** If audit entries reference the ticket or case number, the layers can be linked. If not, they are separate piles.
3. **Is reasoning ever written down?** Approval comments, call notes, resolution notes, policy references.
4. **Is there an outcome check?** A reconciliation, a customer confirmation, a QA review, a closed-and-not-reopened status.
5. **How far back does each layer go, and who owns it?** Logs often roll off in weeks; tickets may go back years.
6. **Who can authorize a licensing discussion?** The CEO (in an owner-run company, usually the owner), often advised by the COO or general counsel, not the IT team that holds the logs.

Our [company introduction record template](/resources/a-company-introduction-record-template) gives you a place to note the answers. The company must also meet the program basics: 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

## Limits and unanswered questions

- **No one can grade a trajectory from a phone call.** Whether a company's task records are complete enough is a question for SourceX's review with the owner.
- **SourceX licenses records; it does not build trajectories.** SourceX licenses approved business data directly from companies and manages the agreement, rights review, data preparation, delivery and payout. How a buyer uses licensed data is a matter for the buyer.
- **Security logs can be sensitive in themselves.** Some logs reveal infrastructure details that a company may decide never to license, and that is the company's call.
- **Company compensation is separate.** Whatever the company is paid is set in its own agreement with SourceX; your reward is funded separately and does not reduce it.

For related terms, see [what a golden dataset is](/questions/what-is-a-golden-dataset) and [agent trajectory data](/questions/agent-trajectory-data), or browse the [guides hub](/guides).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a company's tickets, approvals and audit entries share an ID and go back several years, that is worth an introduction: [register](/register), confirm the basics on [who qualifies](/who-qualifies), and read the [terms](/terms).

## Sources

- https://opentelemetry.io/docs/specs/otel/logs/data-model/
- https://www.appen.com/agentic-ai-golden-trajectories
- https://www.appen.com/agentic-ai-trajectory-analysis
- https://refer.sourcex.si/terms
