# Processing definitions

URL: /systems/trust-and-governance/controls/processing-definitions · Id: `control:processing-definitions`

> Every Noun and Verb publishes its fields, types and effects, so each Interface processes data from one definition.

Every [Noun](/business/nouns/noun) and [Verb](/business/nouns/verb) publishes its fields, types and effects, so each [Interface](/business/nouns/interface) processes data from one definition.

## Satisfies
| Criterion | Text |
| --- | --- |
| [SOC2 PI1.1](/systems/trust-and-governance/criteria/soc2/pi1-1) | The entity generates and communicates relevant, quality information about processing, including definitions of the data it processes. |

## Implemented by
- [Product definition](/workflows/processes/product-definition)
- [Define a Product](/workflows/processes/product-definition/define-product)
- [Database](/code/platform/capabilities/database)

## Test
| Step | Rule |
| --- | --- |
| Kind | Preventive: it stops the failure before it happens. |
| Select | Every Interface Version deployed in the report period. |
| Assert | Each was generated from the Noun and Verb definitions in force, with no hand-written field outside them. |

## Owner
[Product Lead](/agents/product/product-lead), [Product Team](/agents/product).

## Example
A permit-status API adds an `issuedAt` field to `Permit`. The API, CLI, MCP server and SDK all expose it from that one definition, with no hand-written field anywhere.