King Klown Logo
The kOAinitiative

Kristal — What it does

Kristal is a portable epistemic artifact system: a way to package structured knowledge, provenance, certainty, authority, and reader-policy metadata into reusable artifacts.

Its job is simple:

Make knowledge transferable, checkable, auditable, and usable under real-world constraints without pretending that all knowledge has the same certainty, authority, or scope.


At a glance

A Kristal helps you:


What you get, in human terms

1) A portable knowledge artifact

Not a blog post. Not a spreadsheet. Not a single document.

A Kristal is closer to a portable library of structured knowledge, with clear boundaries:

A Kristal can contain imperfect or uncertain material.

What matters is that the artifact does not hide that uncertainty.


2) A reusable foundation for civic and operational workflows

Kristals enable systems where decisions can be traced back to stable knowledge.

That means people can contest outcomes without restarting every debate from zero.

A decision can reference:

This makes disagreement easier to locate, inspect, and resolve.


3) An offline-capable runtime surface

In kOA, many important contexts are degraded:

Kristals are designed so useful access can survive connectivity loss.

A Runtime Pack can make selected Kristal content available locally while preserving the labels needed to understand status, certainty, authority, scope, and provenance.


What Kristals preserve

Kristals are built to preserve distinctions that ordinary documents often collapse.

A Kristal separates:

This is the core of Kristal v5.

A Kristal may be signed, content-addressed, queryable, and portable while still containing assertions that are hypothetical, disputed, fictional, mythological, low-certainty, rejected by one authority channel, recognized by another, or hidden by a reader policy.


Where Kristals appear in kOA

Kristals are a shared substrate beneath multiple layers.

Konnaxion

Konnaxion can use Kristals for:

Konnaxion is where Kristals can be distributed, activated, cached, queried, and rendered for people.

Orgo

Orgo can use Kristals for:

Orgo does not need to treat every claim as final. It can work with structured states, review material, validation reports, and reference artifacts.

SenTient

SenTient can help create or refine Kristal inputs by:

SenTient does not need to force every input into a single “accepted truth” before compilation.

Architect

Architect can render Kristal content into readable outputs.

Its job is not to invent facts.

Its job is to render from selected Kristal material under a reader policy while preserving traceability, certainty, validation, authority, and scope.

Ariane

Ariane can use Kristals for structured navigation and interpretation that depends on stable meaning, provenance, and reader-policy-aware context.

Voting and decision workflows

Voting or decision workflows can reference Kristals so outcomes remain auditable over time.

A vote, consultation, policy decision, or public commitment can point to:


Core guarantees, non-technical

Kristal is meant to support these guarantees.

Portability

A Kristal can move between machines, institutions, communities, and environments.

Integrity

You can verify that what you received is what was published.

Provenance

You can see what the artifact is based on and where its assertions came from.

Traceability

Rendered text, query results, and decisions can point back to source assertions, evidence, and artifacts.

Certainty awareness

Assertions do not all need to have the same confidence level.

A Kristal can preserve hypotheses, early research, disputed positions, established facts, fictional corpora, mythological corpora, symbolic models, and publisher declarations without flattening them into one status.

Authority awareness

Validation is scoped.

A claim can be recognized by one authority channel and rejected by another.

Kristal preserves that difference.

Contestability

People can challenge inputs, interpretations, authority decisions, reader policies, and updates.

Offline usefulness

Core access can work without always-on infrastructure.

Compatibility

Older Kristals and Runtime Packs can remain usable when the ecosystem evolves, provided their schemas, policies, and runtime constraints are understood.


Common use cases

Knowledge preservation

A community publishes a Kristal capturing its history, institutions, vocabulary, decisions, and cultural memory so it cannot be quietly erased, rewritten, or fragmented.

The Kristal can preserve both high-confidence records and contested interpretations, as long as their status is explicit.

Civic dossiers and policy packets

A municipality shares a Kristal that bundles a project’s facts, constraints, public comments, legal references, budget assumptions, and disputed positions.

Debates can then happen on a shared artifact without pretending everyone agrees.

Education and competence

A Kristal packages a curriculum:

Schools or communities can reuse it while preserving provenance and scope.

Operational memory

An organization uses Kristals to preserve the “what we knew then” context behind major decisions.

Later reviews can inspect:

Research and review

Researchers can publish a working Kristal with hypotheses, early evidence, uncertainty, and disputed claims.

Later, domain authorities can validate, reject, recognize, or supersede parts of it without destroying the original lineage.

Cultural, mythological, and fictional corpora

A cultural archive can publish a Kristal describing a mythological system as mythology.

A fiction publisher can publish a Kristal describing a fictional world as fiction.

Those artifacts can be valid and useful without being presented as physical-world facts.


What Kristals are not

Kristal is infrastructure for structured, portable, inspectable knowledge.

It helps people, institutions, communities, and systems share knowledge without losing provenance, certainty, authority, scope, or disagreement.


Next pages