CONTACTS 

SUBJECTS
Augment Upgraded with Java, by Jack Park, Brian Lincoln, per Pat Lincol
Java Upgrade Augment Task is Not Actually Being Performed
Hyperscope Architecture Progress Delayed, Doug Engelbart
Open Sourse Slow Progress Hyperscope Architecture OHS, Doug Engelbart
Open Source Causes Disputes Delays Progress
Engineering Management Requires Accountability Authority
Augment/NLS, 000124
Augment Improved by SDS and Java, Jack Park's OHS

2610 -
2610 -    ..
2611 - Summary/Objective
2612 -
261201 - Follow up ref SDS 73 BV3W.
261202 -
261203 - Received ref DRT 1 0001 from Jack Park correcting the record on 001220
261204 - where it was understood from Pat Lincoln that Jack and Pat's brother,
261205 - Brian, are developing a translation of Doug's Augment NLS program
261206 - using Java. It was, also, understood at that time that Jack confirmed
261207 - this work is underway. ref SDS 73 UZ9L
261209 -  ..
261210 - Jack is responding to a copy of a letter sent to him that was
261211 - submitted to Doug Engelbart yesterday on 010111, ref DIP 6 0001, that,
261212 - also, submits the record of a telecon with Doug on 010111, ref SDS 80
261213 - IB9F, notifying about the record on 001220, as a basis for possible
261214 - action to meet a current objective. ref SDS 80 IB9F
261215 - ..
261216 - In his letter today, Jack clarifies the record on 001220.
261217 - ref DRT 1 IO5M
261218 -
261219 -      Notified Jack by email that his clarification has been entered.
261221 -  ..
261222 - Jack relates that Pat Lincoln wrote a letter to Jack asking about
261223 - progress with java augment.  Jack recalls having reported back to Pat
261224 - that he and Howard had a low priority background project going on
261225 - this, and that Jack had met with Doug and began to mine the augment
261226 - help screens, and Howard had begun to sketch out an ontology using
261227 - Protege. ref DRT 1 009G
261229 -  ..
261230 - Jack does not provide original sources showing chronology, content and
261231 - context.  On 950204 the fragility of human memory was reviewed.
261232 - ref SDS 6 0550
261233 - ..
261234 - Jack recalls that at the SRI event for Doug on 001220, he
261235 - followed up the prior correspondence by asking Pat about his interest
261236 - in Jack and Howard's work on "java Augment."  Jack relates that Pat
261237 - indicated his brother, Brian, could participate, i.e., Brian's name
261238 - came up."  Jack remembers saying that was a great idea to include
261239 - Brian in the project. ref DRT 1 XU8K
261241 -  ..
261242 - That is as far as things have gone.  Jack does not recall having
261243 - confirmed that he and Brian are at work on the project; rather, he
261244 - intended to convey that some discussion with Pat had occured about
261245 - doing such a project. ref DRT 1 KV8O
261246 -
261247 -     [On 010329 Jack indicates new project to upgrade Augment with Java
261248 -     and a form of SDS Jack calls Structured Dialog System, may be
261249 -     pursued to support OHS. ref SDS 82 A13H
261250 - ..
261251 - Jack says about diverting to HyperScope, that's the first time
261252 - he has heard about that.  He is always working on things HyperScope
261253 - related. ref DRT 1 005I
261254 -
261255 -    This record indicates Jack submitted a letter to Pat reporting that
261256 -    Jack and Howard had a "low priority project going" to upgrade
261257 -    Doug's Augment NLS program using Java.
261259 -     ..
261260 -    A "going project" often connotes work is underway.  Jack may have
261261 -    intended to convey that no actual work is being done, until
261262 -    authorization and funding are provided, discussed with Doug on
261263 -    000327, ref SDS 22 5402, by describing the project as "low priority
261264 -    background."
261266 -     ..
261267 -    Jack may have been inquiring at the SRI event for Doug on 001220
261268 -    whether SRI would support the "going project," as discussed at SRI
261269 -    during the meeting on 001017, ref SDS 41 0784, but he did not spell
261270 -    out in so many words that doing this work requires management,
261271 -    authority and funding.
261272 -    ..
261273 -    Pat responded that his brother Brian would assist Jack and
261274 -    Howard on the Augment Java low priority background project, under
261275 -    Open Source practices of volunteering time for a worthy cause, when
261276 -    possible.  Grant Bowman explained open source practices in a letter
261277 -    on 001012, ref SDS 39 PT5M, reflecting earlier "termite" work
261278 -    methods explained by Paul Fernhout on 000829. ref SDS 34 0001
261280 -     ..
261281 -    Accordingly, Pat continued to believe following the exchange with
261282 -    Jack on 001220 that an ongoing project was underway, which
261283 -    justified passing this understanding to Rod Welch.  The record on
261284 -    001220 therefore substantially agrees with Jack's report today.
261286 -     ..
261287 -    Jack's correction shows that evidently "low priority background"
261288 -    means that no work has been done, and there is no "going project"
261289 -    to translate Augment to Java, and that no coordination has been
261290 -    done with Brian to plan or perform any work on this.
261291 -    ..
261292 -    As a result, there are no resources to divert for working on
261293 -    the Hyperscope, contrary to the idea advanced to Doug yesterday.
261294 -    ref SDS 80 IB9F
261296 -     ..
261297 -    Jack advises that the work he is doing supports Hyperscope
261298 -    objectives, ref DRT 1 005I, which are set out in the Launch Plan
261299 -    submitted by Doug on 001025. ref SDS 44 ADK1  Jack explained in a
261300 -    letter on 000426 the process of developing product architecture.
261301 -    ref SDS 23 0304  Since then, Jack has submitted important ideas on
261302 -    developing an architecture for OHS, for example on 000623,
261303 -    ref SDS 28 9900, and more recently on 001130. ref SDS 65 0001  Eric
261304 -    Armstrong submitted a series of requirements for OHS, an example is
261305 -    on 000505. ref SDS 25 0001  This record shows the DKR team may have
261306 -    the talent to develop an architecture for Hyperscope, per Doug's
261307 -    objective discussed on 010111. ref SDS 80 0002
261308 -    ..
261309 -    On 001028 Jack explained advantages of open source
261310 -    development, ref SDS 46 ADK2, commenting on analysis of challenges
261311 -    identifed in a record for 001025, which make open source
261312 -    problematic. ref SDS 44 ADK1
261314 -     ..
261315 -    On 001101 Jack submitted a report that VA Linux has encountered
261316 -    problems using open source. ref SDS 48 HW9F
261318 -     ..
261319 -    On 001106 Eric reported snags in developing an architecture for
261320 -    OHS. ref SDS 50 0001  On 001122 Eric reviewed pending issues on
261321 -    this matter. ref SDS 61 0001
261322 -
261323 -
261324 -
261325 -
261326 -
261327 -
2614 -

SUBJECTS
SDS Not Perfect Truth
Accuracy Feedback Discovers Misunderstanding Before Mistakes are Made
Accuracy Requires Continual Renewal Connections Cause Effect Avoid De
Truth Accuracy Derived from Communication Collaboration

3206 -
320701 -  ..
320702 - Feedback Important Communication Metric to Strengthen Accuracy
320703 -
320704 - Jack correctly observes that SDS does not represent a perfect memory.
320705 - ref DRT 1 0001
320706 -
320707 - SDS has a pretty good "memory" of what is entered.  The organization
320708 - of the record, (which correlates to Jack's ideas about "ontology," --
320709 - see for example on 000221, ref SDS 20 2622), aids in entering new
320710 - information, and making connections of cause and effect, and setting
320711 - alignment with history, objectives and requirements, i.e., context.
320712 - SDS, also, aids in assembling chronologies that help refine accuracy
320713 - and understanding over time, for decision support.
320715 -  ..
320716 - Time impacts accuracy.  Limited time causes cursory understandings
320717 - which may be incorrect or imprecise, under the rule, haste makes
320718 - waste.  This can occur at the time information is received, or later
320719 - when it is entered.  The passage of time between getting information
320720 - and capturing it in a permanent record, also causes errors, large and
320721 - small, due to meaning drift, explained on 960518. ref SDS 8 3734
320722 - ..
320723 - The amount of communication impacts accuracy of information due
320724 - to "meaning drift," as explained in analysis on the high cost of
320725 - medical mistakes, ref DIP 1 6048, developed on 990924. ref SDS 16 5576
320726 - This occurs because the human mind "recodes" information into its own
320727 - unique context to facilitate understanding and memory, reported on
320728 - 990303. ref SDS 14 2838
320730 -  ..
320731 - Thus, the chance of error in communication is pretty big, as noted by
320732 - Drucker in the record on 931130. ref SDS 4 3851  Indeed, Welch holds
320733 - that communication has become the biggest risk in enterprise, see
320734 - POIMS. ref OF 1 VX7N
320736 -  ..
320737 - Communication Metrics is a management science that uses SDS to support
320738 - a continual process of refining accuracy, beginning with initial
320739 - impressions by jotting down what is gathered from daily working
320740 - information, such as email, attending events, calls, etc.
320741 - ..
320742 - Jack is correct to emphasize accuracy of the record, because
320743 - memory is a primary source of human reasoning, reported in the record
320744 - on 900303, ref SDS 1 3002, and later on 900319. ref SDS 2 1323
320746 -  ..
320747 - Professor Mary Keeler explained in a presention at SRI on 000518 that
320748 - "truth" is a major objective of knowledge  It requires a constant
320749 - process of refining accuracy, as information is gathered from feedback
320750 - over time, ref SDS 27 O43M, like Jack's letter today, per above.
320751 - ref SDS 0 0001
320753 -  ..
320754 - Professor Keeler's paper on the philosophy of Charles Peirce, which
320755 - Jack submitted on 000515, offers a similar concept that knowledge
320756 - requires a continual process to refine accuracy, and notes that
320757 - absolute accuracy is not attainable. ref SDS 26 7380
320758 - ..
320759 - That is why feedback is an important part of "intelligence"
320760 - explained in POIMS, ref OF 1 3774, and a critical "metric" of
320761 - communication set out in the NWO. ref OF 2 0936
320763 -  ..
320764 - Since accuracy is important, Communication Metrics strives to obtain
320765 - corrections in understandings before harm is caused.  The event for
320766 - Doug at SRI was held on 001220.  A letter was submitted to the project
320767 - team within a day or so, transmitting the record. ref SDS 73 GG6L
320768 -
320769 -    [On 010114 feedback to enhance accuracy cited as practical
320770 -    objective of KM. ref SDS 81 GZ6M
320772 -  ..
320773 - Submission of the record for 001220 provided early opportunity for the
320774 - team to provide feedback with additions and corrections.  As people
320775 - gain experience with using record to manage the work, greater
320776 - attention will be given to providing timely feedback that ensures
320777 - accuracy, so that subsequent activity is properly grounded, which Jack
320778 - urges today.
320779 - ..
320780 - For more on the role of feedback see the record on 961017.
320781 - ref SDS 11 1381, particularly ref SDS 11 2068
320782 -
320783 -
320784 -
320785 -
320786 -
3208 -

SUBJECTS
Psychologically Demanding to Discover Error Constantly
Communication Manager Buffers Shock of Management Details
Feedback Accuracy Metrics Listening
Psychological Anger Discover Communication Not Aligned
SDS Not Perfect Truth Not Accurate
Psychologically Demanding Com Manager

4208 -
420901 -  ..
420902 - Debugging Management Not a Popular Task
420903 - Communication Manager Emotionally, Psychologically Burdensome
420904 -
420905 - Jack has been generous throughout the year complimenting the SDS
420906 - record prepared for the DKR project, using Communication Metrics, for
420907 - example....
420908 -
420909 -      1.  On 000426 he cited SDS as proof of concept for DKR.
420910 -          ref SDS 23 3315
420912 -           ..
420913 -      2.  On 000503 Jack commented favorably on the Com Metrics concept
420914 -          of Knowledge Space, ref SDS 24 6138, developed on 960620,
420915 -          ref SDS 10 3516, and explained in POIMS. ref OF 1 034J
420917 -           ..
420918 -      3.  On 000630 Jack commends the SDS record as one way of applying
420919 -          KM usefull. ref SDS 29 2870
420921 -           ..
420922 -      4.  On 001116 Jack noted the usefulness of SDS records for
420923 -          supporting KM. ref SDS 58 0001
420925 -  ..
420926 - Additionally, Jack has throughout this period requested corrections
420927 - and made clarifications to the SDS record.
420929 -  ..
420930 - This history supports a conclusion that Jack's correction today is not
420931 - intended to criticize the process, nor to question the integrity of
420932 - the Communication Manager.
420934 -  ..
420935 - None-the-less, absent the history of support, it would be reasonable
420936 - to draw from Jack's remarks that he is not pleased with the record on
420937 - 001220, and objects to using that record for supporting proposed
420938 - action on 010111.  Jack seems to be saying in his letter today...
420939 - ref DRT 1 0001
420940 -
420941 -         ..
420942 -      Hey, Rod, you have a good memory, but it is short...
420943 -
420945 -  ..
420946 - This prospect draws attention to value added by the Communication
420947 - Manager role, which presents another parallel with accounting, where
420948 - the process is disparaged as "bean counters," bereft of any concern,
420949 - except aligning figures on a ledger.  This makes it useful for
420950 - accountants to be a separate profession in order to render a measure
420951 - of objective skill, that can withstand rancor and pressure to bend the
420952 - process.
420954 -  ..
420955 - The NWO... explains "feedback" in communiation is not a fun process,
420956 - but is essential for accurate understandings, per above, ref SDS 0
420957 - M2WS  Andy Grove made a similar point in his book, "Only the Paranoid
420958 - Survive," reviewed on 980307. ref SDS 12 4697
420960 -  ..
420961 - Recognizing that communication has a high risk of error, and that
420962 - productivity of knowledge work, like managing, medicine, engineering,
420963 - marketing, etc., is directly related to accurate understandings, there
420964 - is a significant psychological burden on the Communication Manager in
420965 - striving to capture the record quickly, before truth slips away, while
420966 - knowing that the record is only an approximation of truth, and so, of
420967 - necessity, will contain errors, because the architecture of human
420968 - thought buffers the conscious mind from most mistakes, see NWO.
420969 - ref OF 2 2921  The Communication Manager's job is to discover hidden
420970 - mistakes, and present them in a constructive way so that people are
420971 - empowered to make adjustment in time to avoid delay and loss that flow
420972 - from actions predicated on communication.
420974 -  ..
420975 - Getting feedback that improves accuracy, increases stress performing
420976 - Communication Metrics.  For one thing, is there enough time to
420977 - incorporate corrections?  Should the record be changed, or merely
420978 - annotated?  How do we organize the record after it is changed?
420980 -  ..
420981 - Additionally, some people get mad sometimes when they see a record
420982 - that conflicts with their understanding of the truth.  Some people get
420983 - mad everytime they encounter conflicting records, and immediately
420984 - assume others deliberately misrepresented the truth.  Some people get
420985 - mad because the truth is presented rather than an erroneous story they
420986 - want presented to cover up, obfuscate, and conceal truth.  Some poeple
420987 - recover quickly, others do not.  The fact that "truth" is a moving
420988 - target, reported on 950412, ref SDS 7 4543, is overlooked in the heat
420989 - of the moment.
420991 -  ..
420992 - This environment presents risks of intimidation and stress that reduce
420993 - issuing feedback under a variety of scenarios. see NWO. ref OF 2 2670
420995 -  ..
420996 - For these reasons, it seems that a separate profession is needed to
420997 - perform Communication Metrics, similar to accounting in the financial
420998 - arena. see again NWO. ref OF 2 0468
420999 -
421000 -
421001 -
421002 -
421003 -
421004 -
421005 -
421006 -
421007 -
4211 -