Which records and relationships could a booking release contain?

A release for this workflow could contain the entities an environment needs to hold realistic, linked state. All of it is generated, shaped by direct observation of how real businesses operate, and none of it is a real business record.

**Core records**

- approvals, with amount, term, pricing, repayment frequency and conditions - borrowers and related parties, with roles such as primary borrower or security provider - facilities and their repayment schedules - security interests with type, status and lodgement reference - ledger entries for funding and fees

**Relationships**

Approvals link to conditions, facilities link to approvals and security, and exceptions link back to the record that caused them. Keys are stable so a joined query always resolves.

**Policy material**

Booking rules written as short documents, such as which conditions must be satisfied before drawdown and who may waive a documentation item. These let a task test whether an agent applies a rule instead of guessing.

**Exceptions and handovers**

Returned files, reason codes, owner roles and notes, so the environment can model work that ends without a booked facility.

Scope the entity list in a pilot, and inspect a sample for grounding and disclosure risk before wider use.