A Kristal is designed to travel and to work under degraded conditions.
That means two things:
A Kristal can be copied, mirrored, archived, and shared as a package. It does not depend on one central server to remain meaningful.
When you receive a Kristal from somewhere else, you can verify its integrity and provenance locally before trusting it.
Offline does not mean “no functionality.” It means the core functions still work without network dependency.
To make offline use practical, a Kristal can ship with an offline runtime pack: a local bundle optimized for reading and querying.
This page stays at the “what it does” level. Technical formats belong in reference pages.
Offline systems can be dangerous if they silently drift into unverified state.
kOA uses a simple rule:
You can still view what you have, but the system should clearly mark what is verified, what is outdated, and what cannot be trusted until checks succeed.
Offline-capable doesn’t mean “never updates.” It means updates are explicit and checkable.
You always know which version you are using. “What changed?” is answerable.
Updates are not trusted by default. They are verified before becoming active.
Updates can travel via local mirrors, removable media, or “air-gapped” transfer when needed.
A team needs reliable procedures and references while connectivity is intermittent.
An organization wants durable knowledge that outlives vendors and tools.
A community distributes curated knowledge packs for education or local services.
Does offline mean “no accountability”?
No. Offline use increases the importance of clear verification status and versioning.
Can two people have different versions?
Yes, temporarily. That’s why versions and provenance must be visible, and updates must be explicit.
Is offline the default?
The system should behave well in both modes: online when available, offline when needed.
