Notes worth keeping.
We publish when there is something useful to say.
A new release.
A difficult question.
A practical guide.
A decision about privacy.
A thought about memory, family or AI that deserves more than a marketing sentence.
No daily noise.
No posts written simply because a website is supposed to have posts.
Heliarko 1.0.21: what it is — and what it is not
The edition now in closed testing.
What already works, what remains unfinished and what we want early testers to tell us.
Published 29 October 2026
Privacy & ownership
“Local” is a useful word only when its boundary is clear.
What stays inside the Capsule, what may need the internet and why Heliarko intends to keep those two things visible.
Memory & family
An image can survive for a hundred years and still lose its story.
The small pieces of context that turn a file into something another person can understand.
AI & human
AI can remember, connect, compare and pay attention.
The human still decides what matters.
Why Heliarko treats that difference as architecture, not philosophy alone.
Guides
Do not begin by organising thirty years of your digital life.
Begin with one photograph, one document or one project.
A useful archive should be allowed to grow slowly.
Doctrine
Why Heliarko starts with life, not legacy
A personal archive should be useful before it becomes important.
Notes from a project in progress.
Heliarko Journal is where we publish what changes, what we learn and the questions behind the product.
Not only release notes.
Memory.
Privacy.
AI.
Family.
Ownership.
Time.
And what it means to build digital things meant to last.
What changed?
- Release
- Heliarko 1.0.21
- Status
- Closed test
- Platform
- Windows
- Published
- 20 October 2026
The current edition.
Some questions are too important to answer once.
What should AI remember?
What should it be allowed to forget?
Who owns a digital life?
How much context is enough?
Can something remain useful when the company that made it is gone?
How do we preserve a person’s words without pretending to preserve the person?
We may return to these questions more than once.
The answers may improve.
The principles should remain visible.
We will not publish every internal discussion, unfinished experiment or ordinary day of development.
Building in public does not mean turning the work into entertainment.
Journal entries should earn their place.
They should help someone understand Heliarko, use it better, question it intelligently, or understand the ideas behind it.
If there is nothing worth publishing, the Journal can be quiet.
Silence is better than filler.
The Journal also keeps a readable history of Heliarko itself.
When a public version changes, its release record remains.
When an important product principle changes, we explain why.
When we discover that something we previously said was wrong, we correct it visibly.
A project that wants to preserve memory should keep its own memory too.
Product
Releases, product decisions and explanations.
Guides
Simple ways to use Heliarko.
Privacy & ownership
Local storage, online boundaries, security and control.
Memory & family
Context, photographs, stories, voice and long-term memory.
AI & human
Synapse, intelligence, judgment and the boundary between a person and a machine.
Doctrine
Longer writing about the principles Heliarko is built to protect.
Read slowly. Publish rarely.
The internet already has enough things competing for attention. Heliarko Journal should be a place worth returning to because something meaningful has appeared — not because we found another reason to send a notification.