PlatformEngr® Platform fundamentals course

Cheat notes · Module 03 · What the platform offers

The capability map: what the platform offers

A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.

The idea

The capability map is the platform's menu: what a team can get, from whom and how. It must tell the truth: offered means self-service, and planned means nothing may depend on it yet.

Remember

  • The CNCF white paper lists thirteen capability areas, from web portals and APIs to artifact storage.
  • Statuses: offered, beta, planned.
  • Offered or beta needs a self-service interface: portal, cli, api, git or mcp. ticket alone fails C2.
  • Name a capability by what the user gets, not by the tool behind it.
  • The seven layers are this course's grouping, not a standard.

Pitfalls

  • Calling a ticket queue "offered" fails C2.
  • Leaving out planned capabilities hides the roadmap from users.

Test yourself

Answer in your head first, then open the answer.

Is a namespace by ticket within a day self-service?

No: the team still waits for a person to act.

Why list planned capabilities?

So teams know not to build on them, and the gaps are visible.

What fields does each capability carry?

id, name, layer, owner, status, interfaces, users.

Where module 03 leaves you: capabilities.yaml passes the check: eleven capabilities, every one owned by platform, three of them planned, every offered or beta one with a self-service interface. All are for humans for now.