Tags can't compete with deep hierarchy for PKM, due to the unmaintainability of the former. The Textmind algorithm causes constant hierarchical evolution to meet one's changing needs. Achieving the same effect with tags is impossible without causing a giant mess. And without continual nomenclature refactoring, detailed quality thought simply isn't possible. Textmind actually realizes what other systems merely aspire to - the notetaking process is the thinking process.

I've begun identifying the points of resistance to Textmind adoption. One of them is learned helplessness. Most potential early adopters have already tried deeply nested file hierarchies and been burned. They failed due to lack of Treefactor for ergonomics and Textmind algorithm for JIT refactoring.

Similarly, daylogging as one's primary capture is an unorthodox workflow, because until now Treefactor hasn't existed to make the post-jog refactoring feasible.

Serious people have taken a hard look at PKM and failed to arrive at the correct solution. In a sense I'm fortunate that they didn't preempt me. But now I must overcome their incumbent position.

Doing so will take time and proof. Fortunately I anticipated the possibility of a long haul, and planned for it from the start. The Bibliodemos demo grinds slow, but it grinds exceedingly fine. In the meantime, Cyborganize runs fine as a side project that synergizes with my profession.

There is so much to do, that it's difficult to know what to do next. I'm rewriting cyberthal-docs based on feedback and reflection, correcting serious flaws in initial presentation, and clarifying that Textmind is similar to the original Zettelkasten paper method, which had deep hierarchy. I also plan to add blog comment support and increase ease of email contact. These are forum precursors.

Pubmind is newly launched and performing admirably in its intended role. It has greatly shortened the lag between ideation and publication. Content volume per effort ratio is fantastic. "Ready Fire Aim" iteratively improves executive orientation. Writing T2 content by referring to exported Textmind headings and T3 riffs is easy and pleasant. The road to 1,000 books is flat and straight; what more can one ask for?