The app doesn't need to try to guess my intention, it only needs to know that whatever I type needs to be saved. Deleting the document is up to the user; preserving the content should be up to the operating system.
The model may be advised by the OS, but it's not the OS's job to ensure that an application saves its data in a timely manner. It's the application's job.
Currently, there are two models which are prevalent: the "document" model, which hasn't changed much since the original Mac in 1984, and the "database" model, in which every action is immediately written to disk. Most apps choose one or the other; some apps (eg, DevonThink) choose to implement a little of both (in DevonThink, all "database" operations like organizing entries, etc, are in a database model; all "text" operations like adding something new to a note are in a document model).
A few "database model" apps you likely know and use:
- iTunes
- iPhoto
- iChat
- Address Book
A few "mixed model" apps you likely know and use:
The "document" model is the one most users expect from a computer,
especially when entering text, and so it is the one which is used by default in the vast majority of apps. Apps which use the "database" model have to explain this to their users, and field complaints about it, and mitigate confusion over the missing "save" actions et al. A user-level change in expectations could come about either by more of these database-model apps becoming prevalent or by the OS vendor with a respected HIG spec (aka, Apple) making such a model more advised. Of course, that's only if it really is a better model for most applications, and I'm still not convinced it is right for "most" text entry.
IMHO, things like TaskPaper should operate on a database model. As soon as I finish typing in a task, it should get written out to disk. However, longer-form text entry doesn't have a reasonable "break" point at which it should save. We end up there with timed auto-saves, which are the worst of both worlds (the save happens mid-sentence or at least mid-thought, and overwrites what had been on disk with what I might not have wanted to write out), or temporary-timed-auto-saves (which auto-save to a "recovery" area instead of just overwriting what is on disk).
In any case, it's not necessarily the OS's "job" to do this (and Palm doesn't do this either, although the combination of non-volatile memory and well-behaved apps gives that illusion; I've lost typed notes on a Palm before due to the application crashing). The OS vendor can make it a "best practice", but they can't force applications to write every state change out to disk the second it happens.