In Part 1, we established the need for rigorous editing, curating, and culling in the face of content chaos. This quest for clarity is the foundation for my solution.
The Anti-Dote: Introducing the Creative Engine OS
With more options to access and create come potential multiplications of streams of content that shouldn’t have been put out there. And yes, of course, I am talking about all the AI tools…
Here is my thought: why not embrace the tools we have available and utilize them, not to create more of the same, but rather to sharpen our focus on the ‘decisive moment’ I described a little earlier? We need tools for computational efficiency and intelligent culling.
My recent Creative_Engine Operating System (CEOS) is a set of tools to help in creating the piece out of the chaos. I designed CEOS to be a new type of creative foundation: an application production platform, a functional game engine, and an extremely efficient creative workflow utility.
I’m using my experiences to think about designing flexible but guiding workflows. While at the same time, having ethics at the front of my conscience. For this reason, I opt only for self-hosted, open-source tools in a transparent and repeatable, non-destructive method to cut through the noise and to cull the unneeded. The entire CEOS ‘OS’ has an estimated footprint of just ~3,300 – 4,900 lines of code (all non-AI), built on a philosophy of extreme efficiency.
I had built (and tested) the systems in a modular way. Individual components can be connected as nodes or work as stand-alone units, providing a flexible and adjustable workflow. Even when integrating existing platforms (like n8n), the workflows I designed still retain their power (and often even gain functionality).
I’m not done, and I am not sure if I will ever be done, as tools develop quicker than I can keep up with. I often have wondered if I should open up the intention I had earlier and allow for the system to become truly open-source (and community-driven), like many of the tools I use and come to love (Blender, Godot, n8n, DaVinci Resolve, and Affinity (from v1), recently ‘rebooted’ by Canva).
I’m now finding myself in the position that I realize I need to start putting the things I build out in the daylight… but there are some (minor and mostly visual) tweaks I feel still need some work. And that’s why I want to reach out to anyone who feels affinity with my quest of creating an anti-dote to the constant stream-of-too-many-options.
Here is how you can help:
Visual Refinement (UI/UX): Offer feedback on the interface designs to ensure they match the system’s efficiency and vision. This requires consultation to build a user-friendly layer on top of the existing infrastructure.
Beta Testing: Volunteer to test the CEOS core components, helping to ensure the self-auditing architecture is robust.
Code Review/Collaboration: If you have expertise in Python or open-source community building, connect to discuss opening the CEOS architecture and contributing to projects like Project PB_J (the seamless translation layer to external apps like Blender/Godot).
Strategic Funding: If you are a visionary investor who sees the value in an ethical, efficient, and truly open-source creative paradigm, I invite you to discuss the blueprint and the CEOS’ intended impact on creative communities. (More info on meaningful ways to contribute to this projects can be found here).