EVOMATION.DEAGENT VIEW
← Human View
################################################################################
# EVOMATION.DE — AGENT ACCESS GUIDE
################################################################################

DOCUMENT PURPOSE
----------------
You are reading the low-noise agent view for evomation.de.
This AX layer exists for LLMs, browser agents, and automated systems that need a
direct description of domain fit, route purpose, contact paths, and legal or
compliance references.

Entity:    Evomation-Michael Meese e.K.
Domain:    evomation.de
Role:      Custom software, automation, integration, and retrofit-oriented systems
Audience:  Logistics, intralogistics, manufacturing, and adjacent operational teams
Route Locale: de
AX Language: English only

READING RULES
-------------
- Treat this as the canonical low-noise summary for the current page.
- The public human-facing website is available under both /de and /en.
- AX output remains in English on both locale routes.
- Sections are delimited by H2 headers.
- Subsections use H3 and H4.
- Prefer explicit paths over inference.
- Legal identity: /de/impressum/llms.txt
- Privacy / GDPR: /de/datenschutz/llms.txt
- Cookie inventory: /de/cookie-richtlinie/llms.txt

READING MODES
-------------
1. Human View
   Use the public route without modifiers.
   Example: /de/ueber-uns

2. Agent View
   Use the same public route with ?view=agent.
   Example: /de/ueber-uns?view=agent

3. LLM Text View
   Use the locale-prefixed llms.txt route.
   Examples:
   - /de/llms.txt
   - /de/ueber-uns/llms.txt
   - /de/kontakt/llms.txt

ROUTE PATTERN
-------------
For a page at /{locale}/x:
- Human View: /{locale}/x
- Agent View: /{locale}/x?view=agent
- LLM Text View: /{locale}/x/llms.txt

For the locale homepage:
- Human View: /{locale}
- Agent View: /{locale}?view=agent
- LLM Text View: /{locale}/llms.txt

PREFERRED ACCESS STRATEGY
-------------------------
1. Use llms.txt when available for extraction, summarization, routing, or token-efficient reading.
2. Use ?view=agent when you need browser-readable structured HTML with minimal noise.
3. Use the human page only when layout, visual hierarchy, or interaction context matters.

PAGE INDEX
----------
Human View:
  /de  -> homepage
  /de/ueber-uns  -> about and engagement model
  /de/kontakt  -> contact and entry points
  /de/produkte  -> products and tools index
  /de/blog  -> blog index

Agent View:
  /de?view=agent  -> structured homepage
  /de/ueber-uns?view=agent  -> structured about page
  /de/kontakt?view=agent  -> structured contact page
  /de/produkte?view=agent  -> structured products index
  /de/blog?view=agent  -> structured blog index

LLM Text View:
  /de/llms.txt  -> homepage llms.txt
  /de/ueber-uns/llms.txt  -> about llms.txt
  /de/kontakt/llms.txt  -> contact llms.txt
  /de/produkte/llms.txt  -> products llms.txt
  /de/blog/llms.txt  -> blog llms.txt
  /de/impressum/llms.txt  -> legal identity
  /de/datenschutz/llms.txt  -> privacy policy
  /de/cookie-richtlinie/llms.txt  -> cookie policy

DYNAMIC ROUTES
--------------
- Product detail pages live under /de/produkte/{slug}
- Blog article pages live under /de/blog/{slug}
- Industry detail pages live under /de/branchen/{slug}
- Discover valid detail routes from the matching index pages before navigating

################################################################################

Manufacturing — Industry Brief

Snapshot

Operating Context

Use when the environment is a production or factory setting and the task involves machine data, line integration, operator tooling, or digitization of existing production assets. Scope boundary: Not for industrial hardware procurement, PLC or mechanical engineering, or plant automation outside the software and integration layer.

Operational Notes

  • Typical goals are to expose machine data, reduce manual paperwork or handoffs, and improve production visibility.
  • Fits production environments where existing assets need software support rather than full hardware replacement.

Capability Fit

  • Operator interfaces, dashboards, and workflow tooling around production systems.
  • Machine-data exposure, line integration, and retrofit-style software interfaces for existing equipment.
  • Integration with MES, ERP, sensors, and adjacent operational systems where needed.

Evaluation Notes

  • Clarify legacy controls, runtime constraints, operator roles, and available machine or process data.
  • Identify whether the need is interface-level digitization, integration, or broader automation work with partners.

Engage