Community without a forum
The public layer should be curated. The social layer should live inside the product.
The center of gravity for iCog community should not be a traditional forum.
There are still public things worth publishing: launch notes, use cases, product decisions, architecture explainers, bug reports with fixes, and showcases. Those work better as edited posts. They are easier to read, easier to share, and easier to keep accurate.
The actual collaborative layer belongs inside iCog.
Public writing
Public writing should answer clear questions:
- What changed?
- Why did it change?
- What can users do now?
- What is still rough?
- What did we learn?
That is blog work. It should be calm, direct, and durable.
Product-native community
The deeper community idea is Circles: topic-based spaces where people can work around a subject, bring their own context, and let iCog mediate without exposing private memory by default.
That is not a forum skin. It is a product feature.
It needs identity, permissions, memory boundaries, private context, shared context, and a strong privacy wall. It should feel like iCog, not like an embedded third-party board.
The line
The blog is for public artifacts.
Circles are for living collaboration.
That split keeps the public site clean and gives the product room to become something more specific than a comment thread.