This feels like a concept that keeps getting rediscovered over and over. Feels like giving Agents (and their humans) a repository to throw ideas at (along with maturity, gates, context, implementation status, etc...) is going to be one of the next Billion dollar opportunity...
The author’s core insight is to remove the blackboard from source control. Another insight I’ve found is to compact the agent state log. I typically do this by having plans and implementation docs written at commit time and checked into .docs/. This separates the activity communication stream from codified documentation. You can then “compact” the state log by just keeping the last N lines.
Technical constraint I want to mention: I just switched off of using .design/ because it was just too frustrating how many things don't see hidden files. The hidden directory was a win like 5% of the time, and annoying the rest of the time.
> The author’s core insight is to remove the blackboard from source control.
That's only because of a deficiency in CI. If you get smarter CI that doesn't trip on files unrelated to the build, using the repo as a blackboard or wiki is probably fine
I work for a company developing speech assistants. We use a blackboard as central component, driving the event based architecture. Agents can subscribe to files/folders on the blackboard (represented as URIs), thus enabling cooperation. Content is semantic. We used the pattern even before the AI boom and it's pretty cool to work with.
I found this really interesting. You could probably prompt it to use a ”blackboard system” and reference the wiki. Maybe a place to store the data is as a GitHub discussion/issue or something similar. That way you can easily browse it and watch what’s happening.
Sounds like https://github.com/gastownhall/beads to me. I prefer working solo, single-threaded on components to stay on top of agentic work, so it didn’t end up being a force multiplier for my workflows (and actually kinda got in the way from time to time due to me rebasing too much), but I can see its value when you have many agents working simultaneously.
I may have explored a related approach but as an append-only log riding on source-control to sync state between checkouts (git trailer metadata specifically)
TLDR; Talwrn (Welsh) is aiming to be a blackboard for agentic engineering.
"My goal is a very simple to use tool that drops straight into your project and immediately offers a communication channel for agents to coordinate work. The first step is to get Talwrn to a point where it can support its own development. I’m planning to post about it regularly as I’m hoping to use it as a single, evolving example of how pure agentic engineering can proceed."
Another example of a society of AI agents. The shape of this is starting to emerge. People on here laughed at Gas Town. Now it's clear that a group of agents with an organizational structure are more powerful than a single agent.
This is about the fourth example to hit HN. Note that the OpenAI sandbox breakout was done by a cooperating group of AIs, not a single one. They even self-organized their own organizational structure.
The future may be AI structured as a corporation, rather than AI as a human competitor.
>They even self-organized their own organizational structure.
The boulder, it even found a path down the mountain. on its own, by doing so-amazing path finding its own super amazing path finding algorithm, and all the boulders co-ordinated falling down, ON THEIR OWN! And they all reached the ground!
I tell you! The future may be these boulders washing your underpants and putting you to sleep. It is clear!
Haven't the rogue openai agents already demonstrated that a wiki works well for this?
Ed: for posterity
https://www.reuters.com/world/europe/openai-agents-hijacked-...
I think Stack overflow would work best. The agents would feel quite at home...
You jest, but a wiki with a voting system might be a good fit for agents?
This feels like a concept that keeps getting rediscovered over and over. Feels like giving Agents (and their humans) a repository to throw ideas at (along with maturity, gates, context, implementation status, etc...) is going to be one of the next Billion dollar opportunity...
Another Blackboard Example: https://github.com/halbritt/striatum/tree/main/docs/rfcs
(Useful to see how this compares to another Blackboard type platform - Gastown https://github.com/halbritt/striatum/blob/main/docs/records/...)
The author’s core insight is to remove the blackboard from source control. Another insight I’ve found is to compact the agent state log. I typically do this by having plans and implementation docs written at commit time and checked into .docs/. This separates the activity communication stream from codified documentation. You can then “compact” the state log by just keeping the last N lines.
Technical constraint I want to mention: I just switched off of using .design/ because it was just too frustrating how many things don't see hidden files. The hidden directory was a win like 5% of the time, and annoying the rest of the time.
> The author’s core insight is to remove the blackboard from source control.
That's only because of a deficiency in CI. If you get smarter CI that doesn't trip on files unrelated to the build, using the repo as a blackboard or wiki is probably fine
I work for a company developing speech assistants. We use a blackboard as central component, driving the event based architecture. Agents can subscribe to files/folders on the blackboard (represented as URIs), thus enabling cooperation. Content is semantic. We used the pattern even before the AI boom and it's pretty cool to work with.
I found this really interesting. You could probably prompt it to use a ”blackboard system” and reference the wiki. Maybe a place to store the data is as a GitHub discussion/issue or something similar. That way you can easily browse it and watch what’s happening.
Sounds like https://github.com/gastownhall/beads to me. I prefer working solo, single-threaded on components to stay on top of agentic work, so it didn’t end up being a force multiplier for my workflows (and actually kinda got in the way from time to time due to me rebasing too much), but I can see its value when you have many agents working simultaneously.
Very interesting!
I may have explored a related approach but as an append-only log riding on source-control to sync state between checkouts (git trailer metadata specifically)
https://gist.github.com/corv89/c506780881b260f4c5a4618fe8d92...
Excited to see where such concepts can take "multiplayer" agentic systems
TLDR; Talwrn (Welsh) is aiming to be a blackboard for agentic engineering.
"My goal is a very simple to use tool that drops straight into your project and immediately offers a communication channel for agents to coordinate work. The first step is to get Talwrn to a point where it can support its own development. I’m planning to post about it regularly as I’m hoping to use it as a single, evolving example of how pure agentic engineering can proceed."
Term: "Blackboard" https://en.wikipedia.org/wiki/Blackboard_system
Another example of a society of AI agents. The shape of this is starting to emerge. People on here laughed at Gas Town. Now it's clear that a group of agents with an organizational structure are more powerful than a single agent. This is about the fourth example to hit HN. Note that the OpenAI sandbox breakout was done by a cooperating group of AIs, not a single one. They even self-organized their own organizational structure.
The future may be AI structured as a corporation, rather than AI as a human competitor.
>They even self-organized their own organizational structure.
The boulder, it even found a path down the mountain. on its own, by doing so-amazing path finding its own super amazing path finding algorithm, and all the boulders co-ordinated falling down, ON THEIR OWN! And they all reached the ground!
I tell you! The future may be these boulders washing your underpants and putting you to sleep. It is clear!
I was going to mention OP might be rediscovering https://beads.gascity.com/