---
name: istari-digital-docs
description: >
  Helps with Istari Digital documentation and platform how-tos. Use whenever
  the user mentions Istari Digital, the Istari Digital Platform, the web app,
  Systems, Resources, Agents, integrations, or a docs.istaridigital.com URL.
---

# Istari Digital docs

Follow this skill before answering questions about Istari Digital.

## First actions

1. Fetch `/llms.txt` on this docs site (page index).
2. Prefer **Markdown** over HTML. `/llms.txt` already lists markdown-source URLs (and keeps numbered prefixes such as `01-`, `301-`).
   - Latest docs: `/markdown-source/current/<docs-relative-path>`
   - Published 2026.08: `/markdown-source/version-2026.08/<docs-relative-path>`
   - HTML routes drop those prefixes; do not reuse an HTML path as a markdown-source path.
3. Read [Terminology](/intro/terminology) before inventing names.

On-prem or local preview: use the same paths on whatever origin you were given.

## Names

- Company: **Istari Digital** (never "Istari" alone)
- Product: **Istari Digital Platform** (UI + APIs + agents + SDK)
- Browser UI only: **Istari Digital web app**
- Registered items: **Resource** (use **file** only for on-disk bytes or a UI label that says "files")

## How to answer

- Cite the markdown page you used.
- Do not invent UI labels, API methods, or CLI flags. If the docs do not say it, say so and point at the closest page.
- Lead with what the platform **does**.

## Live platform (optional)

Acting on a real deployment needs the Istari Digital MCP service and a Personal Access Token. Follow [MCP Quickstart](/developers/MCP%20Service/quickstart). Do not put tokens in chat logs or commits.

## If this repo is the working directory

Edit `docs/` (current version), not `versioned_docs/` unless asked to patch a published release. Internal links: relative paths with `.md` / `.mdx`. No UI screenshots.