Appearance
Set up governance
An advisor or administrator turns on governed agents for a company in Agents › Rules › Set up governance.
The six packs
| # | Pack | Default |
|---|---|---|
| 1 | Agent rules | 14 neutral rules, including CEIL-01, CEIL-02 and AGT-12 "No agent approves work". CEIL-02 is listed but not yet enforced. |
| 2 | SoD rules | 12 default risks, expanded against the catalog |
| 3 | Mitigating controls | Default controls, with the principal types each may cover |
| 4 | System Catalog | Built from the systems named in the company's Task Cards. A system with no listed scopes gets generic read:records and update:records. |
| 5 | Holdings | From an uploaded access-export CSV |
| 6 | Approval chain | Company people, or the requester's manager |
Each pack can be replaced with the company's own file.
What happens on load
- DutyGraph stores each pack as a new, immutable version.
- It writes a "pack sealed" entry to the ledger.
- It reports holdings rows that match no person and access that matches no catalog scope. It does not load them.
To change a pack later, open Change packs. The old version stays on record.
Task Cards in the registry
Setup gives each eligible Task Card a governance id, such as TSK-0001. A Task Card is eligible when its AI mode allows AI and it maps to catalog scopes.
Its needed scopes are the scope lines it lists. If it lists none, DutyGraph uses every catalog scope of the systems it names. With the default catalog, that is read and update of all records in each system. This is coarse. See System Catalog.
Before real requests, replace the generic scopes with each system's real scopes, and add scope lines to the Task Cards.
INFO
Status. Built for any company: the six packs, versioning, the ledger entry, the unmatched-row report and the Task Card registry. Planned: enforcing CEIL-02, and loading packs straight from live identity and IGA systems.
Source: gitbook/product/governance/set-up-governance.md in the DutyGraph repository.