changelog


For the core c.os model we use the following versioning scheme: functions-major.functions-minor.core-practices (fmj.fmn.cp).. For example 1.0.04
The Core Practices revision number is reset when a new Functions revision is issued.
Each domain has its own version id using the following format: core-model-version.domain-name.domain-practices (dn.dp) where domain-name is fixed. For example 1.0.04.org.001. The core model revision is the one from which the domain-level is derived. The Domain Practices component is never reset.
Editorial revisions shall be denoted using an ‘e‘ component, which will be removed in the next non-editorial version. For example, an editorial change in a function’s overview can be marked as 1.2.09.e01. When one of the model’s components advances, the new revision will be for example 1.2.10.


February 26, 2021

New Wonder practice: Feel Doubt — Welcome Ambiguity

February 26, 2021


February 18, 2021

Adding Reflection Cues to Affect the Operating System and Let It Affect You and Record and Reflect

February 18, 2021


February 6, 2021

Refining two Core Practices: Embrace the Unknown — Expected the Unexpected and Take Detours — Get Lost.

February 6, 2021


February 1, 2021

The first release of the core c.os model.

February 1, 2021


Share this page and help us inspire more people to realize their creative potential

Scroll to Top