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

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

LoopTapper — Product Brief

Snapshot

Operational Role

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. Scope boundary: Utility for cron expression work only. Not for job execution infrastructure, monitoring, or scheduler operations.

Operational Notes

  • Useful for job scheduling, CI timing, and operational automation setup where cron syntax is the bottleneck.

Capability Notes

  • Interprets cron syntax into human-readable scheduling logic.
  • Helps translate plain scheduling requirements into cron expressions.

Route Usage

  • Use this route to decide whether the product matches the operational problem shape.
  • Use the contact route when implementation scope, integration constraints, or delivery setup must be clarified with a human.
  • Use the human route only when screenshots, interface layout, or public positioning context matters.

Engage