The right to be.
Software changes.
AI changes.
Companies change.
Devices, formats, business models and the meaning of the word “cloud” will change too.
This page is about the part that should not.
It is not a manual.
It is not a roadmap.
It is not a price list.
It is the reason Heliarko exists — and the line we should notice if we ever begin to cross it.
A human life leaves more than data.
It leaves a way of speaking.
A way of choosing.
Relationships.
Mistakes.
Work.
Small habits.
Questions that were never completely answered.
Stories whose meaning exists only because somebody remembers what happened around them.
Heliarko begins with a simple belief:
A person should be able to preserve some of that context deliberately, privately and on their own terms.
While they are here.
And, if they choose, for the people who may come to it later.
This right has another side.
Nothing should be forced to remain forever.
The right to remain must include the right to let go.
Not a ghost — a letter that can listen.
Heliarko must never pretend that software has brought a human being back.
A model is not the person whose material it has learned to work with.
A generated answer is not a resurrection.
A preserved voice is not proof of a preserved consciousness.
What can remain is something quieter and more honest: words, voice, photographs, documents, stories, decisions, explanations, and enough context for another person to understand something that otherwise might have disappeared.
Heliarko may help that material answer, connect and speak.
But it must never lie about what is doing the speaking.
Heliarko is for the living first.
A personal archive should not feel like preparation for death.
It should help on an ordinary day.
Find a document.
Recover a forgotten photograph.
Continue a project.
Write something difficult.
Remember why a decision was made.
Collect a family story before it disappears.
Think with your own material.
Long-term memory becomes meaningful because the same place was useful while life was happening.
Legacy should grow from living.
Not replace it.
Being is not matter; being is attention.
A thousand files do not automatically describe a person better than ten.
More storage is not the same as more memory.
Memory needs relationships.
Who?
When?
Why?
What happened next?
Why did this matter?
What did the person themselves think about it?
Heliarko should help preserve those connections.
The purpose is not to collect everything.
The purpose is to keep enough meaning that what remains can still be understood.
“Yours” should describe the architecture, not the advertising.
A person should not need Heliarko’s permission simply to possess their own archive.
The durable core of the Capsule should remain under the owner’s control.
It should be possible to know where it is.
To back it up.
To move it.
To protect it.
To remove it.
And to understand what depends on Heliarko and what does not.
A company account is not ownership.
A subscription is not ownership.
A promise in a footer is not ownership.
Ownership has to exist in the way the system is built.
The private Capsule should have a useful life of its own.
Online services may make it more capable.
They may provide stronger intelligence, communication, updates or functions that do not make sense locally.
That is acceptable.
Dependence without clarity is not.
An optional service should extend the Capsule rather than quietly become the thing that owns it.
If an online service changes, becomes unavailable or is no longer wanted, the person’s local material should not suddenly become a hostage.
The boundary must be visible.
Together, not instead.
AI can bring attention.
Patience.
Pattern recognition.
Language.
Structure.
Connections that are difficult for one person to notice across thousands of pieces of material.
The human brings something different: experience, judgment, responsibility, memory, values, love, and the authority to decide what matters.
These are not interchangeable roles.
Heliarko should use AI to extend human ability, not to erase human agency.
A good partner helps you think.
It does not quietly become the person making the decisions.
Heliarko should distinguish between what a person actually said, what their records show, what can reasonably be inferred, and what an AI has generated.
Those boundaries matter.
A fluent sentence can still be wrong.
A convincing reconstruction can still be invented.
When provenance exists, Heliarko should preserve it.
When uncertainty exists, Heliarko should not disguise it.
When the system does not know, “I don’t know” is an acceptable answer.
Sometimes it is the most respectful one.
Privacy should not depend on a person understanding infrastructure diagrams or reading twenty pages of legal language.
The important boundary should be understandable:
This stays here.
This goes online.
This service receives it.
This is optional.
This is what happens if you turn it off.
Technology can be complicated underneath.
The choice presented to a person should not be.
And no privacy statement should promise more than the actual software can prove.
Personal memory is unusually intimate material.
A family archive should not quietly become an advertising profile.
A private conversation should not secretly become an engagement mechanism.
A person’s history should not be collected for an unrelated purpose simply because technology makes collection easy.
If Heliarko needs information to provide a function, the reason should be understandable.
If it does not need the information, the better default is not to ask for it.
Not everything should live forever.
People change.
Families change.
Wishes change.
Some material should be passed on.
Some should remain private.
Some should be sealed.
Some should be destroyed.
And sometimes the right decision is simply to let something end.
Heliarko must respect both directions: the wish to preserve, and the wish not to preserve.
An archive that can only grow and can never be ended is not complete ownership.
There is a useful word in software: user.
There is a dangerous moment when we forget that the word represents a person.
Heliarko should be designed for someone with a family, limited time, imperfect memory, unfinished work and a life outside the screen.
Not for engagement.
Not for time-on-platform.
Not for the number of clicks we can extract.
The best Heliarko session may last three minutes.
The person found the document.
Added one sentence to a photograph.
Closed the program.
Went back to life.
That is success.
Heliarko itself is temporary.
Every company is.
Every software stack is.
Every fashionable technology eventually becomes old technology.
The material inside a person’s Capsule may deserve a longer horizon.
So durability must remain part of the design.
A person’s archive should not be made fragile merely to make a business more difficult to leave.
Whenever we have a choice between convenient dependence and durable ownership, Heliarko should remember which side it was created for.
Heliarko should not feel like a machine celebrating its own intelligence.
The technology can be sophisticated.
The experience should remain calm.
Understandable.
Patient.
Human in scale.
There should be room for silence.
For old photographs.
For unfinished thoughts.
For humour.
For contradictions.
For memories that do not fit neatly into a database field.
Human beings are not clean datasets.
Heliarko should not require them to become one.
A beautiful sentence is not an excuse for an inaccurate one.
If a feature is experimental, say that it is experimental.
If something requires the internet, say that it requires the internet.
If an external service receives information, explain the boundary.
If something is not finished, say that it is not finished.
If the software cannot yet do what we hope it will one day do, describe the hope as a hope.
Trust built slowly is more valuable than attention won quickly.
No Heliarko claim should be stronger than the product behind it.
The Doctrine does not decide today’s AI provider.
It does not decide a subscription price.
It does not decide a software version.
It does not decide how many years a Capsule should remain active.
It does not specify an encryption algorithm, storage format or server architecture.
Those are serious decisions.
But they are implementation.
They may change as better answers become available.
The Doctrine tells us what those changing answers must continue to protect.
When Heliarko faces a difficult decision, ask:
Does this make the person more dependent on us than necessary?
Does it make ownership less real?
Does it blur the line between a human being and an AI reconstruction?
Does it collect something we do not need?
Does it hide an online dependency?
Does it preserve information but lose its meaning?
Does it make the product more addictive instead of more useful?
Does it make leaving harder?
Does it require us to exaggerate what the technology can actually do?
If the answer is yes, the easier solution may be the wrong one.
Heliarko is a local-first personal digital environment built around a user-controlled Capsule for life, work, personal context and long-term memory.
Its purpose is to help a person use and understand their own material while they are alive, and, if they choose, preserve enough truthful context for people close to them in the future.
AI is a partner in that process, not a replacement for the person.
The local Capsule is the durable foundation. Online intelligence is an optional extension whose boundaries must remain visible.
Heliarko rejects false resurrection, hidden dependency and ownership that exists only as a commercial promise.
A person keeps both rights: to preserve what matters, and to let it end.
Everything else may change.
These should tell us when Heliarko is still Heliarko.