Which records and relationships can a generated facility dataset contain?

A release can model the facility as a connected set of records instead of a single table. The value for training comes from the links.

**Core records** - Approval, with limit, purpose, conditions and approver role - Offer letter, with terms that may or may not match the approval - Facility and sub-limits, with status history - Parties: borrowers, related entities, sureties, and their roles - Security: charges, insurance, valuations, registration references - Repayment schedule and fee schedule - Tickets, queries and handover notes

**Relationships** A facility links to one approval and one or more offers. Parties link to the facility with a role and an effective date. Security links to parties and to facilities, and one asset can secure more than one facility. Conditions link to evidence documents, and each evidence item has a status.

**Policy layer** A dataset can include the rules that govern the work: which conditions block drawdown, which roles may override a hold, and what must be recorded for an exception.

**Variation** Cases can vary by product (term loan, line of credit, equipment finance), by document quality, and by how many exceptions are present.

All of it is generated. A buyer should inspect whether relationships are internally consistent and whether any pattern is too close to a recognisable real organisation.