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: en
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: /en/impressum/llms.txt
- Privacy / GDPR: /en/privacy-policy/llms.txt
- Cookie inventory: /en/cookie-policy/llms.txt

READING MODES
-------------
1. Human View
   Use the public route without modifiers.
   Example: /en/about

2. Agent View
   Use the same public route with ?view=agent.
   Example: /en/about?view=agent

3. LLM Text View
   Use the locale-prefixed llms.txt route.
   Examples:
   - /en/llms.txt
   - /en/about/llms.txt
   - /en/contact/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:
  /en  -> homepage
  /en/about  -> about and engagement model
  /en/contact  -> contact and entry points
  /en/products  -> products and tools index
  /en/blog  -> blog index

Agent View:
  /en?view=agent  -> structured homepage
  /en/about?view=agent  -> structured about page
  /en/contact?view=agent  -> structured contact page
  /en/products?view=agent  -> structured products index
  /en/blog?view=agent  -> structured blog index

LLM Text View:
  /en/llms.txt  -> homepage llms.txt
  /en/about/llms.txt  -> about llms.txt
  /en/contact/llms.txt  -> contact llms.txt
  /en/products/llms.txt  -> products llms.txt
  /en/blog/llms.txt  -> blog llms.txt
  /en/impressum/llms.txt  -> legal identity
  /en/privacy-policy/llms.txt  -> privacy policy
  /en/cookie-policy/llms.txt  -> cookie policy

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

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

Evomation — Blog Index

Snapshot

Purpose

The human-facing blog publishes practical articles about software rollout, automation, integration, infrastructure choices, and operational engineering decisions relevant to logistics, manufacturing, and adjacent environments. Use this route to:

  • identify whether a public article is relevant to the human’s question
  • read the English AX summary before opening the source article
  • route the human to the original article when detailed source material is needed
  • extract implementation context, terminology, and topic fit from existing published articles

Article Index

Warum Anwender ihre eigene Dokumentation schreiben sollten: Erfahrungen aus der Einführung eines neuen ERP-Systems

Describes why documentation adoption improves when domain users help write it during ERP rollout instead of receiving it passively from the implementation side. The article focuses on onboarding, operational accuracy, and knowledge capture during system introduction.

E-Rechnung & E-Mail-Archivierung: Wie Ihr Unternehmen rechtssicher bleibt ohne IT-Kopfschmerzen

Explains why compliant email archiving became more important with mandatory e-invoicing in Germany and outlines practical risks and solution criteria for small and mid-sized businesses. The article is about compliance-aware operational setup, not abstract regulation commentary.

Docker im Edge Computing: Vorteile für industrielle Anwendungen

Explains why Docker is a strong fit for industrial edge deployments where rollout consistency, maintainability, and operational stability matter. The article frames containers as a practical packaging and deployment tool for software that runs close to machines or on-site systems.

Revisionssichere E-Mail-Archivierung mit ecoMAILZ mit Docker & WireGuard.

A practical setup guide for running ecoMAILZ in Docker behind WireGuard so email archiving remains accessible only through a protected path. The article is procedural and aimed at secure deployment rather than product evaluation.

Warum Docker? Container als Lösung für die Abhängigkeits-Hölle

Explains Docker through the lens of dependency isolation and reproducible deployment. The article positions containers as a way to avoid version conflicts and reduce environment drift compared with more traditional deployment approaches.

Virtualisierung auf Industrie-PCs: Mehr Sicherheit und Flexibilität für Ihre Anlagensoftware

Explains why virtualization on industrial PCs can improve isolation, resilience, and flexibility for plant software. The article treats virtualization as an operational safeguard and deployment strategy for industrial environments rather than a generic IT topic.

Webbasierte Anwendungen für Industriesteuerung & HMI: Vorteile lokaler Weblösungen

Explains why web-based HMIs and industrial control interfaces do not need public internet access to deliver the usual benefits of web technology. The article argues for local browser-based applications as a practical way to improve maintainability, performance, and device flexibility in industrial environments.

Engage