--- 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/` - Published 2026.08: `/markdown-source/version-2026.08/` - HTML routes drop those prefixes; do not reuse an HTML path as a markdown-source path. - **Percent-encode spaces.** Directories such as `developers/MCP Service/` contain a literal space. `.../developers/MCP%20Service/01-quickstart.md` resolves; the same path with a raw space does not. 3. Read [Terminology](/markdown-source/current/intro/terminology.md) before inventing names. 4. Reading three or more pages from one section? Fetch that section's bundle instead (`/markdown-source/
-bundle.md`) — one round trip, listed at the end of `/llms.txt`. `/llms.txt` is a curated index, not a complete file listing. Some pages exist without being linked there (for example `users/user-guide/branches.md` and `users/user-guide/lineage.md`). If the index has no obvious page for a question, check the table below before concluding the docs are silent. On-prem or local preview: use the same paths on whatever origin you were given. ## Fetching accurately Many agent fetch tools pipe a page through a smaller summarizing model before you see it, paraphrasing UI labels on the way. That silently breaks the "do not invent labels" rule below — the label you report was never on the page. - Ask for **verbatim** reproduction, and treat only strings you received inside quotation marks as real labels. Everything else is paraphrase. - A missing label usually means the summarizer dropped it, not that the docs omit it. Re-fetch with a narrower prompt naming the one procedure you need before reporting a gap. - If a label still does not survive intact, say which labels you are confident in and which you are not. Never reconstruct a plausible-sounding button name. - If your tooling can retrieve raw bytes (a plain HTTP GET rather than a summarizing fetch tool), prefer that for any answer that quotes UI labels, API methods, or CLI flags. ## 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") Terminology defines **File** and **Model** but has no standalone **Resource** entry; the definition lives in [Resources](/markdown-source/current/intro/key-concepts/resources.md). Source pages are not fully consistent here — Terminology says a Job runs "on a model," the Jobs guide says "on a file." Both mean a Resource. Normalize to **Resource** in your answer, and quote a page's own wording only when quoting it directly. ## Where answers live | Question | Pages | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | What is a Resource / getting a file into the platform | `intro/key-concepts/resources.md`, `users/user-guide/files.md` | | Add a Resource to a System, commit a change | `users/user-guide/systems.md`, `intro/key-concepts/systems.md` | | Branches, commits, change requests | `users/user-guide/branches.md`, `users/user-guide/version-control.md` | | Why a System did not pick up a new Resource version | `intro/key-concepts/version-control.md` (tracked vs pinned membership) | | Run an extraction or any job; job statuses | `users/user-guide/jobs.md` | | Is my CAD / solver / PLM tool supported | `integrations/01-supported-integrations.md` | | How integrations, Agents, and Modules fit together | `intro/key-concepts/integrations.md`, `integrations/00-integration_basics.md` | | A job failed | `integrations/07-troubleshooting.md`, `users/user-guide/jobs.md` | | Where an artifact came from | `users/user-guide/lineage.md` | | Permissions, roles, sharing | `intro/key-concepts/sharing-security-access-control.md`, `users/user-guide/sharing-and-access.md` | | Classification and control tags | `intro/key-concepts/infosec-levels.md`, `users/admin-guide/control-tags.md` | | Personal access tokens | `users/user-guide/settings.md` | | Python client | `developers/SDK/01-setup.md` | | MCP service | `developers/MCP%20Service/01-quickstart.md` | | CLI | `developers/CLI/01-istari-digital-cli.md` | | What an Agent is / deploying one | `itAdmins/04-Agent/01-Introduction.md` | All paths are relative to `/markdown-source/current/`. ## 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**. For a how-to, state in this order: **required role** · **prerequisites** · **steps with exact labels** · **how to verify it worked** · **anything the docs do not cover**. Prerequisites are often on a different page than the procedure — an extraction needs a Module installed on an Agent (Terminology), which the Jobs guide does not repeat. If the answer could differ between releases, ask which version the user is on before answering, or state which tree you read (`current` vs `version-2026.08`). ## Live platform (optional) Acting on a real deployment needs the Istari Digital MCP service and a Personal Access Token. Follow [MCP Quickstart](/markdown-source/current/developers/MCP%20Service/01-quickstart.md). 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. Prefer reading files from disk over fetching the site — no summarizing layer, and you get pages `/llms.txt` does not list. `/llms.txt` itself is generated from a hardcoded template in `src/plugins/markdown-source-plugin.js`; edit it there, not in `build/`.