Welcome to Geodesia G-1¶

Geodesia G-1 is a validating gateway that sits in front of any large language model (LLM) and provides a comprehensive quality and compliance layer. It is fully OpenAI-compatible — your existing application sends requests to Geodesia G-1 exactly as it would to OpenAI, and the gateway forwards them to your chosen underlying model (vLLM, Ollama, SGLang, OpenAI, TensorRT-LLM, and others) after enriching both the input and output with safety and reliability signals.

You do not need to retrain your model. You do not need to change your application code. You plug Geodesia G-1 in, and your LLM immediately gains:

• Hallucination detection — five independent signals that tell you whether the model's answer is grounded in the provided context or is a fabrication.
• Safety enforcement — real-time prompt screening and answer inspection to block unsafe, harmful, or jailbreak requests before they reach the model or the user.
• Regulatory compliance — a full audit trail, EU AI Act impact assessments, GDPR data retention, kill-switch, human oversight escalation, and more — across 13 global frameworks.
• Causal explainability — token-level attribution that shows exactly which words in the input caused the model's output, with no access to model internals required.

How It Works¶

flowchart LR
    A([Your Application]):::app -->|OpenAI-compatible<br/>request| B[Geodesia Gateway]

    subgraph IN [" Input validation "]
        C{Prompt safety<br/>& jailbreak}
    end
    subgraph OUT [" Output validation "]
        V{Hallucination<br/>& answer safety}
    end

    B --> C
    C -->|safe| E[Upstream LLM<br/>vLLM · Ollama · OpenAI · …]
    C -->|unsafe| D[/Block or annotate/]:::block
    E -->|answer| V
    V -->|flagged| D
    V -->|passed| F([Return to application]):::pass
    B -.->|log every call| G[(Compliance DB<br/>Audit · FRIA · Oversight)]:::db

    classDef app fill:#3f51b5,color:#fff,stroke:#283593;
    classDef block fill:#c62828,color:#fff,stroke:#8e0000;
    classDef pass fill:#2e7d32,color:#fff,stroke:#1b5e20;
    classDef db fill:#00838f,color:#fff,stroke:#005662;
    style IN fill:#3f51b510,stroke:#3f51b5,stroke-dasharray:4 3;
    style OUT fill:#00bcd410,stroke:#00bcd4,stroke-dasharray:4 3;

Every request flows through input validation → the LLM you choose → output validation, with each call written to the compliance ledger.

Every chat message goes through this pipeline:

1. Input validation — the prompt and conversation history are scored across prompt safety and jailbreak detection axes. If a threshold is exceeded in blocking mode, the request is refused before the model sees it.
2. Context injection — if you supplied a grounding context (or uploaded documents to the knowledge base), it is injected into the upstream request.
3. Generation — the upstream LLM produces a response. For streaming requests, Geodesia monitors every 32 tokens (configurable cadence) and can halt generation mid-stream if dangerous content emerges.
4. Output validation — the completed answer is scored for hallucination and unsafe content. RAG answers additionally go through claim-level citation verification.
5. Compliance logging — the call is written to the audit database, watermarked, and linked to the running hash chain.
6. Response delivery — the original OpenAI-compatible response is returned with an additional geodesia field containing the full detection payload.

Quick Navigation¶