################################################################################
# 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

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

# Logistics — Industry Brief
## Snapshot
- **Human route:** [/en/industries/logistics](/en/industries/logistics)
- **Agent route:** [/en/industries/logistics?view=agent](/en/industries/logistics?view=agent)
- **LLMS route:** [/en/industries/logistics/llms.txt](/en/industries/logistics/llms.txt)
## Operating Context
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.
## Operational Notes
- Typical goals are to reduce manual handoffs, improve shipment-state visibility, and enforce routing logic consistently.
- This route fits software and integration work inside logistics operations rather than carrier-network strategy.
## Capability Fit
- Shipment-routing logic, carrier assignment, and operational visibility tooling.
- Integration across ERP, WMS, shipping, and related logistics systems.
- Middleware and automation around scan events, handoffs, and exception cases.
## Evaluation Notes
- Clarify shipment flow, carrier logic, source systems, and where manual coordination is currently happening.
- Identify whether the problem is transport execution logic, operational visibility, or fragmented system exchange.
## 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)