Talk:Time Management with timeline

Process Anti-Pattern Observation

The whole point of using PKC is to leverage its powers in managing Namespaces. And you guys (Kevin & Jared) have been selfishly define namespaces in ways that are most convenient in your own private contexts, without thinking about Namespaces must be put in a "Single Source of Shared Truth", such as a single wiki or Git repository, to ensure the consistency and re-usability of the chosen names. This mental laziness causes systematic misunderstanding, and most seriously, delayed the possibility to make progress in a reasonable speed. Moreover, the explicit statement that all of your actions must be put into a Logic Model, which you both conveniently ignored, repeatedly caused our communication to go into directions that goes no where. This is really a sad condition that is now being documented here. One more time, all pages are specialization of the Logic Model, and this page included, must have a Logic Model. --Benkoo (talk) 09:32, 15 July 2021 (UTC)

TO BE DEPRECATED: When you see this, please consider moving the logic model below from Template:Logic Model to Template:LogicModel

1. Context	The lack of named spatial/temporal contexts will cause confusion in the process of communication
2. Goal	Use Logic Model to capture context, goal, success criteria in Wiki.
3. Success Criteria	Seeing Logic Model as a formal data structure to be included in pages that describes named entities.
4. Outputs	5. Process	6. Inputs
A Logic Model written by each page's verifier in PKC.	A compositional process to relate Inputs with Outputs.	PKC access # Content Creator #Page Verification Process
7. Boundary Conditions	The intersection of arrogance and stupidity.