System · the brain, it knows

Cortex

The knowledge engine.

Cortex turns approved interviews and documents into typed, cited Knowledge Cards, retrieves them with permission awareness, and refuses honestly when there is no grounded source.

Core running today

How it flows

Interviews · documents
Forge
Knowledge Cards
typed · cited · scoped
Ask
Cited answer
∅ Honest refusal
no grounded source
  • Typed Knowledge Cards: topic, criticality, audience, source, confidence.
  • Tenant isolation enforced in the database itself (Postgres row-level security).
  • Answers carry citations, or return ∅ instead of inventing one.

How it fits

Fed by Pharynx and Larynx, tuned by Thalamus, spoken through Lens, shown by Atlas.

Under the hood

Two pipelines: knowledge in, grounded answers out.

The diagram above is the shape. Here is what the code actually does: one LLM call where it earns its keep, deterministic everywhere else.

Forge · text → typed Knowledge Cards

clean
rule
chunk
rule
extract
LLM
consolidate
rule
classify
hybrid
embed
optional

Six stages. Only extract calls a model to pull structured cards; cleaning, chunking, de-duplication and classification are deterministic rules, and the embedding vector is optional.

Ask · question → grounded answer, or ∅

Question
Hybrid retrieve
dense · keyword · graph → RRF
Sufficiency gate
Cited answer
verify → refine
∅ Honest refusal
missing entity · too weak

Dense, keyword and graph search are fused (reciprocal-rank fusion), then a sufficiency gate refuses when the question names something the cards never mention. In strict mode a verify→refine loop checks that every claim is supported; otherwise it refuses rather than guess.

Tenant isolation lives in Postgres row-level security. Deny by default, no leak.
Strict answers pass a verify→refine loop; an answer the verifier rejects is never shown.
Every Knowledge Card keeps its source span, so answers can cite where they came from.
Runs fully offline on a mock provider; real models switch on with an env key.

The rest of the constellation

This is one part of a system built to keep one promise: every answer is grounded and permission-aware, or it doesn’t come at all.