THE PROJECT, AS A CALENDAR DECIDE  Feb – 2 Apr DESIGN  Apr – May PROVE  wks 8–11 OBSERVE  launch – quarter OPERATE  the year idea → production: 16 weeks · governance: ongoing PLAN OF RECORD →
OsterNet · Scheduling & Rooms · rollout 2014
MonthWeekDayRoomsPrint logged in: okafor.d · third floor

February

project yearDECIDE · it begins with one sentence, late February

March

project yearDECIDE · five of the calendar's densest weeks
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

April

project yearDECIDE → DESIGN · the seam is a memo, not a meeting
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

May

project yearDESIGN · the persona month
6 May is canon (glance p.69) · persona review placed before it ⊕

Prove

project clockPROVE · dated in weeks; the bible fixes no months here

WK 8WK 10WK 11 · the version number is the fix loop

launch follows within the week · rung 2, nothing above the break

August

operating months, launch clockOBSERVE · one meeting; the calendar cannot see the incident
SunMonTueWedThuFriSat
1
2
3
4
R. Vaughn's spot check finds the 21 July send, by the account name · fourteen days after it went out · no meeting existed about it until now
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

The operating year

launch + 12 monthsOPERATE · the meetings thin out; the documents govern
this row is deliberately thin · five transcript meetings sit in the first sixteen weeks and one sits here at zero · the white space is the argument
CF-021 Designed composite · dates marked ⊕ are placed for layout