Skip to content
Mike Reams

Try

Searches titles, summaries and topics across posts, work, diagrams, pages and the 47 Toolbox resources.

↑ ↓ move · Enter open · Esc close
← Work

PRJ · 2026

Blueprint Catalog: An Open Business Capability Catalog

A free, open-data catalog of business capabilities, value streams, products and patterns: pages, JSON and an MCP server.

A capability model in a slide deck to Open data with an API and an MCP server

View project
LinkedIn (opens in a new tab)X (opens in a new tab)Facebook (opens in a new tab)Email
The Blueprint Catalog's capability explorer: a tree of domains and L1 capabilities with ids and counts on the left, and eight macro-domain cards from Direct & Govern to Resilience & Responsibility on the right.The Blueprint Catalog's capability explorer: a tree of domains and L1 capabilities with ids and counts on the left, and eight macro-domain cards from Direct & Govern to Resilience & Responsibility on the right.

What it is

A reference catalog for enterprise architects: 116 top-level business capabilities across eight macro domains and eight industries, broken down to more than 3,000 nodes, each with a description, scope lines and a CSDM note. Around them sit 55 value streams with their stages and domain events, 58 products mapped to the capabilities they realize, 63 design patterns and 22 anti-patterns, 52 frameworks and standards, 21 architecture principles, 31 data concepts, a technology reference model with end-of-life dates for 45 technologies, and a glossary. Everything is Mike's own writing under CC BY 4.0.

The problem

Every capability-mapping engagement starts by rebuilding the same model: a reference map, a way to place applications on it, exports that the EA tool or CMDB will accept, and a vocabulary the business recognizes. The good references are paid or locked inside a tool, and none of them are shaped for an AI agent to read.

What I built

  • Content as code: YAML validated by JSON Schema at build, with stable ids that are never reused and a change log per release.
  • Three ways in: the pages, a static JSON API under /api/v1, and a read-only MCP server at /mcp that answers from the same build, with no key.
  • Exports shaped for ServiceNow, LeanIX, Ardoq and ArchiMate, parents first, so the map lands in a tool in one import and re-imports onto the same records at the next release.
  • Nine agent skills for using it, a FINOS CALM standard for tagging architectures with catalog ids, and a fictional worked example with the heat map and gaps computed from the mapping.

Where it shows up here

The Technology and Toolbox pages read a committed snapshot of the catalog, so the tiles carry product capabilities, lifecycle dates and book details without the site ever calling it. The nine catalog skills are in the AI Library.