Use Cases · v1.0

What Gnostikon does once you stop asking systems to remember for you.

Six patterns drawn from teams running Gnostikon in production. Each ships with the canonical contract, a real ethos, and the operational telemetry that makes it auditable.

paired runtimebackend rev 2c4a · client 8819

latest caseVoice-to-knowledge · 2026-05-08

in production43 teams · 12,400 gnoses indexed

contractOpenAPI 3.1 · 117 ops

Sort · most recent

01·Featured·Capture·Mobile

Expo · WatermelonDBWhisper-large-v3Offline-first

Voice to knowledge — meetings become validated gnoses, not transcripts.

A field engineer dictates a postmortem in the truck. The capture module transcribes locally, segments speech into provenance-bearing claims, and queues each as a draft gnosis. Sync resolves on the next reconnection; Aletheia validates against the existing codex; conflicts surface in the inbox.

Read case →

1Speech capturedoffline

2Whisper localon-device

3Segmented to gnoses12 drafts

4Aletheia validates2 conflicts

5Synced to canonicalrev 2c4a

02·Retrieval

RAG with provenance, not vibes.

Agents retrieve only gnoses that pass the pinned ethos. Every claim ships with confidence, references, and revision — and the system says "I don't know" instead of guessing when the codex hasn't validated an answer.

−74%

Hallucinations vs. baseline RAG

03·Capture · governance

Postmortems that survive the team that wrote them.

Each incident produces a small, dated cluster of gnoses. The next incident retrieves them automatically — and surfaces conflicts when last quarter's runbook contradicts this quarter's reality.

2.4×

Faster MTTR after first cycle

Research synthesis with citation chains.

Ingest 200 papers; get back a coherent codex of confidence-banded claims, every one tied to its source paragraph. Disagreements between authors surface as Aletheia conflicts.

05·Governance

Audit-grade knowledge for regulated work.

Every retrieval is an operation. Every operation has an op_id, a pinned ethos, a revision, and an immutable log. Auditors don't ask how — they read the trail.

op_2026_05_10_T7c2a

ethos · scientific_rigor

scope · project_helios

revisions · 4 touched

06·Governance

Cross-team handoff without the doc graveyard.

A project scope is the body of knowledge. New joiners switch scope and inherit the validated codex — including what is unknown, contested, or recently revised.

project_atlas→project_heliosscope switch

Stop asking your tools to remember. Start asking them to prove it.

Read the docs Browse the API