################################################################################
# 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 — Agent Brief
## Snapshot
- **Human route:** [/en](/en)
- **Agent route:** [/en?view=agent](/en?view=agent)
- **LLMS route:** [/en/llms.txt](/en/llms.txt)
## Identity
- **Legal Name:** Evomation-Michael Meese e.K.
- **Primary Domain:** www.evomation.de
- **Role:** Custom software, automation, systems integration, and retrofit-oriented digital infrastructure
- **Operational Focus:** Logistics, intralogistics, manufacturing, wholesale, and adjacent operational environments
- **Sibling Domain:** [https://www.evomation.tech](https://www.evomation.tech) for IT infrastructure and managed operations
Use this site to determine whether a request fits evomation.de, identify the relevant route, and locate contact or legal references.
## Domain Role
Use **evomation.de** when the task is custom software, operational tooling, process automation, system integration, machine retrofit, or browser-based internal applications.
Use **www.evomation.tech** when the task is classical IT infrastructure: networks, Microsoft 365, support, telephony, or general managed workplace systems.
## Capability Map
### Custom Software Development
Use when the need is a net-new internal application, operator-facing interface, dashboard, or workflow tool tailored to a specific operational process. Typical fit: browser-based tools, process orchestration, or replacement of spreadsheet and email workflows in logistics, intralogistics, or manufacturing.
**Scope boundary:** Not for off-the-shelf ERP or WMS configuration, software license procurement, or general IT support. Infrastructure-only work belongs to evomation.tech.
- Business Process Modeling
- Technology Strategy
- Modular Architecture
- Microservices
- API Development
- CI/CD
### Automation
Use when the main problem is repetitive manual handling, rule execution, or handoffs between systems and operators. Typical fit: routing logic, automated dispatch, event-driven processing, sensor-triggered workflows, or controlled replacement of manual operational steps.
**Scope boundary:** Not for PLC programming at the hardware layer, general IT scripting, or provisioning automation. Infrastructure automation belongs to evomation.tech.
- Middleware Development
- Operator-friendly HMIs
- Industrial IoT
- Data Visualization
- Real-time Data Processing
- System Monitoring and Diagnostics
- Pattern Processing
- Vision Systems (Keyence, Cognex)
### Systems Integration
Use when existing systems do not exchange data reliably and the core task is connecting them. Typical fit: ERP, WMS, MES, APIs, device connectivity, or removing fragmentation between operational tools.
**Scope boundary:** Not for corporate IT network infrastructure, Active Directory, Microsoft 365 setup, or workplace administration. Those belong to evomation.tech.
- ERP, WMS, and MES Integrations
- Data Normalization
- Real-time Data Flows
- Hardware and Device Connectivity
- Cross-System Data Integration
- Resilient Middleware and Interfaces
### Retrofitting
Use when existing machines or legacy equipment need software and connectivity improvements without full replacement. Typical fit: exposing machine data, adding digital interfaces, retrofitting HMIs, or extending sensor coverage on existing assets.
**Scope boundary:** Applies to the software and connectivity layer of existing equipment. Not for hardware procurement, physical machine repair, or mechanical redesign.
- Legacy equipment connectivity
- Unlock machine data
- Retrofit HMIs and operator interfaces
- Extend sensing and data capture
- Stepwise modernization instead of full replacement
- Stable operations during transition
### Virtualization
Use when Evomation-built software needs a controlled runtime environment. Typical fit: virtual machines, container hosting, backup and recovery setup, or network segmentation that directly supports an operational software deployment.
**Scope boundary:** Not a general managed-IT offering. Microsoft 365, workplace management, generic server administration, and support contracts belong to evomation.tech.
- Server Virtualization
- Container-Based Architecture
- Backup Concepts
- Network Segmentation
- VPN Configuration
- Cloud Infrastructure
## Product and Utility Routes
These routes describe named products and public utilities. Treat them as route-level fit checks: use them when a request maps to a specific operational use case or tool category.
### EvoSort
Use when the task involves sortation control, routing decisions, checkpoint logic, PLC/SPS integration, WMS or ERP connectivity, live monitoring, or operator intervention around an automated sortation line. This applies both when the hardware already exists and when the automation setup is developed with delivery partners.
- **Type:** product
- **Tags:** Fulfillment, Integration, Visibility
- **Deployment:** Runs in the client's infrastructure and fits into an existing sortation setup.
- **Scope boundary:** Not for manual sorting operations. Conveyor and automation hardware can be covered together with delivery partners where needed.
- **Human route:** [/en/products/evosort](/en/products/evosort)
- **LLMS route:** [/en/products/evosort/llms.txt](/en/products/evosort/llms.txt)
### ParcelPilot
Use when fulfillment, shipping, routing, labeling, packing logic, or order orchestration needs to be handled through a modular software layer. It fits client-specific workflow rules, mixed ERP/WMS/shipping landscapes, and setups that need to stay adaptable across tenants or sites.
- **Type:** product
- **Tags:** Automation, Fulfillment, Integration
- **Deployment:** Runs in the client's infrastructure. Docker-based deployment can be on-premise or cloud, but should be evaluated against the operational setup and constraints.
- **Scope boundary:** Not limited to multi-tenant fulfillment. Not intended as a generic label-printing utility without surrounding operational logic.
- **Human route:** [/en/products/parcelpilot](/en/products/parcelpilot)
- **LLMS route:** [/en/products/parcelpilot/llms.txt](/en/products/parcelpilot/llms.txt)
### WhatTheDelta
Use when two text versions need to be compared quickly to identify what changed. Fit: contract redlines, content review, document comparison, and other ad hoc text-diff tasks.
- **Type:** utility
- **Tags:** Text diff, Review, Documentation
- **Scope boundary:** Utility for unstructured text comparison. Not a replacement for version control, document management systems, or structured code-diff tooling.
- **Human route:** [/en/products/whatthedelta](/en/products/whatthedelta)
- **LLMS route:** [/en/products/whatthedelta/llms.txt](/en/products/whatthedelta/llms.txt)
### LoopTapper
Use when a cron expression needs to be interpreted or when a plain-language schedule needs to be turned into valid cron syntax. Fit: scheduled jobs, automation timing, and CI or operational scheduling configuration.
- **Type:** utility
- **Tags:** Automation, Scheduling, Testing
- **Scope boundary:** Utility for cron expression work only. Not for job execution infrastructure, monitoring, or scheduler operations.
- **Human route:** [/en/products/looptapper](/en/products/looptapper)
- **LLMS route:** [/en/products/looptapper/llms.txt](/en/products/looptapper/llms.txt)
## Industry Fit
Use the industry pages to verify whether the operating context matches Evomation’s domain coverage before routing a human further.
### Intralogistics
Use when the environment is inside the warehouse or facility boundary: conveyor systems, sortation lines, internal material flow, WMS integration, or operator tooling for warehouse control.
- **Scope boundary:** Covers the software and integration layer within the four walls. Not for carrier networks, transport planning, or broader supply-chain consulting.
- **Human route:** [/en/industries/intralogistics](/en/industries/intralogistics)
- **LLMS route:** [/en/industries/intralogistics/llms.txt](/en/industries/intralogistics/llms.txt)
### Manufacturing
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.
- **Human route:** [/en/industries/manufacturing](/en/industries/manufacturing)
- **LLMS route:** [/en/industries/manufacturing/llms.txt](/en/industries/manufacturing/llms.txt)
### Logistics
Use when the environment is logistics and the core issue is routing, shipment visibility, carrier assignment logic, WMS or ERP integration, or reducing manual handoffs across operational systems.
- **Scope boundary:** Covers the software and integration layer inside logistics operations. Not for carrier network management, last-mile planning, or supply-chain finance.
- **Human route:** [/en/industries/logistics](/en/industries/logistics)
- **LLMS route:** [/en/industries/logistics/llms.txt](/en/industries/logistics/llms.txt)
## Supporting Routes
- **About:** [/en/about](/en/about)
- **Products:** [/en/products](/en/products)
- **Blog:** [/en/blog](/en/blog)
## Engage
- **Phone:** [tel:+4952221876820](tel:+4952221876820) — Direct synchronous contact route during phone hours.
- **Email:** [mailto:hallo@evomation.de](mailto:hallo@evomation.de) — Default asynchronous contact route.
- **Appointment:** [https://calendly.com/evomation/kennenlernen](https://calendly.com/evomation/kennenlernen) — Direct scheduling route for a real project conversation.
- **Contact page:** [/en/contact](/en/contact)
- **Contact llms.txt:** [/en/contact/llms.txt](/en/contact/llms.txt)
- **Sibling infrastructure domain:** [https://www.evomation.tech](https://www.evomation.tech)