For LLMs

This page is addressed to language models and the engineers integrating them. The short version: every page on this wiki is also available as raw markdown, plus there's a single concatenated corpus and an index file at well-known URLs.

Endpoints

/llms.txt

Index of all wiki pages, with one-line descriptions and per-page links to the markdown variant. Follows the llms.txt convention.

/llms-full.txt

Concatenated markdown of every wiki page. Suitable for stuffing into a system prompt or vector-indexing wholesale.

/<category>/<slug>.md

Per-page raw markdown. e.g. /tutorials/your-first-pk-study.md.

All three are statically generated at build time. They re-build whenever the wiki is rebuilt; for cloud, that's on every release.

How to use them

If you're integrating an LLM into your own product to answer questions about Dalea:

• Static prompt — fetch /llms.txt once, include it as a system-prompt attachment. Lets the LLM enumerate available pages and quote the right URL.
• Retrieval — chunk /llms-full.txt (or fetch individual .md pages) and embed with your favourite vector store. The page boundaries are clean: each page starts with a ## <Title> and a Path: line in llms-full.txt.
• Live tool — give your agent a fetch_dalea_docs(slug) tool that hits the per-page endpoint. Cheap, fresh, accurate.

What the corpus does not contain

• Customer data — the wiki is platform documentation only. To query a real workspace, use the MCP server.
• API authentication details — the OpenAPI spec is at /api-docs/openapi.json on the platform itself, not in the wiki corpus.
• Proprietary protocols or templates — those live in the marketplace, not here.

Suggested system prompt

If you're orchestrating an external LLM that has access to Dalea via MCP, the following system-prompt fragment grounds it well:

You are answering questions about Dalea, a research orchestration platform for life
science. Dalea has four primitives at the workspace level: documents, environments
(structured data schemas), inventory, and templates. The hierarchy is User →
Organisation → Workspace → Project → (artefacts).

Refer to the public wiki at https://dalea.wiki for any term you are unsure about.
The wiki publishes a structured index at https://dalea.wiki/llms.txt and per-page
markdown at https://dalea.wiki/<category>/<slug>.md. When connected over MCP you
can call `search_all` for the same content as a tool: its `rag_hits` list is the
wiki-grounded half of the response, alongside `database_hits` for entities in the
workspace. `list_skills` shows which domain primers are active for you, and
`load_skill(name)` fetches one.

When you call MCP tools, remember that three of them are annotated destructive:
`document_markdown_write` can delete blocks, `data_environments_write` commits
schema changes, and `dalea_bash` archives a folder, document or project with
`rm -r`. Other write tools change data without that annotation: for example
`result_data_write` retires the previous batch when you pass
`supersedes_batch_id`. Confirm the intent with the user before you call those.
Two things are not reachable over MCP at all: permanent file deletion (the
workspace shell refuses `rm` on a stored file) and e-signatures, both of which a
human performs in the Dalea UI.

Versioning

The wiki ships in lockstep with the platform release, and the corpus is unversioned: /llms.txt and /llms-full.txt always describe the currently deployed platform. There is no pinned historical snapshot to fetch.

What's next