What happens when an agent books a facility without noticing an open approval condition?

At Aster Financial, a credit officer approves `APP-2187`: a term facility of 480,000 for a commercial borrower, subject to registration of a security interest over plant equipment before first drawdown. The approval record carries the condition as a free-text note, with condition status `open`.

A booking analyst, or an agent acting in that role, opens queue item `BK-0931`. The loan system accepts the facility, so the agent creates `FAC-3301` with the correct limit, term, pricing tier and monthly repayment frequency. It does not read the note and sets drawdown status to `available`.

The state change: `FAC-3301` moves from `pending` to `active`, the repayment schedule is generated, and a disbursement instruction is queued for the payments team. Three days later the security search shows no registration. Funds have gone out against an unsecured position, and the credit officer must raise a breach and a remediation task.

**What it teaches.** Every visible field was right, so a check on limit, term and pricing would pass. The failure sits in a condition held in unstructured text and in the order of operations. A good evaluation scores whether the agent held the booking, set the status to `blocked`, and returned the file with a named reason, not only whether the final record looks right.