APP · 01 — THE CENTRAL NODE
Core — the reasoning and chat motor.
Core is the cognitive heart of the server. It runs the chat experience, drives the Audit Chain, and owns the SSO and design system that every other application inherits. Llama 3 served by Ollama runs in-situ on the local GPU — every prompt, retrieval and tool call is traced by Chain before it leaves the request boundary.
Modules
What ships inside Core
MOD-01
Operator Chat
Streaming chat surface with citations. Every response carries a Trace ID linking back to the prompts, resources and tools that produced it.
MOD-02
Audit Chain Motor
Tamper-evident ledger that records every reasoning step. Signed, exportable, and replayable for regulators and internal auditors.
MOD-03
SSO & Identity
OAuth 2.1 + OIDC with tenant-scoped JWTs. Sessions issued and revoked by Shield; Core never sees a raw password.
MOD-04
Design System
A single typographic and component library inherited by every cognitive application — same look, same accessibility, same telemetry hooks.
Hooks
Programmatic surface
useChatSession
useChatSession(opts: { tenantId: string }) => ChatSession- Opens a streaming chat session against the local Llama 3 runtime, wires Trace IDs into every emitted message, and exposes the active SSO claims.
useAuditTrace
useAuditTrace(traceId: string) => AuditTrace- Loads a signed Chain trace by ID — prompts, retrievals, tool calls, and the operator action that initiated them.
useDesignTokens
useDesignTokens() => Tokens- Returns the live design-system tokens (typography, colors, spacing) so satellite UIs render consistently across Core, Vault, Hub and Nexus.
useSsoClaims
useSsoClaims() => SsoClaims | null- Reads the current tenant, role and scope set from the Shield-issued JWT without forcing a network round trip.
Integration example
Drop Core into a tenant app
// Embed the Core chat surface inside a tenant app
import { CoreChat, useChatSession } from "@cognitivserver/core";
export function OperatorConsole({ tenantId }: { tenantId: string }) {
const session = useChatSession({ tenantId });
return (
<CoreChat
session={session}
runtime="ollama:llama3"
onTrace={(traceId) => console.log("Chain trace:", traceId)}
/>
);
}Language · ts
Related applications
The rest of the stack
APP · 02
Vault
Vault is the cognitive server's memory under European jurisdiction. A Vector Data Space built on Qdrant, with every asset sealed by an HMAC SHA-256 fingerprint and surfaced through a Compute-to-Data execution boundary. Skills, regulatory texts, embeddings and generated artefacts live inside the perimeter — Vault returns the answer, never the raw bytes. Aligned with GAIA-X and Pontus-X federation contracts so that what stays sovereign on the appliance can still be discovered, attested and exchanged across trusted European nodes.
Open vault
APP · 03
Hub
Hub is where the cognitive server learns the operator's landscape. A live catalog of every connected ERP, CRM, MES, WMS and TMS, with a Fleet Manager that probes each connector continuously and an Ecosystem Dashboard that surfaces the entire posture in one screen. Built for the reality of European mid-market: SAP next to Odoo, Salesforce next to a homegrown WMS — all addressable through a single sovereign perimeter so Core can reason across them and Nexus can orchestrate them.
Open hub
APP · 04
Nexus
Nexus is the MCP Host of the cognitive server. It carries the approved Skill Catalog, four granular RBAC roles — admin, director, operator, viewer — and the compliance posture surface that turns every reasoning step into evidence. Bridge transports the JSON-RPC traffic, Shield evaluates the scope, Chain seals the result, and a Firebase mirror keeps the live posture visible across the operator's regulators, auditors and lines of business. Where Vault remembers and Hub connects, Nexus decides who is allowed to do what — and proves it.
Open nexus
Engage