@eventcatalog/core 5.9.0 → 5.10.0

package/dist/analytics/analytics.cjs

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(analytics_exports);
 var import_os = __toESM(require("os"), 1);
 
 // package.json
-var version = "5.9.0";
+var version = "5.10.0";
 
 // src/constants.ts
 var VERSION = version;

package/dist/analytics/analytics.js

@@ -1,8 +1,8 @@
 import {
   raiseEvent
-} from "../chunk-26C26LFE.js";
+} from "../chunk-EXBUNFIM.js";
 import "../chunk-CPW6G62V.js";
-import "../chunk-C4L6B5KR.js";
+import "../chunk-EETSYUKN.js";
 export {
   raiseEvent
 };

package/dist/analytics/log-build.cjs

@@ -169,7 +169,7 @@ var verifyRequiredFieldsAreInCatalogConfigFile = async (projectDirectory) => {
 var import_os = __toESM(require("os"), 1);
 
 // package.json
-var version = "5.9.0";
+var version = "5.10.0";
 
 // src/constants.ts
 var VERSION = version;

package/dist/analytics/log-build.js

@@ -1,12 +1,12 @@
 import {
   log_build_default
-} from "../chunk-WN6ZFSXF.js";
+} from "../chunk-5QOG7UYZ.js";
 import "../chunk-AD7CL772.js";
-import "../chunk-26C26LFE.js";
+import "../chunk-EXBUNFIM.js";
 import "../chunk-YRZK7HKX.js";
 import "../chunk-CA6WCQ2T.js";
 import "../chunk-CPW6G62V.js";
-import "../chunk-C4L6B5KR.js";
+import "../chunk-EETSYUKN.js";
 import "../chunk-4G7FSRPN.js";
 export {
   log_build_default as default

package/dist/{chunk-WN6ZFSXF.js → chunk-5QOG7UYZ.js}

@@ -3,7 +3,7 @@ import {
 } from "./chunk-AD7CL772.js";
 import {
   raiseEvent
-} from "./chunk-26C26LFE.js";
+} from "./chunk-EXBUNFIM.js";
 import {
   countResources,
   hashCatalogContent,

package/dist/{chunk-C4L6B5KR.js → chunk-EETSYUKN.js}

@@ -1,5 +1,5 @@
 // package.json
-var version = "5.9.0";
+var version = "5.10.0";
 
 // src/constants.ts
 var VERSION = version;

package/dist/{chunk-UIJUSHOT.js → chunk-EGOTM5ZG.js}

@@ -1,6 +1,6 @@
 import {
   logger
-} from "./chunk-SZU7I2PD.js";
+} from "./chunk-ZE2RPUNY.js";
 import {
   cleanup,
   getEventCatalogConfigFile
@@ -8,6 +8,7 @@ import {
 
 // src/generate.js
 import path from "path";
+import { pathToFileURL } from "url";
 function getDefaultExport(importedModule) {
   if (importedModule === null || typeof importedModule !== "object") {
     throw new Error("Invalid module");
@@ -39,7 +40,7 @@ var generate = async (PROJECT_DIRECTORY) => {
         plugin = plugin.replace("<rootDir>", PROJECT_DIRECTORY);
       }
       try {
-        const importedGenerator = await import(plugin);
+        const importedGenerator = await (path.isAbsolute(plugin) ? import(pathToFileURL(plugin).href) : import(plugin));
         const generator2 = getDefaultExport(importedGenerator);
         await generator2({ eventCatalogConfig: {} }, pluginConfig);
       } catch (error) {

package/dist/{chunk-26C26LFE.js → chunk-EXBUNFIM.js}

@@ -4,7 +4,7 @@ import {
 } from "./chunk-CPW6G62V.js";
 import {
   VERSION
-} from "./chunk-C4L6B5KR.js";
+} from "./chunk-EETSYUKN.js";
 
 // src/analytics/analytics.js
 import os from "os";

package/dist/{chunk-SZU7I2PD.js → chunk-ZE2RPUNY.js}

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-C4L6B5KR.js";
+} from "./chunk-EETSYUKN.js";
 
 // src/utils/cli-logger.ts
 import pc from "picocolors";

package/dist/constants.cjs

@@ -25,7 +25,7 @@ __export(constants_exports, {
 module.exports = __toCommonJS(constants_exports);
 
 // package.json
-var version = "5.9.0";
+var version = "5.10.0";
 
 // src/constants.ts
 var VERSION = version;

package/dist/constants.js

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-C4L6B5KR.js";
+} from "./chunk-EETSYUKN.js";
 export {
   VERSION
 };

package/dist/docs/development/00-why-eventcatalog.md

@@ -45,6 +45,9 @@ EventCatalog is technology agnostic, this means you can document and model any s
 - **Help you detect breaking changes before they reach production**
   - Use EventCatalog Agents to [detect breaking schema changes](/docs/development/agents/set-up-breaking-changes)
   - Bring your own model and get notified when things break
+- **Help you follow the architecture decisions you've made**
+  - Document decisions as [ADRs](/docs/development/guides/resources/adrs/introduction) alongside the resources they affect
+  - Use EventCatalog Agents to [check pull requests against your ADRs](/docs/development/agents/set-up-adr-compliance)
 - **Use natural language to query your architecture**
   - Connect AI tools to your architecture using [EventCatalog's MCP server](/docs/development/ask-your-architecture/mcp-server/introduction)
   - Ask architectural questions grounded in your documented domains, services, events, [data products](/docs/development/guides/resources/data-products/introduction), and schemas

package/dist/docs/development/ask-your-architecture/01-intro.md

@@ -9,14 +9,27 @@ description: Architecture documentation for humans and AI
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
 
-EventCatalog creates an internal graph of your architecture. Perfect for AI and LLMs.
+There are three ways to use AI with your catalog.
 
-EventCatalog supports eight ways to use AI with your catalog:
+## Ask questions about your architecture
+
+Connect AI to your catalog, and ask it how your architecture works.
 
 - [EventCatalog MCP Server](/docs/development/ask-your-architecture/mcp-server/introduction) - Connect EventCatalog to Agents through MCP
 - [EventCatalog Assistant](/docs/development/ask-your-architecture/eventcatalog-assistant/what-is-eventcatalog-assistant) - AI Chat in your Catalog.
-- [Sync docs with your code](/docs/development/agents/set-up-code-to-docs) - EventCatalog Agents keep your catalog in sync with your code
-- [Catch breaking changes](/docs/development/agents/set-up-breaking-changes) - EventCatalog Agents warn you before a schema change breaks a consumer
+
+## Automate your pull requests
+
+EventCatalog Agents run in your CI/CD pipeline and report back on your pull requests.
+
+- [Sync docs with your code](/docs/development/agents/set-up-code-to-docs) - Keep your catalog in sync with your code
+- [Catch breaking changes](/docs/development/agents/set-up-breaking-changes) - Get warned before a schema change breaks a consumer
+- [Check code against ADRs](/docs/development/agents/set-up-adr-compliance) - Check that pull requests follow your architecture decisions
+
+## Help AI tools work with your catalog
+
+Give the AI tools you already use the skills and context they need.
+
 - [AI Skills](/docs/development/getting-started/install-skills) - Install our Skills to help you manage your catalog
 - [llms.txt](/docs/development/developer-tools/llms.txt) - Give AI tools a machine-readable index of your catalog.
 - [schemas.txt](/docs/development/developer-tools/schemas.txt) - Give AI tools access to your schemas and specifications.

package/dist/docs/development/ask-your-architecture/06-sync-docs-with-your-code.md

@@ -45,7 +45,7 @@ You need:
 - A repository with code to document (the **source repository**).
 - An API key for an AI model provider.
 
-## Set it up
+## Setup
 
 In your source repository, add two secrets under **Settings → Secrets and variables → Actions**:
 
@@ -75,11 +75,18 @@ jobs:
           fetch-depth: 0
       - uses: event-catalog/agents@v2
         env:
+          # The key for your model's provider. This one is for the default model.
+          # Using another provider? Swap this variable and set `model` below.
           ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
         with:
+          # The agent workflow to run.
           agent: code-to-docs
+          # Your catalog repository, in owner/repo format.
           catalog-repo: your-org/your-catalog
+          # A token that can read your catalog, push branches and open pull requests.
           catalog-token: ${{ secrets.EVENTCATALOG_TOKEN }}
+          # Optional: the model to use. Defaults to anthropic/claude-sonnet-4-6.
+          # model: openai/gpt-5.1
 ```
 
 Replace `your-org/your-catalog` with your catalog repository. Keep `fetch-depth: 0`: the agent needs it to compare the pull request with its base branch.

package/dist/docs/development/ask-your-architecture/07-catch-breaking-changes.md

@@ -40,7 +40,7 @@ You need:
 - A repository with message schemas (the **source repository**).
 - An API key for an AI model provider.
 
-## Set it up
+## Setup
 
 In your source repository, add two secrets under **Settings → Secrets and variables → Actions**:
 
@@ -68,11 +68,18 @@ jobs:
           fetch-depth: 0
       - uses: event-catalog/agents@v2
         env:
+          # The key for your model's provider. This one is for the default model.
+          # Using another provider? Swap this variable and set `model` below.
           ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
         with:
+          # The agent workflow to run.
           agent: breaking-changes
+          # Your catalog repository, in owner/repo format.
           catalog-repo: your-org/your-catalog
+          # A token that can read your catalog repository.
           catalog-token: ${{ secrets.EVENTCATALOG_TOKEN }}
+          # Optional: the model to use. Defaults to anthropic/claude-sonnet-4-6.
+          # model: openai/gpt-5.1
 ```
 
 Replace `your-org/your-catalog` with your catalog repository. Keep `fetch-depth: 0`: the agent needs it to compare the pull request with its base branch.

package/dist/docs/development/ask-your-architecture/08-check-code-against-adrs.md

@@ -0,0 +1,169 @@
+---
+sidebar_position: 8
+keywords:
+  - ADR Compliance
+  - EventCatalog Agents
+  - architecture decision records
+  - ADR governance
+  - GitHub Actions
+sidebar_label: Check code against ADRs
+title: Check code against ADRs
+description: The ADR Compliance workflow comments on pull requests when the code conflicts with an architecture decision documented in your EventCatalog, citing the line and the decision.
+slug: /development/agents/set-up-adr-compliance
+---
+
+import { AdrComplianceComment } from '@site/src/components/AgentOutputs';
+import { AgentPrompt } from '@site/src/components/AgentPrompt';
+
+The **ADR Compliance** workflow checks the code changed in a pull request against the [architecture decision records](/docs/development/guides/resources/adrs/introduction) in your catalog. You choose which ADRs apply to the repository. If the code clearly conflicts with one, it comments with the line, the decision, and how to fix it. It never edits your catalog or blocks a merge.
+
+<AgentPrompt variant="adr-compliance" />
+
+### Example 
+<AdrComplianceComment />
+
+## How it works
+
+1. **Selects the ADRs.** It finds the ADRs matching your `adrs` input, and keeps the `accepted` ones at their latest version. If an accepted ADR amends one of them, it's included too, because the decision can't be judged correctly without it.
+2. **Finds the relevant ones.** It compares the ADR summaries with the changes, so only ADRs on the same topic are reviewed in full.
+3. **Reviews the changed lines.** It reports only clear conflicts. Code that follows an ADR, code the pull request didn't change, and comments that merely mention something an ADR rules out are not conflicts. A decision for a domain or system takes precedence over a broader one on the same topic.
+4. **Checks its citations.** The line must be one the pull request changed, and the quoted sentence must be in the ADR. A conflict that fails this check is dropped.
+5. **Comments on the pull request** with each conflict. The comment updates on every push, and says so once the conflicts are gone.
+
+If there are no conflicts, it doesn't comment.
+
+## Before you start
+
+You need:
+
+- An EventCatalog in a GitHub repository (the **catalog repository**), with the catalog at the root of the repository, and your decisions documented as [ADRs](/docs/development/guides/resources/adrs/creating-adrs).
+- A repository with the code you want to check (the **source repository**).
+- An API key for an AI model provider.
+
+## Setup
+
+In your source repository, add two secrets under **Settings → Secrets and variables → Actions**:
+
+- `ANTHROPIC_API_KEY`, or the key for [your model provider](#models).
+- `EVENTCATALOG_TOKEN`, a GitHub token that can read your catalog repository. The workflow never writes to it.
+
+Then add the workflow. It runs while the pull request is open, so a conflict is raised while the code can still change:
+
+```yaml title=".github/workflows/eventcatalog-adr-compliance.yml"
+on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+jobs:
+  adr-compliance:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      issues: write
+      pull-requests: write
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+          fetch-depth: 0
+      - uses: event-catalog/agents@v2
+        env:
+          # The key for your model's provider. This one is for the default model.
+          # Using another provider? Swap this variable and set `model` below.
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+        with:
+          # The agent workflow to run.
+          agent: adr-compliance
+          # The ADRs to check against, as globs from your catalog's root.
+          # Here: the top-level adrs folder and the Orders domain.
+          adrs: adrs/**, domains/Orders/**
+          # Your catalog repository, in owner/repo format.
+          catalog-repo: your-org/your-catalog
+          # A token that can read your catalog repository.
+          catalog-token: ${{ secrets.EVENTCATALOG_TOKEN }}
+          # Optional: the model to use. Defaults to anthropic/claude-sonnet-4-6.
+          # model: openai/gpt-5.1
+```
+
+Replace `your-org/your-catalog` with your catalog repository, and set `adrs` to the [ADRs that apply to this repository](#choose-which-adrs-to-check). Keep `fetch-depth: 0`: the agent needs it to compare the pull request with its base branch.
+
+To check it works, open a pull request that does something one of your accepted ADRs rules out.
+
+## Choose which ADRs to check
+
+The `adrs` input is required. It takes comma-separated globs, relative to the root of your catalog. ADRs can live in any `adrs` folder in your catalog, so point the globs at wherever yours are:
+
+| To check against | Use |
+| --- | --- |
+| ADRs in the top-level `adrs` folder | `adrs/**` |
+| A domain, and everything nested in it | `domains/Orders/**` |
+| One system | `domains/Orders/systems/checkout-system/**` |
+| One service | `domains/Orders/services/OrdersAPI/**` |
+| ADRs that share a naming convention | `adrs/adr-orders-*/**` |
+| One ADR | `adrs/adr-012-use-outbox` |
+| Every ADR in the catalog | `'**/adrs/**'` |
+
+A typical repository checks against your organization-wide ADRs and those of its own domain:
+
+```yaml
+with:
+  adrs: adrs/**, domains/Orders/**
+```
+
+Globs start at the catalog root, so `adrs/**` means only the top-level folder, not every folder called `adrs`. A value that starts with `*` needs quotes in YAML.
+
+If `adrs` is missing or matches no ADRs, the run fails with an error that shows where your ADRs are, so a typo can't look like a clean pass.
+
+:::tip
+Checking every ADR in the catalog can raise conflicts with decisions meant for other teams. Start with the ADRs that apply to the repository.
+:::
+
+## Record an exception
+
+If a conflict is intentional, add a line to the pull request description with the ADR's `id` and your reason:
+
+```text
+adr-exception: adr-003-offload-async-work-to-worker small thumbnails only
+```
+
+The conflict then moves to an exceptions list in the comment, so reviewers can still see it. The agent reads the description when it runs, so push a commit or re-run the workflow after adding the line. To re-run automatically when the description changes, add `edited` to the `types`.
+
+A reason is required: a line without one is ignored. Exceptions are visible rather than enforced, so anyone who can edit the description can add one.
+
+If the decision itself has changed, propose a new ADR in your catalog instead. See [ADR relationships](/docs/development/guides/resources/adrs/relationships).
+
+## Configuration
+
+| Input | Required | Default | Description |
+| --- | --- | --- | --- |
+| `agent` | Yes | | Set to `adr-compliance` to run this workflow. |
+| `adrs` | Yes | | Comma-separated globs, relative to the catalog root, selecting the ADRs to check against. |
+| `catalog-repo` | Yes | | Your catalog repository, in `owner/repo` format. |
+| `catalog-ref` | No | `main` | The catalog branch to read. |
+| `catalog-token` | No | `github.token` | A token that can read the catalog repository. |
+| `catalog-url` | No | | The URL of your hosted catalog. The comment links ADRs to it. Without it, they link to your catalog repository. |
+| `model` | No | `anthropic/claude-sonnet-4-6` | The model the agent uses. See [models](#models). |
+| `ignore-paths` | No | Build and dependency folders | Comma-separated paths or glob patterns to leave out of the review. |
+
+## Models
+
+Use any model from [these providers](https://pi.dev/models). Set `model` to a provider and model name, and pass your provider's key as an environment variable on the step:
+
+| Provider | Model example | Environment variable |
+| --- | --- | --- |
+| Anthropic | `anthropic/claude-sonnet-4-6` | `ANTHROPIC_API_KEY` |
+| OpenAI | `openai/gpt-5.1` | `OPENAI_API_KEY` |
+| OpenRouter | `openrouter/anthropic/claude-sonnet-4.6` | `OPENROUTER_API_KEY` |
+
+To use models in your own AWS account, use an `amazon-bedrock/` model, such as `amazon-bedrock/eu.anthropic.claude-sonnet-4-6`, and give the job AWS credentials with [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials).
+
+## Data and privacy
+
+- **It's read-only.** It only comments on pull requests, and never edits your catalog.
+- **Your code goes to one place:** the model provider you configure. The agent runs in your GitHub Actions runner. EventCatalog never receives your code, your catalog or your pull requests.
+
+Each run sends one anonymous usage event: the outcome and the kind of error if it failed, the model, the run's duration, whether the pull request was open or merged, and the repository name. It never contains code, file names, paths, diffs or pull request content. To turn it off, set `POSTHOG_KEY: ''` in the step's `env`.
+
+## Versions
+
+ADR Compliance needs `event-catalog/agents@v2.2.0` or later. Use `event-catalog/agents@v2` for the latest v2 release, or an exact release such as `event-catalog/agents@v2.2.0`, which never changes. Releases are listed on [GitHub](https://github.com/event-catalog/agents/tags).

package/dist/docs/development/guides/resources/adrs/01-introduction.md

@@ -20,6 +20,7 @@ Documenting ADRs in your catalog gives your team:
 - **Context** — anyone can see what alternatives were considered and why a particular path was chosen.
 - **Traceability** — decisions are linked directly to the services, events, domains, and flows they affect via `appliesTo`.
 - **Lifecycle tracking** — each ADR has a status (`proposed`, `accepted`, `rejected`, `deprecated`, `superseded`) so it is clear which decisions are still in force.
+- **Checks in pull requests** — the [ADR Compliance workflow](/docs/development/agents/set-up-adr-compliance) comments when a pull request's code conflicts with an accepted decision.
 - **AI-ready context** — because ADRs sit alongside the resources they govern, the [EventCatalog MCP server](/docs/development/ask-your-architecture/mcp-server/introduction) can surface the *why* behind your architecture to AI assistants, not just the *what*. When an LLM is reasoning about a service or event, it picks up the decisions, trade-offs, and constraints recorded in your ADRs.
 
 ## Lifecycle statuses

package/dist/docs/development/guides/resources/entities/05-entity-maps.md

@@ -44,7 +44,12 @@ You can also embed an entity map on a page using the `<EntityMap />` component.
 
 Use embedded entity maps when you want the model to appear directly in domain, service, or custom documentation.
 
+## See every entity at once
+
+Entity maps show the entities of one domain or service. To see every entity in your catalog, and how entities relate across domains, open the [Global Entity Map](/docs/development/guides/resources/entities/global-entity-map).
+
 ## Next steps
 
 - [Model entity relationships](/docs/development/guides/resources/entities/model-entity-relationships)
+- [Global entity map](/docs/development/guides/resources/entities/global-entity-map)
 - [EntityMap component reference](/docs/development/components/components/entitymap)

package/dist/docs/development/guides/resources/entities/06-global-entity-map.md

@@ -0,0 +1,101 @@
+---
+keywords:
+- EventCatalog entities
+- Global entity map
+- Entity relationship diagram
+- Data model
+sidebar_position: 6
+sidebar_label: Global entity map
+title: Global entity map
+description: See every entity in your catalog, and how they relate across domains, on one diagram.
+---
+
+import AddedIn from '@site/src/components/MDX/AddedIn';
+
+<AddedIn version="5.10.0" />
+
+The Global Entity Map shows every entity in your catalog on one diagram, with the references between them. Where an [entity map](/docs/development/guides/resources/entities/entity-maps) shows the entities of one domain or service, the Global Entity Map shows the data model of the whole organization.
+
+Use it to answer questions like:
+
+- Which entities does each domain own?
+- Which entities are referenced from other domains?
+- Which entities are shared by more than one domain?
+- Which entities don't belong to anything yet?
+
+![Global Entity Map showing every entity grouped into its domain](./img/global-entity-map.png)
+
+## Open the Global Entity Map
+
+When your catalog has entities, a **Global Entity Map** link appears in the **Top level diagrams** section of the visualizer sidebar. You can also open it at:
+
+```txt
+/visualiser/entity-map
+```
+
+The map shows the latest version of every entity.
+
+If you've [customized your sidebar](/docs/development/customization/documentation-sidebar#custom-groups-and-links), you can add a custom link to this URL.
+
+## How entities are placed in domains
+
+[Entities can be added to domains, systems, and services](/docs/development/guides/resources/entities/add-entities-to-resources). The Global Entity Map works out which domain each entity belongs to from any of them:
+
+| Entity listed by | Belongs to |
+|------------------|------------|
+| A domain | That domain. |
+| A system | The system, and the domain the system is in. |
+| A service | The service's system (if it's in one), and its domain. |
+| More than one domain | **Shared across domains**, a group of its own. |
+| Nothing | No domain. It's shown outside every group. |
+
+A resource that pins an older version of an entity doesn't own the latest version. For example, if a domain lists `customer` at version `1.0.0` and the latest is `2.0.0`, that domain doesn't own the `customer` shown on the map.
+
+An entity's team is its own owner, or else the owner of the domain, system, or service that lists it.
+
+## Group entities
+
+The map opens with entities grouped by their domain. Use **Group by** at the top right of the diagram (or press <kbd>G</kbd>) to group them another way:
+
+| Group by | What it shows |
+|----------|---------------|
+| **Domain** | A box for each domain, and one for entities shared across domains. |
+| **System** | A box for each system. Only entities listed by a system, or by a service in one, are grouped. |
+| **Team** | A box for each owning team. |
+| **Domain, then system** | Systems nested in their domain. |
+| **Nothing** | No groups. |
+
+Groups can be shown as **Boxes** placed around their entities, or as **Lanes** stacked from top to bottom.
+
+![The Group by menu, with entities grouped by domain](./img/global-entity-map-group-by.png)
+
+## Filter what's shown
+
+The panel on the left of the diagram lists each domain, with how many entities it has and how many references cross into other domains.
+
+- Click a domain to show or hide its entities.
+- Hover over a domain and click the button that appears beside it (**Only show**) to show just that domain. Click it again to show everything.
+- Use **Show all** and **Hide all** to change every domain at once, and **Filter domains** to find a domain in a long list.
+- Turn on **Only references across domains** to show only the entities that reference, or are referenced by, an entity in another domain. This is a quick way to see the dependencies between domains.
+
+![The Global Entity Map with two domains hidden and only references across domains shown](./img/global-entity-map-filters.png)
+
+To give the diagram more room, collapse the panel with the button at its top right (or press <kbd>[</kbd>). The collapsed panel shows how many filters are on, so hidden domains aren't forgotten. The map remembers whether the panel is open in your browser.
+
+## Share a view
+
+The domains you've hidden, the **Only references across domains** filter, and the grouping are all kept in the URL. Copy the URL to share exactly what you're looking at. For example:
+
+```txt
+/visualiser/entity-map?hide=reviews,shopping&crossDomain=true&group=team
+```
+
+## Find an entity
+
+Use **Search nodes** at the top of the diagram to find an entity. Picking one moves the diagram to it and selects it.
+
+## Next steps
+
+- [Add entities to resources](/docs/development/guides/resources/entities/add-entities-to-resources)
+- [Model entity relationships](/docs/development/guides/resources/entities/model-entity-relationships)
+- [Entity maps](/docs/development/guides/resources/entities/entity-maps)

package/dist/docs/development/guides/resources/entities/{06-reference.md → 07-reference.md}

@@ -2,7 +2,7 @@
 keywords:
 - EventCatalog entities
 - Entity frontmatter
-sidebar_position: 6
+sidebar_position: 7
 sidebar_label: Reference
 title: Entities reference
 description: Frontmatter fields, paths, and routes for entities in EventCatalog.
@@ -43,6 +43,7 @@ Nested entities use the same `versioned/{version}/index.mdx` pattern inside thei
 | `/visualiser/entities/{entity-id}/{version}` | Entity resource diagram. |
 | `/visualiser/domains/{domain-id}/{version}/entity-map` | Entity Diagram for entities assigned to a domain. |
 | `/visualiser/services/{service-id}/{version}/entity-map` | Entity Diagram for entities assigned to a service. |
+| `/visualiser/entity-map` | [Global Entity Map](/docs/development/guides/resources/entities/global-entity-map): every entity in the catalog, grouped by domain. |
 
 ## Frontmatter example
 

package/dist/eventcatalog.cjs

@@ -33,11 +33,12 @@ var import_node_path22 = require("path");
 var import_node_http = __toESM(require("http"), 1);
 var import_fs = __toESM(require("fs"), 1);
 var import_node_path23 = __toESM(require("path"), 1);
-var import_node_url2 = require("url");
+var import_node_url3 = require("url");
 var import_node_module3 = require("module");
 
 // src/generate.js
 var import_node_path3 = __toESM(require("path"), 1);
+var import_node_url2 = require("url");
 
 // src/eventcatalog-config-file-utils.js
 var import_promises2 = require("fs/promises");
@@ -174,7 +175,7 @@ var verifyRequiredFieldsAreInCatalogConfigFile = async (projectDirectory) => {
 var import_picocolors = __toESM(require("picocolors"), 1);
 
 // package.json
-var version = "5.9.0";
+var version = "5.10.0";
 
 // src/constants.ts
 var VERSION = version;
@@ -273,7 +274,7 @@ var generate = async (PROJECT_DIRECTORY) => {
         plugin = plugin.replace("<rootDir>", PROJECT_DIRECTORY);
       }
       try {
-        const importedGenerator = await import(plugin);
+        const importedGenerator = await (import_node_path3.default.isAbsolute(plugin) ? import((0, import_node_url2.pathToFileURL)(plugin).href) : import(plugin));
         const generator2 = getDefaultExport(importedGenerator);
         await generator2({ eventCatalogConfig: {} }, pluginConfig);
       } catch (error) {
@@ -3090,7 +3091,7 @@ Run npm i @eventcatalog/core to update`;
 };
 
 // src/eventcatalog.ts
-var currentDir = import_node_path23.default.dirname((0, import_node_url2.fileURLToPath)(importMetaUrl));
+var currentDir = import_node_path23.default.dirname((0, import_node_url3.fileURLToPath)(importMetaUrl));
 var astroCli = import_node_path23.default.join(import_node_path23.default.dirname((0, import_node_module3.createRequire)(importMetaUrl).resolve("astro/package.json")), "bin/astro.mjs");
 var ASTRO_IN_FOREGROUND = { ASTRO_DEV_BACKGROUND: "1", ASTRO_PREVIEW_BACKGROUND: "1" };
 var program = new import_commander.Command().version(VERSION);
@@ -3576,7 +3577,7 @@ var startServerCatalog = async () => {
   const base = (config?.base || "/").replace(/\/$/, "");
   await runCommandWithFilteredOutput({
     command: process.execPath,
-    args: ["--input-type=module", "-e", SERVER_BOOTSTRAP, (0, import_node_url2.pathToFileURL)(serverEntryPath).href],
+    args: ["--input-type=module", "-e", SERVER_BOOTSTRAP, (0, import_node_url3.pathToFileURL)(serverEntryPath).href],
     cwd: dir,
     env: {
       PROJECT_DIR: dir,

package/dist/eventcatalog.js

@@ -7,12 +7,12 @@ import {
 import "./chunk-CA4U2JP7.js";
 import {
   log_build_default
-} from "./chunk-WN6ZFSXF.js";
+} from "./chunk-5QOG7UYZ.js";
 import {
   getLicenseStatus,
   printLicenseStatus
 } from "./chunk-AD7CL772.js";
-import "./chunk-26C26LFE.js";
+import "./chunk-EXBUNFIM.js";
 import "./chunk-YRZK7HKX.js";
 import "./chunk-CA6WCQ2T.js";
 import "./chunk-CPW6G62V.js";
@@ -39,10 +39,10 @@ import {
 } from "./chunk-NKNOXQ62.js";
 import {
   generate
-} from "./chunk-UIJUSHOT.js";
+} from "./chunk-EGOTM5ZG.js";
 import {
   logger
-} from "./chunk-SZU7I2PD.js";
+} from "./chunk-ZE2RPUNY.js";
 import {
   resolve_catalog_dependencies_default
 } from "./chunk-PD7KTSYN.js";
@@ -79,7 +79,7 @@ import {
 } from "./chunk-LFQJXLHG.js";
 import {
   VERSION
-} from "./chunk-C4L6B5KR.js";
+} from "./chunk-EETSYUKN.js";
 import {
   getEventCatalogConfigFile,
   verifyRequiredFieldsAreInCatalogConfigFile