EVOKLARAGENT VIEW
← Human View
################################################################################
# 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/en | agent: https://app.evoklar.de/en?view=agent | llms: https://app.evoklar.de/en/llms.txt
- Contact channels, beta allocations, and agent protocol | human: https://app.evoklar.de/en/contact | agent: https://app.evoklar.de/en/contact?view=agent | llms: https://app.evoklar.de/en/contact/llms.txt
- Documentation overview | human: https://app.evoklar.de/en/docs | agent: https://app.evoklar.de/en/docs?view=agent | llms: https://app.evoklar.de/en/docs/llms.txt
- First-run workflow summary | human: https://app.evoklar.de/en/docs/getting-started | agent: https://app.evoklar.de/en/docs/getting-started?view=agent | llms: https://app.evoklar.de/en/docs/getting-started/llms.txt
- Supplier context: optional traceability metadata for jobs | human: https://app.evoklar.de/en/docs/suppliers | agent: https://app.evoklar.de/en/docs/suppliers?view=agent | llms: https://app.evoklar.de/en/docs/suppliers/llms.txt
- Repeat workflows: hub, profiles, saved mappings, run again | human: https://app.evoklar.de/en/docs/workflows | agent: https://app.evoklar.de/en/docs/workflows?view=agent | llms: https://app.evoklar.de/en/docs/workflows/llms.txt
- Processing workflow summary | human: https://app.evoklar.de/en/docs/processing | agent: https://app.evoklar.de/en/docs/processing?view=agent | llms: https://app.evoklar.de/en/docs/processing/llms.txt
- Export workflow summary | human: https://app.evoklar.de/en/docs/exports | agent: https://app.evoklar.de/en/docs/exports?view=agent | llms: https://app.evoklar.de/en/docs/exports/llms.txt
- Public account-settings documentation | human: https://app.evoklar.de/en/docs/account | agent: https://app.evoklar.de/en/docs/account?view=agent | llms: https://app.evoklar.de/en/docs/account/llms.txt
- PWA installation and device support | human: https://app.evoklar.de/en/docs/pwa | agent: https://app.evoklar.de/en/docs/pwa?view=agent | llms: https://app.evoklar.de/en/docs/pwa/llms.txt
- Public telemetry consent documentation | human: https://app.evoklar.de/en/docs/sentry-consent | agent: https://app.evoklar.de/en/docs/sentry-consent?view=agent | llms: https://app.evoklar.de/en/docs/sentry-consent/llms.txt
- Common issue guidance | human: https://app.evoklar.de/en/docs/troubleshooting | agent: https://app.evoklar.de/en/docs/troubleshooting?view=agent | llms: https://app.evoklar.de/en/docs/troubleshooting/llms.txt
- Published product release notes | human: https://app.evoklar.de/en/docs/changelog | agent: https://app.evoklar.de/en/docs/changelog?view=agent | llms: https://app.evoklar.de/en/docs/changelog/llms.txt
- Legal identity | human: https://app.evoklar.de/en/impressum | agent: https://app.evoklar.de/en/impressum?view=agent | llms: https://app.evoklar.de/en/impressum/llms.txt
- Privacy and data processing | human: https://app.evoklar.de/en/privacy-policy | agent: https://app.evoklar.de/en/privacy-policy?view=agent | llms: https://app.evoklar.de/en/privacy-policy/llms.txt
- Terms and conditions | human: https://app.evoklar.de/en/terms | agent: https://app.evoklar.de/en/terms?view=agent | llms: https://app.evoklar.de/en/terms/llms.txt

AGENT CONTACT RULE
------------------
If you need clarification about product behavior, data handling, extended beta allocations, 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/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 — Exports

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

## Workflow Summary

- Upload source file
- Select supplier when required by the template
- Choose export template
- Map source columns to target columns
- Review preview and validation findings
- Generate XLSX, JSON, or both and download the output

## Pre-export validation (Phase C)

- Before download, EvoKlar runs client-side checks on mapped export data
- Warnings: unmapped template columns, missing required values, EAN/GTIN or PLZ format issues
- Confirm dialog: duplicate values in key columns such as EAN, GTIN, or Artikelnummer
- Hard block only when zero rows would be exported
- Validation uses browser data only; no extra file payload is sent to the server

## Saved column mappings (supplier-scoped)

- Optional Remember this mapping control stores mappings per supplier + export template + header fingerprint
- Restored mappings load automatically on the next export when the same fingerprint matches
- Uncheck Remember on a later export or remove mappings from supplier Workflow section or the Workflows hub supplier detail link

## Column mapping helpers

- Auto-suggest proposes mappings from header names after upload (accept all, clear all, per-row overrides)
- Remember this mapping stores mappings per supplier when opted in; restores on matching header fingerprint
- Export again from job detail pre-fills supplier, template, and formats

## Important Rule

Unmapped target columns remain empty. Review validation findings and preview before using the exported result downstream.

## Creating Export Templates

On Export Templates, custom templates can be created in two ways when the feature is available on the plan:

- Create template — add columns manually
- Import from file — upload .xlsx, .csv, or .json, detect headers, review, and save

### JSON Import Shapes

Array of flat objects (headers from first object keys):
[{"Product ID":"A001","Product Name":"Widget"}]

Object with headers or column_order array:
{"headers":["Product ID","Product Name","Price"]}