You know, coworking is soon ceasing to be something bad or unnecessary.
I see how this system is being implemented for all 1500 employees, and people are starting to truly understand why it’s needed and how to use it.
It’s corporate control over token usage, tracking outgoing HTTP requests from agents, verifying skill origins, delivering models, updating workflows according to GAAP, and mandatory employee training within Cowork…
But all of this is still just in the planning stages, and I already feel nauseous at the thought of how boring the CIO conferences for those over 60 will be, where all these topics will be discussed, and most likely the participants will be drinking more than listening.
Now, each role is simply a skill within the Cowork system. It’s no different in architecture from CC, Openclaw, or Cybos, but it’s much easier to explain to accountants and operations staff.
For example, take a skill for searching corporate data:
It connects to all task trackers, messengers, email, CRM, and other software. It gathers everything by topics, responsible persons, and departments.
Everything is secure and under constant control from the CIO. Want to store something in a cloud like Gov AWS? No problem. Want access to employee information? Here you go, with a flag in hand and a couple of other markers somewhere.
It stores all source files—messages from Slack, Telegram, email. It compiles brief summaries from this data set. And it builds a graph of events around events—the so-called temporal graph for analyzing time and relationships between different activities.
Created with n8n:
https://cutt.ly/n8n
Created with syllaby:
https://cutt.ly/syllaby