Artifact types

An application you deploy and use, installed into a system or loaded into an application as a component, rather than a library whose functions you call.

Runs at build time. Nothing of it ships in the deployed application.

Installs into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.

A command you run, rather than a dependency you import.

An application you run locally with a desktop user interface. It may be distributed as an installer or built from source; it is the workspace itself, rather than a library, command-line tool or hosted utility.

Documentation collected and cited. Evidence, like a sample.

Creates a project, a component or configuration once, when you run it, rather than taking part in every build.

Installs into a development environment (VS Code, Eclipse with ABAP Development Tools, SAP Business Application Studio) and works inside it, rather than as a library you call or a command you run.

Exposes tools to a coding agent over MCP.

A library you install and call yourself.

Delivered with a runtime rather than published. Nothing versions it independently and there is nothing to adopt or avoid — it is simply what the platform gives you.

A convention or specification you conform to rather than install. The answer itself, not evidence about one.

A worked example you read or clone. Evidence: it demonstrates, it never provides.

A BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.

A procedure an agent follows. Indexed here, never written here.

A hosted utility you use at a URL, rather than run or install. May be free or paid; source_available says whether anything behind it is inspectable.