> For the complete documentation index, see [llms.txt](https://tracdeepdive.gitbook.io/deepdive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tracdeepdive.gitbook.io/deepdive/overview/supply-chains/oracle.md).

# Oracle

Oracle and OriginTrail partnered up back on Dec. 8th, 2018. As posted by Oracle [tweet](https://twitter.com/orclblockchain/status/1070678005763190784?lang=ar): “***We are thrilled to partner w/@origin\_trail** to deliver secure and trusted data sharing for supply chains using #blockchain technology*.”

This solution is related to Automatic Dairy payments. What this is and how it functions can be seen in the video below, and more recently this [article](https://twitter.com/SmartAgriHubs/status/1458414682134523909) by SmartAgriHubs.

{% embed url="<https://www.youtube.com/watch?v=9-XucYs9FIM>" %}

You can also watch Jens Lusebrink from Oracle [during the Liftoff event](https://youtu.be/UfRWKTKJOFU), where Dan Purtell from BSI was also present, explaining their involvement with Trace Labs creating solutions on the ODN.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tracdeepdive.gitbook.io/deepdive/overview/supply-chains/oracle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.