Which records and relationships can a generated set-up release contain?

A generated release can be shaped around the objects a set-up worker touches. A buyer can ask for some or all of them.

- **Decisions:** approvals, acceptances or signed agreements, with conditions, approver role and effective and expiry dates. - **Parties:** customers, organisations and contacts, including near-duplicates and records with missing or conflicting fields. - **Accounts or services:** facilities, subscriptions, service connections or engagements, each with a status and configuration. - **Conditions:** items that must be satisfied before activation, with their own status and evidence references. - **Policies:** written rules that say which tier applies, who may override and what must be recorded. - **Tasks and cases:** queue items, reopened work and exception cases. - **Handover notes:** messages to billing, support, fulfilment or a relationship owner.

Relationships matter as much as the records. A decision links to a party, the party to an account, the account to conditions and cases, and each case to the notes written about it.

It can also include noise a real queue contains, such as stale approvals and incomplete forms. All of it is generated, informed by direct observation of how businesses operate, so the sample should still be inspected for grounding and disclosure risk.