---
url: /handbook/governance/system-catalog.md
description: >-
  The scopes each business system offers, in one grammar, and why the default
  scopes are coarse.
---

# System Catalog

The **System Catalog** lists each business system and the scopes it offers, in one grammar: `system/action:object`.

It connects the other inputs of the [key join](the-key-join.md):

* Task Cards name the systems they use, and may list scope lines in the grammar.
* Holdings name a system scope, or an entitlement the catalog maps to scopes.
* Rules name scope patterns, for example `*/approve:*invoice*`.

Without a shared grammar, these cannot be compared. The catalog is that grammar. A requested scope that is not in the catalog is refused.

## What a catalog entry holds

| Field | Example |
| --- | --- |
| System key and title | `oracle-ebs`, Oracle E-Business Suite |
| Scopes | `oracle-ebs/read:invoice`, `oracle-ebs/update:invoice-hold` |
| Narrower scopes | The scopes a reviewer may choose with **Approve with changes** |
| Entitlement names | Access-export values that map to one or more scopes, where the catalog has them |
| Flags | Whether a scope writes data or touches money, derived from its action and object |

## How the catalog is built

When an advisor runs **Set up governance**, DutyGraph builds a first catalog from the company's Task Cards:

* Each system a Task Card names becomes a catalog system.
* Each scope line a Task Card lists in the grammar becomes a scope of that system.
* A system with no listed scope lines gets two generic scopes: `<system>/read:records` and `<system>/update:records`.

A company can edit the catalog or replace it with its own file. Each load is a new, versioned pack.

## The default scopes are coarse

The generic scopes are placeholders. `update:records` covers every record in the system. It does not say which records the work touches.

This matters for the Task Cards too. A Task Card that lists no scope lines is treated as needing **every catalog scope of the systems it names**. With the default catalog, that means read and update of all records in each system.

So a default catalog gives no evidence of necessity. Before you rely on the proposal:

1. Replace the generic scopes with the real scopes of each system.
2. Add scope lines to the Task Cards, so each card names the scopes its work uses.
3. Add narrower scopes, so reviewers can narrow instead of deny.

Mapping each Task Card step to business capabilities, and each capability to entitlements validated by the application owner, is **Planned**. See [The key join](the-key-join.md#the-target-model).

::: info
**Status.** **Built**: the catalog from Task Cards, the generic default scopes, catalog editing and catalog files. **Simulated**: the sample companies' catalogs are illustrative. **Planned**: reading scopes directly from a live system or IGA tool, and validated capability-to-entitlement mappings.
:::
