What this blog is for
A public log for product decisions, build notes, and the parts of iCog that should be explained plainly.
This blog is for the things that should be public, but do not need the weight of a research essay.
Research stays for deeper arguments: memory architecture, model continuity, personal AI, benchmarks, market analysis. The blog is more direct. It is where we write down product calls, release notes, rough edges we are fixing, small build logs, and the reasoning behind changes users will feel.
That matters because iCog is not just a chatbot interface. It is a continuity layer: memory, identity, context, and cognition that should survive the model underneath it. A lot of the work is invisible unless we explain it.
What belongs here
- product notes
- release notes
- short build logs
- migration notes
- known issues and fixes
- user-facing explanations of design decisions
- curated showcases when people build with iCog
What does not belong here
This is not a support queue. It is not a generic comment board. It is not a place where every passing thought needs a permanent URL.
The public surface should stay readable. The social product should stay native to iCog.
Why this shape
A traditional forum is good when the main thing you need is volume: many threads, many replies, many moderation tools.
That is not the immediate need here.
The immediate need is a clean public voice that compounds: posts people can read, cite, search, and send to someone else without needing to understand the whole product first.
So this blog is the working public log.