Best Practice vs Pattern vs Standard Work

I noticed that the Yahoo! Design Pattern Library has a curious definition for a Pattern borrowed from the IAWiki:

Patterns are optimal solutions to common problems. As common problems are tossed around a community and are resolved, common solutions often spontaneously emerge. Eventually, the best of these rise above the din and self-identify and become refined until they reach the status of a Design Pattern.

The emphasis is on the optimal solution out of a set of common solutions (aka Best Practice)

Christopher Alexander in The Timeless Way of Building describes a Pattern somewhat differently:

Each pattern is a three-part rule, which expresses a relation between a certain context, a problem, and a solution.

As an element in the world, each pattern is a relationship between a certain context, a certain system of forces which occurs repeatedly in that context, and a certain spatial configuration which allows these forces to resolve themselves.

As an element of language, a pattern is an instruction, which shows how this spatial configuration can be used, over and over again, to resolve the given system of forces, wherever the context makes it relevant.

The pattern is, in short, at the same time a thing, which happens in the world, and the rule which tells us how to create that thing, and when we must create it. It is both a process and a thing; both a description of a thing which is alive, and a description of the process which will generate that thing

Instead of emphasising "optimal solution", the emphasis is on context, on a system of forces, and on a configuration that allows the forces to resolve themselves.

These days, I'm more interested in Standard Work. From Workplace Management by Taiichi Ohno...

There is something called standard work, but standards should be changing constantly. Instead, if you think of the standard as the best you can do, it's all over. The standard is only a baseline for doing further kaizen.
...
When creating Standard Work, it will be difficult to establish a standard if you are trying to achieve "the best way." This is a big mistake. Document exactly what you are doing now.
...
If you are observing every day you ought to be finding things you don't like, and rewriting the standard immediately. Even if the document hanging here is from last month, this is wrong.
...
If it takes one or two months to create these documents, this is nonsense. You should not create these away from the job. See what is happening on the gemba and write it down.

The emphasis is on a baseline for continuous improvement, on documenting exactly what is done rather than the best way, on rewriting the standard immediately when improvements are made, and on doing all of this at the place of work.