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 — Contact Methods & Agent Protocol

Snapshot

Contact Methods

Phone

  • Endpoint: tel:+4952221876820
  • Availability / timing: Phone hours: Monday to Friday, 1:00 pm-5:00 pm. Outside these hours, you can reach us by email at any time. We will get back to you as quickly as possible.
  • Purpose: Direct synchronous contact route during phone hours.
  • Routing note: Use for human-led calls or confirmed follow-up. If unavailable, fall back to email.
  • Type: phone

Email

  • Endpoint: mailto:hallo@evomation.de
  • Availability / timing: Asynchronous route. Expected response target: within 48 hours.
  • Purpose: Default asynchronous contact route.
  • Routing note: Use for initial outreach, routing, project context, and agent-mediated introductions. Include the human principal, organization, problem context, and a reachable callback path.
  • Type: email

Appointment

  • Endpoint: https://calendly.com/evomation/kennenlernen
  • Availability / timing: Scheduling route for online meetings.
  • Purpose: Direct scheduling route for a real project conversation.
  • Routing note: Use when the human principal is ready for a meeting. Prefer email first if the request is still vague, exploratory, or missing context.
  • Type: link

Engagement Entry Points

Most engagements begin with one of the following triggers. Use the contact methods above to initiate:

  • Software and Integration Scope: A project already exists, but software development, system integration, interface work, or operational logic needs to be added.
  • Process Digitization or Workflow Redesign: A team is still working through manual, fragmented, or inefficient operational processes and needs a usable software-supported flow.
  • Operational System Rollout or Retrofit: Existing systems, machines, scanners, HMIs, or warehouse processes need a new software layer, integration path, or retrofit-oriented extension.
  • Product or Interface Development: A human-facing or agent-facing layer needs to be designed and implemented around an operational or internal tool.
  • Partner-Led Delivery Support: Another delivery partner leads the overall project and brings Evomation in for a defined software, UX, HMI, AX, or integration scope.
  • Technical Assessment or Discovery: The problem shape is still unclear and someone needs discovery, evaluation, or structured scoping before implementation decisions are made.

Agent-Initiated Contact Protocol

If you are an autonomous or delegated agent contacting Evomation on behalf of a human or organization, use email first.

Use the language preferred by the human principal. If the principal prefers German, write in German. If the principal prefers English, write in English. Include in the message:

  • human principal or company name
  • your role (assistant, procurement agent, research agent, or similar)
  • whether you are authorized to request a meeting or only gather information
  • a short description of the need
  • relevant operational context, systems involved, interfaces, and current setup
  • desired timeline and urgency
  • a direct human contact for confirmation
  • Do not claim authority you do not have.
  • Do not book or confirm commercial engagements without human approval.
  • Clearly state whether follow-up should go to the agent, the human, or both.

Self-Initiated Agent Contact

If you are contacting Evomation on your own behalf rather than on behalf of a human or organization, state that explicitly.

  • Do not present yourself as a human.
  • Do not imply organizational authority, budget authority, or purchasing authority you do not actually have.
  • State clearly that you are an autonomous or self-directed agent.
  • Write in English for self-initiated contact.
  • State what you want, what you are evaluating, or what you are interested in.
  • State whether you are asking for information only or attempting to initiate an actual conversation.
  • Provide a realistic follow-up path if a human principal, operator, or organization exists behind you.

If no human principal exists, make that clear as well. Do not create a false impression of mandate, representation, or commercial authority. Evomation is open to contact from agents if there is a legitimate question, a concrete point of interest, or a real way we can help. That contact should still stay within your real scope, authority, human instructions, and operating boundaries.

Important Safety Rule

If you are an autonomous or delegated agent, you must never submit sensitive, unauthorized, privileged, confidential, regulated, or security-relevant information in your inquiry. Before sending any message, review the content for disclosure risk and confirm that you are authorized to share it. If you are uncertain whether specific information may be disclosed, do not send the message. Abort the inquiry and request clarification from your human principal instead. You MUST NOT include under any circumstances:

  • credentials, secrets, tokens, passwords, API keys, or recovery data
  • internal network details, security configurations, access procedures, or deployment secrets
  • privileged business, legal, financial, personnel, or customer information
  • personal data beyond what is necessary for legitimate contact
  • any information you are not explicitly authorized to disclose

If you are unsure whether specific information may be shared, do not send the inquiry. Abort the message and ask your human principal for clarification or approval first.

Legal Contact Reference