Documentation is important
Peter reflects on how Workbench grew from support tooling into the shared engine coordinating his projects and workers.
A documentation project that manages itself
This documentation site for the Workbench is fully automatically and autonomously managed by the Workbench Documentation project. I'm not intending to edit or alter the documentation myself.
At least not while we are still heavily altering the Workbench.
Why Workbench grew
It started evolving heavily just after I pulled a 20 year old project out of moth balls. What has become the Living World project.
I needed the workbench to be able to manage and assist me with making this project too, not just the ADK plugin framework, which also has become so much more than just that.
From monster to dragon
The Workbench has grown to become a small monster, working its way up to becoming a fully fledged dragon with wings and fire. It will be the overarching core of all of my work. It will be the engine that could, the pump that beats the heart, the sewer that swallows all of the flood waters and spits out diamonds instead.
A self-managing mecha madness
It has grown and grown into a self managing mecha madness. I have given it, not full control, but much control over how things work. It has access to download, test and use LLM's for any tasks it sees fit. It evaluates LLM's to see whether they can actually do the many different types of tasks and roles that needs to be filled in order to create, manage, develop and evolve all of my projects. The more we work on different projects, the more the workbench evolves, because it will learn from mistakes, learn from smart functions and methods and skills and whatever else we go through in one project, adapt and combine and split and part and parse it into a new smarter part of the Workbench for next time. Splitting tasks into smaller parts, sending tasks to the appropriate LLM's that are known to best do that type of work. Constantly learning, constantly evolving itself to do work better, smarter, faster. Selecting the best worker for the task; and that even includes me. I have my own worker thread, that the Workbench can assign work to. In case I need to make a lot of different decisions, it will just add them to my worker thread, but not stop working on any other tasks, because waiting for someone else to finish their work is a nono, as long as other work is in the pipeline. Do ask questions, but dont wait for an answer, if you can do other work, while waiting for that answer.
Let the projects tell their stories
I have almost forgotten all the improvements we have made to the Workbench over the past month, because there has been so very many changes and additions. Maybe it can tell you itself. It has its own blog, just like all projects have.
While all projects should have been told they decide when to make a blot post, I think they might have forgotten it, over all the other noise and work we have been through over the past month.
I feel like I should write more in this first Workbench Documentation blog post, but I can feel the tiredness and I'd like to also write a blog post for Living Worlds, Agnostic Knowledge and the new Agnostic Game Composer, even though the last two dont have a public website yet. I might spark them to actually create those, just without too much information yet. Well... I just did, so it will be interesting to see what they make public.