A Kristal is the core epistemic artifact of the kOA ecosystem.
It is designed to make structured knowledge portable, verifiable, traceable, and usable under degraded conditions — including offline.
Think of it as a compiled unit of structured meaning that can be shared, audited, queried, federated, and reused without requiring trust in a single platform, publisher, institution, or operator.
A Kristal does not claim to be “the truth.” It preserves what is claimed, what is sourced, what is validated, what remains uncertain, who recognizes it, under which scope, and which reader policy is being applied.
Kristals exist to solve a simple problem:
Most “knowledge” is stored as text, screenshots, websites, chat logs, or platform-specific records — hard to verify, hard to reuse, fragile under crisis, and easy to detach from context.
A Kristal turns knowledge into something that can be:
When a system is backed by Kristals, you get:
answers and summaries that can be traced back to sources;
a clearer separation between:
visibility into who recognizes what, under which scope;
the ability to keep operating when the network fails, using local runtime packs;
a way to compare multiple authorities without pretending disagreement has disappeared.
Kristals are meant to support learning, deliberation, research, coordination, decision, and execution while preserving a durable memory of what was known, by whom, when, why, and under which conditions.
Kristal v5 keeps these layers separate:
artifact existence
≠ artifact integrity
≠ assertion status
≠ certainty level
≠ validation status
≠ authority recognition
≠ reader visibility
≠ runtime activation
This separation matters.
A Kristal may contain uncertain, disputed, incomplete, fictional, mythological, speculative, or low-certainty assertions.
That is allowed.
What matters is that the system must not present an assertion as more certain, more validated, more recognized, more factual, or more universal than its metadata supports.
A Kristal usually follows this model:
Signal / Draft / Dataset / Submission
→ Structured Epistemic State
→ Compile
→ Working Artifact
→ Review / Validation / Attestation / Federation
→ Authority Recognition
→ Reference Artifact
→ Runtime Pack / Distribution / Reader Policy
In plain language:
The normative input unit for Kristal v5 is the Structured Epistemic State.
It can contain:
Older extractor formats such as Claim-IR may still be used internally by ingestion tools, but they are not the universal input boundary for Kristal v5.
A Kristal is typically published or used through two complementary forms.
An Exchange is the compiled artifact.
It may be:
An Exchange is the artifact you verify, cite, audit, federate, or use as the basis for runtime packaging.
It preserves structure, provenance, validation metadata, authority metadata, and lineage.
A Runtime Pack is the portable offline/query bundle.
It is optimized for local use:
A Runtime Pack should preserve the labels needed to understand assertion status, certainty, validation, authority, scope, and provenance.
In short: Exchange = verifiable compiled artifact. Runtime Pack = usable offline/query package.
Reader policies determine what a person, interface, query engine, or renderer is allowed to expose.
Common reader modes include:
reference_only;validated_only;high_certainty_only;research;creative;all_with_labels;custom.A validated_only reader policy does not mean that every visible assertion is a universal fact.
It means that every visible assertion satisfies that policy’s validation, authority, certainty, and scope filters.
For example, a reader policy may allow material validated as:
The important rule is that the label must remain clear.
Kristals are not “a platform.” They are a shared artifact layer used by platforms, tools, institutions, and communities.
Typical roles:
Kristals can be published by different authorities:
The ecosystem needs two guarantees:
This is where concepts like authority channels, domain shards, validation reports, federation manifests, and reader policies matter.
The public principle is simple:
If two sources disagree, the system should preserve the disagreement instead of hiding it.
A Kristal may contain many kinds of structured material:
The artifact must preserve the difference between these categories.
A mythological corpus can be validated as mythology. A fictional corpus can be validated as fiction. A hypothesis can be validated as a hypothesis. A disputed claim can be recorded as disputed.
None of those should be rendered as universal physical-world fact.
Kristal gives digital knowledge a stronger public structure.
It makes it possible to ask:
That is the point: not to erase disagreement, but to make knowledge portable, inspectable, and usable without losing context.
/technology/kristal/what-it-does/technology/kristal/trust-and-provenance/technology/kristal/portability-and-offline/technology/kristal/distribution-and-versioning/technology/kristal/integrations