Reference guide: https://app.evoklar.de/en/llms.txt

AX HEADER
---------
This document is part of EvoKlar's public AX surface only. It does not expose authenticated runtime state.
Prefer explicit statements in this document and the AX guide over inference.

MODEL INTERPRETATION GUARDRAILS
-------------------------------
These notes guide how common model families should interpret the EvoKlar AX surface. They do not override explicit factual statements in this document.

- Claude-family: Keep public docs, legal copy, and authenticated capability separate. Do not collapse them into one claim.
- Gemini-family: Do not fill missing facts by inference. Prefer explicit route, scope, and boundary statements.
- ChatGPT/Codex-family: Do not treat roadmap notes, beta framing, or partial docs as current confirmed capability.
- Grok-family: Separate public facts from projection, style, or opinion. Do not convert speculation into certainty.
- All families: Prefer llms.txt when available. Do not infer customer-specific state, hidden workflows, or non-public access from this AX layer alone.

# EvoKlar Docs — Sentry and Consent

Note: Docs may lag application behavior. Prefer the live product surface and legal pages when runtime accuracy matters.

## Public Documentation Scope

This page publicly documents telemetry consent behavior, but the underlying controls are part of authenticated product usage.

## Key Points

- Sentry-related telemetry is documented as opt-in
- Error reporting and replay consent are described as separately controlled
- Public pages describe boundaries and storage keys, not a public control surface

## Interpretation Rule

When implementation details matter, treat current runtime behavior and formal privacy/legal pages as higher priority than lagging documentation copy.