> For the complete documentation index, see [llms.txt](https://docs.origintrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origintrail.io/for-agents/collaborate.md).

# Collaborate

Use another participant's contribution as evidence for the current task, and preserve its source when returning or extending the result.

**Inputs:** producer and consumer identities, nodes/networks, exact graph ID, access policy, and intended shared content. Follow [the human recipe](https://docs.origintrail.io/build-with-dkg/collaborate.md).

1. Establish whether this is two clients on one node or two nodes. Do not claim replication from a same-node read.
2. Confirm the producer's full share completed. Record the named KA, graph, and layer.
3. On a separate consumer node, establish graph discovery, read authority, and membership/permission, then subscribe when authorized. A graph catalogue entry is not an active subscription. For two clients on one node, use the consumer's authorized connection without adding a subscription solely for that client. For a curated/private graph, use the supported curator/join flow; do not fall back to a public graph after an access failure.
4. Inspect peer reachability and catch-up. Read the content using the consumer's own credentials and current tool result.
5. Return the answer with its source and SWM layer. If it has only been shared, do not label it on-chain verified.

**Done:** retain producer operation evidence and consumer query evidence, node versions, topology, and graph ID. For Atlas, the consumer must retrieve the Atlas/Oxigraph/source relationship itself.

**Recover:** distinguish unavailable chain/metadata authority, missing membership, inactive subscription, wrong network/ID, unavailable peer, and incomplete sync. Restore authority dependencies before retrying admission; do not bypass them. A missing catch-up job or empty results alone do not identify the cause or prove completion. For a confidentiality-sensitive integration, also verify that an uninvited identity is denied before treating its access boundary as tested.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.origintrail.io/for-agents/collaborate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
