> 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/okf.md).

# OKF Workflow

**Inputs:** bundle directory, exact target graph, mapping options, and intended layer. Start with the [supplied two-concept tutorial](https://docs.origintrail.io/build-with-dkg/okf-tutorial.md).

1. Run the offline dry-run mapping. Inspect concept count, resolved/broken links, conformance errors, and warnings. Do not run a mutating import if the expected mapping is unresolved.
2. Import into WM and retain the lifecycle manifest and reported per-concept KA names. Import does not publish on-chain.
3. Inspect the RDF actually produced. A general Markdown cross-link maps to a general relation; do not silently reinterpret it as a stronger domain claim.
4. If sharing is authorized, advance the same import with `--share` and confirm completion. Resume through its manifest after an interruption; do not use `--replace` unless replacement was intended.
5. Verify using the same mapping and scope options supported by the installed CLI. The 10.0.23 baseline verification is SWM-oriented; a completeness check is neither factual validation nor an on-chain proof.
6. Export the requested memory view to a new directory and inspect concept content and links. Never overwrite the user's original bundle as an incidental verification step.

**Done:** report mapping counts, warnings, exact graph, current layer, verification outcome/scope, and export location. For the sample, expect two concepts and one Atlas-to-Oxigraph `http://schema.org/mentions` link.

For optional VM publication, select the intended named KAs and follow [Publish and query](https://docs.origintrail.io/for-agents/publish-query.md). Neither import nor export is implicit authorization to spend funds.


---

# 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/okf.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.
