For AI agents

This documentation is written for AI agents as much as for people. Every task page has the same structure: screen name, menu path, application route, required permission, prerequisites, numbered steps and result. An agent can carry out the work in CoreX ERP with these steps, without asking for additional context.

Endpoints

File	Content
/llms.txt	Site summary and a list of all pages (llmstxt.org format)
/llms-full.txt	Plain Markdown text of all pages, in a single file
/<page>.md	The Markdown version of each page — append .md to the page URL
/procedures.json	Structured steps of the task pages
/en/…	The English version of the same files

procedures.json

Each task is one record:

{
  "id": "teklif-olusturma",
  "title": "Create a sales quotation",
  "route": "/erp/sales/quotations/new",
  "menuPath": "Satış › Teklif Yönetimi › Satış Teklifi Oluştur (Sales › Quotation Management › Create Sales Quotation)",
  "permissions": ["erp-sales-quotations.create"],
  "prerequisites": ["The customer is defined as an Aktif (Active) business partner on the Müşteriler (Customers) screen."],
  "steps": [
    { "n": 2, "action": "fill", "target": "Müşteri", "value": "M-0004",
      "text": "In the Müşteri (Customer) field, type the customer's code or name and press Enter…" }
  ],
  "result": "The quotation is saved with number ST-yyyy-nnnnnn in Taslak (Draft) status…"
}

Field	Meaning
action	navigate open the screen · click click a button · fill type into a field · select select from a list · choose check an option · press press a key · open open a tab or section · verify check the result
target	The Turkish screen, button or field name in the application — verbatim
value	Example value (from the demo company)
expect	What should be visible after the step

Rules

• Screen and field names are the Turkish names used in the application; target is Turkish on the English pages as well.
• The application route (route) is appended to the installation's domain: https://<installation>/erp/sales/quotations.
• The screenshots in the steps are taken from a fictitious demo company; codes and names are examples.
• If the permission is missing, the button is not displayed — an agent should check the permissions field first.