{"ref":"capability:documentation","page":"/capabilities/documentation","json":"/capabilities/documentation.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"documentation","name":"Documentation","domain":"learning-and-reference","ecosystems":["cap","ui5","btp","abap"],"universal":false,"description":"Finding the answer in what has already been written, and writing it where it has not — first-party documentation made searchable by something other than a person scrolling it, including by an agent, and a document of custom code produced from the code itself.","short":"Finding answers in written documentation, and writing what is missing","core_coverage":{"state":"core-and-community","assessed_at":"2026-09-27","where_it_stops":"capire is the documentation and it is SAP's; what the corpus holds beside it is machine-readable packaging of the same material rather than a second source. Nothing here documents your application — that is metadata publishing.","note":"SAP-official packages and independent servers both package first-party prose for machines, and how they relate has not been assessed.","relationship":"unassessed","community_adds":"[mcp-sap-docs](artifact:marianfoo-mcp-sap-docs) clones SAP's documentation repositories and serves them over MCP with hybrid keyword and embedding retrieval, reaching ABAP, UI5 and BTP material the SAP-official embeddings package does not carry. [Clean-Core.io](artifact:sonnyfrenzel-rgb-clean-core-io) is the other kind: it writes a document of a custom program from the program itself.","what_core_does":"capire, at cap.cloud.sap, is the CAP documentation: its core pages are built from the public [capire/docs](artifact:capire-docs) repository, open to issues and pull requests, with SAP-specific pages added on publication. Around it, [@cap-js/mcp-server](artifact:cap-js-mcp-server) searches a preprocessed copy of it from a coding agent, and [@sap-ux/fiori-docs-embeddings](artifact:sap-ux-fiori-docs-embeddings) does the same for the Fiori documentation.","sources":[{"url":"https://github.com/capire/docs#readme","title":"capire/docs — README","checked":"2026-09-27","quote":"This repository contains the core parts of the documentation pages for the SAP Cloud Application Programming Model. As a short name, we refer to the documentation as Capire. Along with additional SAP-specific pages the content is published to https://cap.cloud.sap on a regular basis."},{"url":"https://github.com/SAP/open-ux-tools/tree/main/packages/fiori-docs-embeddings","title":"@sap-ux/fiori-docs-embeddings — README","checked":"2026-09-27","quote":"A Node.js package that indexes SAP Fiori related documentation from multiple sources and generates vector embeddings for semantic search capabilities."}]},"history":[{"date":"2026-09-09","field":"core_coverage.state","from":"core-only","to":"core-and-community","reason":"The previous note reasoned from the corpus — \"one provider, SAP-official\" — and the corpus changed: marianfoo-mcp-sap-docs was entered the same day as an independent provider. The state was a reading of what the graph held, so it moves when the graph does."},{"date":"2026-09-09","field":"ecosystems","from":"cap","to":"cap, ui5","reason":"An SAP-published MCP server entered from the sap-ai-mcp-servers catalogue answers this concern on the UI5 door, and the door had no tile for it to sit under."},{"date":"2026-09-10","field":"ecosystems","from":"cap, ui5","to":"cap, ui5, btp","reason":"Two documentation servers over BTP and AI Core corpora entered from the sap-ai-mcp-servers sweep."},{"date":"2026-09-10","field":"ecosystems","from":"cap, ui5, btp","to":"cap, ui5, btp, abap","reason":"Artifacts that answer this concern sat behind the ABAP door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a ABAP developer actually decides there, which is the test for opening a door rather than trimming a serves claim."},{"date":"2026-09-13","field":"description","from":"Finding the answer in what has already been written — first-party documentation made searchable by something other than a person scrolling it, including by an agent.","to":"widened to documenting custom code","reason":"Widened rather than forked into abap-code-documentation: producing a document of a custom package is the same concern from the writing side. The ABAP coverage moved from community-only to core-and-community because ADT's ABAP Doc export is the core's answer for custom code. Done so abap-doc (staged in intake-20260913-mariokernich) can provide it."},{"date":"2026-09-14","field":"coverage_by_flavor.abap-cloud","from":null,"to":"core-only","reason":"SAP documents the ABAP Cloud language version and its released-API contract directly — the developer guide, the Released Objects tree in ADT, the ABAP_CLOUD_READINESS check — and no artifact whose own ecosystem is abap states abap-cloud in its flavors: abap-cheat-sheets demonstrates rather than provides, and mcp-sap-docs answers this capability from the CAP door."},{"date":"2026-09-14","field":"coverage_by_flavor.web-components","from":null,"to":"core-only","reason":"The only UI5-ecosystem artifact that states web-components in its flavors is ui5-webcomponents-mcp-server, sap-official, and no other UI5-ecosystem provider of this capability names the flavor at all — core-only per the reading rule. framing_by_flavor was left unset: framing_by_ecosystem.ui5 already describes this same artifact, and it already reads as the web-components flavor's own paragraph rather than a cross-flavor one, so a second copy would restate it rather than say something different."},{"date":"2026-09-27","field":"core_coverage","from":"before the package pass","to":"after it","reason":"Package pass 2026-09-27: the capability had no paragraph and no source at all."},{"date":"2026-10-26","field":"core_coverage.note, core_coverage.community_adds","from":"Two providers packaging the same first-party prose for machines, one SAP-official and one independent, and how they relate has not been assessed. There is still no capire page about documentation-about-documentation to quote, so what_core_does stays empty rather than invented.","to":"SAP-official packages and independent servers both package first-party prose for machines, and how they relate has not been assessed. community_adds drops \"sixteen\" and names the kind that writes a document of custom code.","reason":"Reassessed against the graph (check:capabilities): the note counted providers and said what_core_does was empty, which it no longer is; a provider that documents a custom program changes the shape of the community answer."},{"date":"2026-10-26","field":"coverage_by_ecosystem.ui5.state, coverage_by_ecosystem.ui5.note","from":"core-only: Every provider behind this door is SAP-published, so core-only is a assessment of the corpus rather than a quote from the core.","to":"core-and-community: SAP's Web Components MCP server is core; independent tools reach the API reference and the change log.","reason":"Reassessed against the graph (check:capabilities): independent providers sit on this door (ui5-lib-diff, vscode-ui5-api-reference, and mcp-sap-docs, which serves ui5), so the stated core-only contradicted the providers."},{"date":"2026-10-26","field":"coverage_by_ecosystem.btp.where_it_stops, coverage_by_ecosystem.btp.note, framing_by_ecosystem.btp.description","from":"Each of these points at one SAP-docs repository; Both providers here are independent; two people have, each over one corpus","to":"Stops at the corpus or catalogue each server reads; the note and framing name kinds (documentation repositories, API catalogue, notes, roadmap) instead of counting","reason":"Reassessed against the graph (check:capabilities): servers over the API Business Accelerator Hub, SAP Notes and the roadmap arrived, so \"each points at one repository\" and \"both providers\" were no longer true."},{"date":"2026-10-26","field":"coverage_by_ecosystem.abap.note","from":"the artifacts here are community tools that read ABAP Doc, or generate a document","to":"the note names the community kinds: tools that read ABAP Doc, and generators of a package document, beside the core's ADT export","reason":"Reassessed against the graph (check:capabilities): community providers arrived that the note never named. The state stays core-and-community, because the core is the platform and the block states the ADT ABAP Doc export with its source."},{"date":"2026-10-26","field":"coverage_by_flavor.abap-cloud.note, coverage_by_flavor.web-components.note","from":"No artifact whose own ecosystem is abap states abap-cloud in its flavors; The only UI5-ecosystem artifact that states web-components in its flavors","to":"Notes state what is documented and where the flavor is named, without a claim about who else provides it","reason":"Reassessed against the graph (check:capabilities): absence claims about providers go stale as providers arrive. The flavor states are unchanged."}],"coverage_by_ecosystem":{"ui5":{"state":"core-and-community","assessed_at":"2026-09-09","relationship":"unassessed","where_it_stops":"At the documentation. Nothing here opens your project, so it cannot say whether the component it just described is the one your application already uses.","note":"SAP's own answer is [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server). Independent tools add the API reference inside the editor, as [vscode-ui5-api-reference](artifact:wozjac-vscode-ui5-api-reference) does, and the change log answered by release range, as [ui5-lib-diff](artifact:marianfoo-ui5-lib-diff) does. what_core_does is left empty: no page has been checked that states an intent here."},"btp":{"state":"community-only","assessed_at":"2026-09-10","where_it_stops":"At the corpus or catalogue each server reads. What is answerable is exactly what that repository, catalogue or feed holds and nothing beside it.","note":"The providers are independent and read SAP's published material: documentation repositories, the Business Accelerator Hub catalogue, SAP Notes and the roadmap. SAP publishes the documentation itself, in the open, which is what makes indexing it possible — publishing a corpus is not the same as answering this capability."},"abap":{"state":"core-and-community","assessed_at":"2026-09-13","what_core_does":"For custom code, ADT exports the ABAP Doc comments of classes and interfaces, chosen singly or by package, as HTML files, for example as a record for audits.","where_it_stops":"For SAP's own documentation, at the corpus indexed: an index cannot tell you which of two statements your release supports. For custom code, at what developers wrote as ABAP Doc comments on classes and interfaces; an element with no comment gets at most its short text.","sources":[{"url":"https://help.sap.com/doc/saphelp_nw75/7.5.5/en-us/95/acbb5ae3364dbca65bf4e0ecf9f7c8/content.htm","title":"ABAP Development Tools — Exporting ABAP Doc Comments","checked":"2026-09-13","quote":"you can export source code documentation of ABAP classes and ABAP interfaces, for example, in order to create a backup of this information for audits"}],"relationship":"unassessed","note":"Two halves on this door. SAP publishes its ABAP documentation in the open, and publishing a corpus is not answering this capability. For custom code the core export is the ABAP Doc one, a function of ADT, the platform; community tools add to it by reading ABAP Doc, such as [abapdocs-code-scanner](artifact:tf-franz-seidl-abapdocs-code-scanner), or generate a document of a package, such as [abap-doc](artifact:mariokernich-abap-doc). How they relate to the export has not been assessed."}},"framing_by_ecosystem":{"ui5":{"description":"The framework's own reference, served as tools rather than scrolled. [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server) answers what properties, slots, events and methods a named component actually has — the part a model is most likely to invent — and returns the integration guide for the framework you are wiring it into."},"btp":{"description":"SAP publishes its platform documentation as public repositories, which makes indexing it something anybody can do. Independent servers do so over single corpora, such as [BTP documentation](artifact:nickels-sap-btp-docs-mcp) and [AI Core documentation](artifact:nickels-sap-ai-docs-mcp), with semantic search and category filtering, and over catalogues such as SAP's [API Business Accelerator Hub](artifact:marianfoo-sap-api-hub-mcp)."},"abap":{"description":"The ABAP keyword documentation, the cheat sheets and the RAP tutorials are public repositories, and [mcp-sap-docs](artifact:marianfoo-mcp-sap-docs) indexes all three alongside a cloud and standard flavour switch — so an agent asked about a statement answers from the reference rather than from memory of an older release. Custom code is the other half: a package nobody documented, handed to a team that did not write it, where the document has to be produced from the objects in the system."}},"coverage_by_flavor":{"abap-cloud":{"state":"core-only","assessed_at":"2026-09-14","what_core_does":"SAP publishes ABAP Cloud as a restricted, cloud-safe ABAP language version built on released APIs, and lists which repository objects carry that release: found in ADT's Project Explorer under Released Objects, or on the SAP Business Accelerator Hub and the Cloudification Repository Viewer.","where_it_stops":"It documents which objects and statements the release contract covers, not whether a given piece of code still compiles against it — that check is ADT's syntax check and the ABAP_CLOUD_READINESS ATC variant, run against the code rather than read from a page.","sources":[{"url":"https://github.com/SAP-docs/btp-developer-guide/blob/main/docs/developing-with-abap-cloud-in-the-sap-btp-abap-environment-9aaaf65.md","title":"SAP-docs/btp-developer-guide — Developing with ABAP Cloud in the SAP BTP ABAP Environment","checked":"2026-09-14","quote":"ABAP Cloud is SAP's cloud-ready development model, used in the SAP BTP ABAP environment to build upgrade-stable extensions, services, and applications using released APIs and a restricted, cloud-safe ABAP language version."},{"url":"https://github.com/SAP-samples/abap-cheat-sheets/blob/main/19_ABAP_for_Cloud_Development.md","title":"SAP-samples/abap-cheat-sheets — 19_ABAP_for_Cloud_Development.md","checked":"2026-09-14","quote":"You can find the released repository objects in the Project Explorer view in ADT under Released Objects"},{"url":"https://github.com/SAP-samples/abap-cheat-sheets/blob/main/19_ABAP_for_Cloud_Development.md","title":"SAP-samples/abap-cheat-sheets — 19_ABAP_for_Cloud_Development.md","checked":"2026-09-14","quote":"You can use ATC check variant ABAP_CLOUD_READINESS for this purpose."}],"note":"The ABAP Cloud contract is documented by SAP in the developer guide and in ADT. [abap-cheat-sheets](artifact:sap-samples-abap-cheat-sheets) demonstrates this capability rather than providing it, and [mcp-sap-docs](artifact:marianfoo-mcp-sap-docs) answers it from the CAP door, abap only among the ecosystems it serves."},"web-components":{"state":"core-only","assessed_at":"2026-09-14","what_core_does":"SAP publishes the Web Components documentation at [ui5.github.io/webcomponents](https://ui5.github.io/webcomponents/docs/), describing the components as custom HTML elements compatible with React, Angular and Vue, and ships [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server), which serves component API across the `@ui5/webcomponents`, `@ui5/webcomponents-fiori` and `@ui5/webcomponents-ai` packages, a framework integration guide and its documentation set as tools an agent calls.","where_it_stops":"The MCP server's integration guide is narrower than the site it serves: `get_guidelines` covers React, Angular and native JavaScript, not the Vue integration the documentation site itself lists.","sources":[{"url":"https://ui5.github.io/webcomponents/docs/","title":"Introduction | UI5 Web Components","checked":"2026-09-14","quote":"Fully compatible with any current or future web development frameworks such as React, Angular, and Vue, allowing seamless integration into any tech stack."},{"url":"https://github.com/UI5/webcomponents-mcp-server","title":"UI5/webcomponents-mcp-server — README","checked":"2026-09-14","quote":"Fetch API docs for any UI5 Web Component (properties, slots, events, methods). Searches across @ui5/webcomponents, @ui5/webcomponents-fiori, and @ui5/webcomponents-ai packages."},{"url":"https://github.com/UI5/webcomponents-mcp-server","title":"UI5/webcomponents-mcp-server — README","checked":"2026-09-14","quote":"Get integration guides for React, Angular, or native JavaScript. Includes installation, imports, and usage examples."}],"note":"[@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server), sap-official, is the UI5-ecosystem artifact that states web-components in its flavors, which is what makes the assessment core-only rather than unmapped."}},"drafted_with_ai":true},"sap_delivery":{"door":"cap","all":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:cap-js-mcp-server","name":"@cap-js/mcp-server","json":"/artifacts/cap-js-mcp-server.json"},{"ref":"artifact:sap-ux-fiori-docs-embeddings","name":"@sap-ux/fiori-docs-embeddings","json":"/artifacts/sap-ux-fiori-docs-embeddings.json"}]},"by_flavor":{"node":null,"java":null}},"edges":{"use_cases":[],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:cap-js-mcp-server","name":"@cap-js/mcp-server","json":"/artifacts/cap-js-mcp-server.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:sap-ux-fiori-docs-embeddings","name":"@sap-ux/fiori-docs-embeddings","json":"/artifacts/sap-ux-fiori-docs-embeddings.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:ui5-webcomponents-mcp-server","name":"@ui5/webcomponents-mcp-server","json":"/artifacts/ui5-webcomponents-mcp-server.json","ecosystem":"ui5","origin_ring":"sap-official"},{"ref":"artifact:mariokernich-abap-doc","name":"abap-doc","json":"/artifacts/mariokernich-abap-doc.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:abap2ui5-playground","name":"abap2UI5 Playground","json":"/artifacts/abap2ui5-playground.json","ecosystem":"abap","origin_ring":"community-org"},{"ref":"artifact:tf-franz-seidl-abapdocs-code-scanner","name":"abapdocs-code-scanner","json":"/artifacts/tf-franz-seidl-abapdocs-code-scanner.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:sonnyfrenzel-rgb-clean-core-io","name":"Clean-Core.io","json":"/artifacts/sonnyfrenzel-rgb-clean-core-io.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:marianfoo-mcp-sap-docs","name":"mcp-sap-docs","json":"/artifacts/marianfoo-mcp-sap-docs.json","ecosystem":"cap","origin_ring":"independent"},{"ref":"artifact:nickels-sap-ai-docs-mcp","name":"sap-ai-docs-mcp","json":"/artifacts/nickels-sap-ai-docs-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:marianfoo-sap-api-hub-mcp","name":"sap-api-hub-mcp","json":"/artifacts/marianfoo-sap-api-hub-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:nickels-sap-btp-docs-mcp","name":"sap-btp-docs-mcp","json":"/artifacts/nickels-sap-btp-docs-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:marianfoo-sap-note-search-mcp","name":"sap-note-search-mcp","json":"/artifacts/marianfoo-sap-note-search-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:marianfoo-sap-roadmap-mcp","name":"sap-roadmap-mcp","json":"/artifacts/marianfoo-sap-roadmap-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:marianfoo-ui5-lib-diff","name":"ui5-lib-diff","json":"/artifacts/marianfoo-ui5-lib-diff.json","ecosystem":"ui5","origin_ring":"independent"},{"ref":"artifact:wozjac-vscode-ui5-api-reference","name":"vscode-ui5-api-reference","json":"/artifacts/wozjac-vscode-ui5-api-reference.json","ecosystem":"ui5","origin_ring":"independent"}],"samples":[{"ref":"artifact:marianfoo-abap-docs","name":"abap-docs","json":"/artifacts/marianfoo-abap-docs.json"},{"ref":"artifact:sap-samples-btp-service-metadata","name":"btp-service-metadata","json":"/artifacts/sap-samples-btp-service-metadata.json"},{"ref":"artifact:capire-docs","name":"capire/docs","json":"/artifacts/capire-docs.json"},{"ref":"artifact:tobiashofmann-off-stack-abap","name":"off-stack-abap","json":"/artifacts/tobiashofmann-off-stack-abap.json"},{"ref":"artifact:sap-samples-abap-cheat-sheets","name":"SAP-samples/abap-cheat-sheets","json":"/artifacts/sap-samples-abap-cheat-sheets.json"}],"explained_by":[{"ref":"content:devtoberfest-2026-ai-assisted-sap-development-with-mcp","name":"AI-assisted SAP development with MCP","json":"/content/devtoberfest-2026-ai-assisted-sap-development-with-mcp.json"},{"ref":"content:devtoberfest-2026-developers-sap-com-in-your-dev-environment","name":"Bring \"developers.sap.com\" Into Your Dev Environment: SAP Developer Context for AI Coding Agents","json":"/content/devtoberfest-2026-developers-sap-com-in-your-dev-environment.json"},{"ref":"content:how-i-use-ai-for-development-and-why-context-matters","name":"How I Use AI for Development and Why Context Matters","json":"/content/how-i-use-ai-for-development-and-why-context-matters.json"},{"ref":"content:finally-an-mcp-server-for-abap","name":"Finally: An MCP Server for ABAP","json":"/content/finally-an-mcp-server-for-abap.json"},{"ref":"content:unlocking-the-power-of-llms-in-cap-llms-txt","name":"⚡Unlocking the Power of LLMs in CAP: Understanding llms.txt and llms-full.txt","json":"/content/unlocking-the-power-of-llms-in-cap-llms-txt.json"},{"ref":"content:teched-2026-xp160","name":"Enhancing cyber resilience through AI-enabled tabletop exercises","json":"/content/teched-2026-xp160.json"}],"normative_context":[]}}