157 donate 12thFLgal. blood 159 154 144
101 locate comfort solitude 4
………..
LIFE-FLOW is usually measured in time units. This web-site is for the current year, for example. For another time-unit, this blog-site concerns weekly self-organization activity.
LIFE-FLOW can also be seen apart from time-units -- LIFE-FLOW can be seen as A LOGICAL PROGRESSION of lifetime acts, toward death if you wish, but more lofty, TOWARD A VISION, mission statement, aim, or goal.
Harv's vision is "82 experience joy-love-freeing 70 79 80 81 86 87 95 111 120 125 126 138" as of 2023week47.
BUT, putting that complexity aside for now, let's begin back at the the 23w47 calendar snippet's first life-flow act of the day -- "surf internet". This verb-noun act description/record is a 'wholly hour' meaning that calendar life-flow acts are to be calendar-measured in whole hours only, for practicality.
The next snippet act is "118 sleep 93" -- a nice simple example for further explanation -- "118" is the act#, "sleep" is the verb, and "93" is the pre# -- more on that follows.
Previously, "internet" was the example noun of that verb-noun act description/record. The use of record brings explanation of the simplified database record of Theory-W, that of "act# verb-descriptor-noun pre#(s) who when where worth ...". The v-d-n description is "what", and the overarching purpose of the precedence-network-database is the why<--->way, that is, the act#<--->pre#(s).
Back to "118 sleep 93", "118" is the act#, "sleep" is the act, "93" the pre#. From the database, find act# "93" as "93 prepare comfort sleep". Note that "prepare comfort sleep" is not 'timed' on the calendar -- in Harv's case "prepare" is absorbed in "sleep'. As a point of curiosity, in the database, the "what(s)" are highlighted in light blue color.
In precedence-network parlance, those two acts are written/read in narration as in either direction -- 118 sleep 93 <---> 93 prepare comfort sleep. From "prepare" reading to the left answers the question why, that is "sleep". The how/way of "sleep" reads to the right, that is 'prepare".
For Otto's self-organization as of week 47 is written below. In fancy terms, it is written in the language of precedence-network-database (PNDL). For corporate entities the database is easily sorted into job descriptions for study.
2023nov11. The second-week iteration of this precedence network application, elevates its self operation portrayal, to a higher level, that is, ultimately to joy-love-freeing, away from sad-hate-fear, for self-another-others -- the organization's vision. A narrative form of corporate vision are mission statements, published in most annual reports.
actualized current week 23w47 — act# 139 and prior.FLAW FOUND -- RETHINK and REWRITE required -- ...Self Happenings (weekly blog posts) are written in the language of data-base precedence-network language (Harv's conglomeration) using verb-descriptor-noun phraseology. Example: first, characterize a chosen action of an organization with another act# = #3 state organization mission #2 , where #3 act is the why of #1. Back to act#1 WRITTING INTERRUPTION
#2 is #1's preceding act number; second, determine the why of #1 ask why or how (the way) to #1. If you ask why, then the answer could be -- #2 explain precedence network #1. In a database record format that means #2 is preceded by #1. In flow chart language that would be charted as (explain...) <--- (characterize...) ,and read in 'why<---way protocol' as "the way to (#2explain...) is to (#1characterize...).
Moving to a more complex example of an actual week (2023week46) in an organization, the below example data has 90+ 'explained' acts. Go to the middle of the week's data set, and read "52 study retirement operation." Fifty-two (52) is the act#, "study retirement operation" is the "VERB-DESCRIPTOR-NOUN action phrase." Now scan the 90+ date set for the number fifty-two in the pre# position.
Harv's Theory-W conglomeration gives;instant publishing;
a database replacement for time-consuming and eventually impossibly obsolete PERT/GANDT-type chart drawings (WHY <---> WAY);
expandability to WHO, WHEN, WHERE, HOW(the WAY), that is, job descriptions for better effectiveness leverage; Proven at DeZurik for 10% bottom-line profit improvement ($5,000,000).technical project control; Proven at Mercury Marine Engineering with two sets of reconciled $ books, one for budget control, the other for project effectiveness....can Theory W (Functional Organization principles apply to Self-Organization ? Decades later -- still trying.
……….. expansionary comments apart from the above narrative
174 loop example