Kept, Unprompt Banks, Kept Banks, Domains and Space Banks,
The Stonewall Defence, A matter of Promptness, This is a promising but premature approach. (needs title),
Confinement bug; Bank Allocation, The Frame Perspective, Keepers, Extended Banks.

These need review and conflict resolution if possible. I wanted to record this evening’s insight stemming from dinner with Markm. The least demanding requirement for a bank keeper may be as follows. When the bank cannot perform some normal request, presumably to buy material, it keeps the resume key of the requester while it calls the keeper. While the keeper runs the bank is waiting and unavailable. Banks with keepers are not promised as prompt. I think that some of the above pages assume more stringent requirements. When I am more awake I will research this.

There are at least two advantages of the keeper pattern:

• Most invocations of the kept object avoid extra messages. Admittedly the exceptional cases must be tested for but this was already necessary in the extant uses of this pattern.
• More fundamental, the kept object may be trusted by its user more than the user trusts the keeper. Even a kept bank can vouch to a user that the pages are clean and private. The keeper is not in a position to break that agreement.