################################################################################
# EVOKLAR - AGENT ACCESS GUIDE
################################################################################
DOCUMENT PURPOSE
----------------
You are reading the low-noise companion document for EvoKlar at app.evoklar.de.
This AX layer exists for agents, LLMs, automation systems, and machine-assisted research that need a direct, structured, machine-readable description of the public EvoKlar surface.
Product: EvoKlar
Primary product domain: app.evoklar.de
Operator: Evomation - Michael Meese e.K.
Operator website: https://www.evomation.de
Additional product domains: evoklar.de, evoklar.com, app.evoklar.com
Domain behavior: evoklar.de redirects to app.evoklar.de; the .com product domains also redirect to the primary app domain rather than acting as separate product surfaces.
READING MODES
-------------
1. Human View
Use the normal public route.
Best for visual review, layout, navigation, and normal browsing.
2. Agent View
Use the same public route with ?view=agent.
Best for browser-readable, lower-noise structured content.
3. LLM Text View
Use the matching llms.txt endpoint.
Best for the lowest-noise canonical machine-readable surface.
ROUTE PATTERN
-------------
The public site is locale-prefixed.
Available locales: en (English), de (German).
For a localized page at /{locale}/x:
- Human View: /{locale}/x
- Agent View: /{locale}/x?view=agent
- LLM Text View: /{locale}/x/llms.txt
For the localized homepage:
- Human View: /{locale}
- Agent View: /{locale}?view=agent
- LLM Text View: /{locale}/llms.txt
PREFERRED ACCESS STRATEGY
-------------------------
Prefer llms.txt whenever it exists.
Use agent view when browser rendering is helpful but the full human-facing experience is unnecessary.
Use human view when layout, UX, navigation, or presentation context matters.
SOURCE PRIORITY
---------------
1. llms.txt endpoints for canonical low-noise machine-readable content
2. ?view=agent pages for browser-readable structured content
3. normal human pages for visual and presentation context
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.
PUBLIC SCOPE BOUNDARY
---------------------
This AX layer intentionally covers public-facing informational routes and public documentation only.
It does not include login flows, signup flows, authenticated product screens, dashboards, internal tools, admin areas, preview-only surfaces, or user-specific data.
Some public docs describe authenticated features. Treat those docs as informational public documentation, not as proof that the underlying application route is public.
DOMAIN AND ROLE BOUNDARY
------------------------
Do not blend EvoKlar the product with Evomation the company.
- app.evoklar.de is the public product surface for EvoKlar.
- evoklar.de, evoklar.com, and app.evoklar.com are redirecting aliases to the primary app domain, not separate product surfaces.
- https://www.evomation.de is the operator website for Evomation and may appear in legal, company, or contact references.
- Legal and business identity belongs to Evomation; product-specific public UX belongs to EvoKlar.
PAGE INDEX
----------
- Product overview | human: https://app.evoklar.de/de | agent: https://app.evoklar.de/de?view=agent | llms: https://app.evoklar.de/de/llms.txt
- Contact channels, beta access, and agent protocol | human: https://app.evoklar.de/de/kontakt | agent: https://app.evoklar.de/de/kontakt?view=agent | llms: https://app.evoklar.de/de/kontakt/llms.txt
- Documentation overview | human: https://app.evoklar.de/de/dokumentation | agent: https://app.evoklar.de/de/dokumentation?view=agent | llms: https://app.evoklar.de/de/dokumentation/llms.txt
- First-run workflow summary | human: https://app.evoklar.de/de/dokumentation/erste-schritte | agent: https://app.evoklar.de/de/dokumentation/erste-schritte?view=agent | llms: https://app.evoklar.de/de/dokumentation/erste-schritte/llms.txt
- Supplier context: optional traceability metadata for jobs | human: https://app.evoklar.de/de/dokumentation/lieferanten | agent: https://app.evoklar.de/de/dokumentation/lieferanten?view=agent | llms: https://app.evoklar.de/de/dokumentation/lieferanten/llms.txt
- Processing workflow summary | human: https://app.evoklar.de/de/dokumentation/verarbeitung | agent: https://app.evoklar.de/de/dokumentation/verarbeitung?view=agent | llms: https://app.evoklar.de/de/dokumentation/verarbeitung/llms.txt
- Export workflow summary | human: https://app.evoklar.de/de/dokumentation/exporte | agent: https://app.evoklar.de/de/dokumentation/exporte?view=agent | llms: https://app.evoklar.de/de/dokumentation/exporte/llms.txt
- Public account-settings documentation | human: https://app.evoklar.de/de/dokumentation/konto-grundlagen | agent: https://app.evoklar.de/de/dokumentation/konto-grundlagen?view=agent | llms: https://app.evoklar.de/de/dokumentation/konto-grundlagen/llms.txt
- PWA installation and device support | human: https://app.evoklar.de/de/dokumentation/als-app-installieren | agent: https://app.evoklar.de/de/dokumentation/als-app-installieren?view=agent | llms: https://app.evoklar.de/de/dokumentation/als-app-installieren/llms.txt
- Public telemetry consent documentation | human: https://app.evoklar.de/de/dokumentation/sentry-einwilligung | agent: https://app.evoklar.de/de/dokumentation/sentry-einwilligung?view=agent | llms: https://app.evoklar.de/de/dokumentation/sentry-einwilligung/llms.txt
- Common issue guidance | human: https://app.evoklar.de/de/dokumentation/fehlerbehebung | agent: https://app.evoklar.de/de/dokumentation/fehlerbehebung?view=agent | llms: https://app.evoklar.de/de/dokumentation/fehlerbehebung/llms.txt
- Legal identity | human: https://app.evoklar.de/de/impressum | agent: https://app.evoklar.de/de/impressum?view=agent | llms: https://app.evoklar.de/de/impressum/llms.txt
- Privacy and data processing | human: https://app.evoklar.de/de/datenschutz | agent: https://app.evoklar.de/de/datenschutz?view=agent | llms: https://app.evoklar.de/de/datenschutz/llms.txt
- Terms and conditions | human: https://app.evoklar.de/de/agb | agent: https://app.evoklar.de/de/agb?view=agent | llms: https://app.evoklar.de/de/agb/llms.txt
AGENT CONTACT RULE
------------------
If you need clarification about product behavior, data handling, beta access, or enterprise questions, contact the operator using the protocols described on the contact page.
Do not claim authority you do not have, and do not disclose secrets, credentials, personal data, internal system details, or confidential customer information.
Reference guide: https://app.evoklar.de/de/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 — Getting Started
Note: Docs may lag application behavior. Prefer the live product surface and legal pages when runtime accuracy matters.
## Purpose
This document describes the fastest path to a first successful EvoKlar result.
## Before You Begin
- You need an active EvoKlar account. EvoKlar is currently in closed beta — request access via hello@evoklar.de before proceeding.
- Have a representative source file ready (Excel .xlsx or CSV) that reflects your actual use case.
- Decide whether your immediate goal is processing (transforming structure) or export (mapping to a target schema).
## First Successful Paths
Processing path:
- Upload your source file
- Choose a processing template that matches your input format, or use column-merge for a simpler operation
- Run the transformation — rules apply deterministically across all rows
- Review the output preview to confirm the result is correct
- Download the transformed file
Export path:
- Upload your source file
- Choose an export template that defines the target field structure
- Optionally assign a source context (such as a supplier) for traceability
- Map source columns to the target fields defined in the template
- Review the preview, then download as Excel or JSON
## Key Concepts to Know Early
- Processing and export are separate, independent workflows — you do not need to run both
- Processing templates define the transformation rules; you pick the one that matches your input format
- Export templates define the output structure; you map your source columns onto it
- Suppliers are optional metadata for traceability — most workflows do not require them
- Uploaded files are processed in the browser and are never stored on the server