Tutorials, missions and groups. The product tag lives in the public GraphQL endpoint and the group hierarchies live in /build/catalog, so a useful sweep joins the two. Both anonymous.
Verified identities let the connected graph show one resource or person with references to both graphs. Identity does not establish implementation compatibility.
Builds the Incident Management CAP service and its HTML5 UI deployer as container images with the pack CLI's Cloud Native Buildpacks, then deploys both to SAP BTP, Kyma runtime with a Helm chart, wiring in the mock-server destination and productive cds build --production output set up in the prerequisite tutorials. Marked out of maintenance in favour of the newer "Develop a Side-by-Side CAP-Based Extension Application" mission in SAP Discovery Center, but the build-and-deploy mechanics it walks through — buildpacks, image tags, a Helm chart — are what deployment still covers for Kyma.
Constraints expressed in the model rather than checked in a handler — the distinction the atlas draws between input validation the framework enforces and validation somebody writes.
Mock users locally so authorization is modelled from the first commit instead of retrofitted — the argument being that auth added late reshapes a domain model rather than sitting on top of it.
Four steps in the SAP BTP cockpit that end with a service key for SAP Document AI: open the cockpit, check the subaccount's entitlements and add the service on the free tier plan if it is not listed, create the instance, then create the key. It names the plans to use in production instead, blocks_of_100, embedded_edition and premium_edition, and stops at the credentials, before any document is uploaded.
Atlas explains: artifact:btp-document-ai — How to get an instance of the service on a free tier subaccount: the entitlement, the free tier service plan, the service instance and the service key.
Eight steps from an entitled subaccount to the SAP Document AI basic UI open in a browser, and most of them are identity work rather than document work: getting a tenant for Cloud Identity Services, which the basic UI requires, activating the account and establishing trust with the subaccount, then subscribing, creating a user and assigning the Document_Information_Extraction_UI_Templates_Admin role collection. Using the UI to read a document is the subject of Use Machine Learning to Extract Information from Documents with the SAP Document AI Basic UI, which this tutorial names as what to read next.
Atlas explains: artifact:btp-document-ai — Subscribing a free tier subaccount to the service's basic UI, creating a user for it and assigning the Document_Information_Extraction_UI_Templates_Admin role collection that opens it.
Atlas explains: artifact:btp-cloud-identity-services — Getting a tenant, activating the account and establishing trust with the subaccount, which is the prerequisite the basic UI states before it can be subscribed to.
A fifteen-minute walkthrough of turning a plain CAP service into an MCP server: annotate the service with @mcp, install @cap-js/mcp, and it is served alongside OData at /mcp/<path>. The part worth reading it for is what happens next — cds watch writes the endpoint into the local agent's own configuration file, so OpenCode or Claude Code can call the service without anyone editing JSON by hand. It is built on the tiny-sample facet, so there is nothing to prepare, and it shows the protocol traffic rather than only the result. Written while the adapter was in beta, and it says so.
Both HTTPS GET requests returned 200 at the same final tutorial URL. The intake host bound the verification time and response hashes to its cached observations. Checked 2026-10-12.
Both HTTPS GET requests returned 200 at the same final tutorial URL. The intake host bound the verification time and response hashes to its cached observations. Checked 2026-10-12.
Tutorials, missions and groups, read from its public GraphQL endpoint and its build catalogue. Since mid-2026 it runs on an open platform with a knowledge graph of first-party learning content, which the atlas links into rather than repeats.