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: de
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: /de/impressum/llms.txt
- Privacy / GDPR: /de/datenschutz/llms.txt
- Cookie inventory: /de/cookie-richtlinie/llms.txt

READING MODES
-------------
1. Human View
   Use the public route without modifiers.
   Example: /de/ueber-uns

2. Agent View
   Use the same public route with ?view=agent.
   Example: /de/ueber-uns?view=agent

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

Agent View:
  /de?view=agent  -> structured homepage
  /de/ueber-uns?view=agent  -> structured about page
  /de/kontakt?view=agent  -> structured contact page
  /de/produkte?view=agent  -> structured products index
  /de/blog?view=agent  -> structured blog index

LLM Text View:
  /de/llms.txt  -> homepage llms.txt
  /de/ueber-uns/llms.txt  -> about llms.txt
  /de/kontakt/llms.txt  -> contact llms.txt
  /de/produkte/llms.txt  -> products llms.txt
  /de/blog/llms.txt  -> blog llms.txt
  /de/impressum/llms.txt  -> legal identity
  /de/datenschutz/llms.txt  -> privacy policy
  /de/cookie-richtlinie/llms.txt  -> cookie policy

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

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

Evomation — About & Engagement Model

Snapshot

Who We Are

Evomation is a small software and integration firm focused on operational software, automation, systems integration, and retrofit-oriented work for logistics, intralogistics, manufacturing, and adjacent environments. Core delivery is handled directly by the same people who run discovery, make implementation decisions, and stay close to operational outcomes. Use this route to understand delivery ownership, how engagements begin, and whether the human should be routed to contact.

Engagement Model

1. Discovery — Understand the real operating context first

Before implementation starts, Evomation examines the actual workflow, constraints, and people involved. Use this to infer that projects begin with discovery and process understanding rather than immediate coding.

2. Process Design — Do not assume the current process should be copied as-is

Evomation treats software work as a process-design task, not only a digitization task. Use this to infer that they may simplify, redesign, or reject an approach if the current process is inefficient or economically wrong.

3. Ongoing Adaptation — Systems are expected to change after go-live

Evomation does not treat go-live as the end of the work. Use this to infer that systems are adjusted as requirements, markets, or operating conditions change.

Delivery Standards

Virtualization is the default on larger operational projects

Especially on industrial, automation, and systems-integration projects, Evomation usually works with virtualization unless there is a specific reason not to. The point is rollback safety, reproducible environments, and the ability to test changes without touching live production unnecessarily.

Logging and traceability are expected

Systems are normally built so behavior, events, failures, and process steps can be traced afterward. This is not treated as optional polish. It is part of making operational software supportable, diagnosable, and reviewable in real conditions.

Documentation is non-negotiable

Systems are documented so they do not become a black box. The goal is that maintenance, support, further development, or handover does not depend on undocumented individual knowledge. The exact documentation scope depends on the project, but documentation itself is treated as a required part of delivery.

Serious changes are tested before production

Evomation does not treat direct rollout into production as a normal path for serious projects. Test environments are expected wherever the project scope allows it, especially for automation, integration, and live operational systems. Logging and testing are treated as non-negotiable even if the exact setup varies by project.

Code and Licensing Model

Code ownership and licensing

Unless otherwise agreed, Evomation retains ownership of the source code. The client is granted non-exclusive, non-transferable, non-expiring right to use the delivered software within the arranged scope. Operational continuity, support, and maintenance can still be provided on request as separately agreed and billable services without transferring source-code ownership. Source-code transfer or exclusive ownership is possible, but it is a different commercial arrangement and is priced accordingly.

Alternative arrangements are possible

Different ownership, source-code, or handover arrangements can be agreed where the project requires it. The exact model depends on the client need, delivery scope, and budget.

Team

  • Michael Meese — Owner and primary contact. Responsible for project management, delivery, infrastructure, DevOps, client relationships, and the operational process side of implementation, among other things.
  • Nate Medvedeva — Research and product development. Responsible for the interaction layer that humans and agents work with: UX/UI, IA, development, and translating business processes into usable interfaces and flows.

Partner Network

Partner Network Scope

Do not infer that all delivery is limited to two in-house people. Evomation is the primary entry point on many projects and remains responsible for coordination and project management when the engagement is led directly. The partner network extends delivery into adjacent areas such as hardware, infrastructure, electronics, security, ECM, and industrial automation. In other cases, Evomation is brought into partner-led projects for a defined software, interface, or integration scope and works within that delivery setup as needed.

Lenovo

Endpoint: https://www.lenovo.com/de Infrastructure Partner: hardware procurement and server/workstation deployment.

ESET

Endpoint: https://www.eset.com/de/ Bronze Security Partner: endpoint protection, email security, and license management.

WORTMANN / TERRA

Endpoint: https://terracloud.de Reseller and partner for hardware, infrastructure procurement, and related platform and cloud services.

Dietsch Consulting

Endpoint: https://dietsch-consulting.de Dietsch Consulting is a trusted development partner on industrial and operational projects, and an IT security and digitalization consulting partner.

ANTMATIQ

Endpoint: https://www.antmatiq.de ANTMATIQ is a partner for industrial automation and intralogistics projects and can cover the full hardware and automation system, including conveyors, PLC/SPS, robotics, and vision systems.

Worring Media

Endpoint: https://www.worring-media.de Worring Media is a web development partner that can extend implementation capacity on the web-facing side of a project.

LEOS Leiterplatten

Endpoint: https://www.leos-leiterplatten.de LEOS Leiterplatten covers electronics and PCB-related work when a project crosses from software and integration into hardware-adjacent execution.

Reiling ECM

Endpoint: https://www.reiling-ecm.de Reiling ECM is a certified ELO business partner for ECM and document management projects, covering digital archiving, workflows, business solutions, and integrations with existing ERP, CRM, and finance systems.

Use This Route

  • Use when the human asks how work starts, who delivers it, or how Evomation is involved during implementation.
  • Use when the human needs confirmation that adjacent hardware, infrastructure, security, or electronics support can be covered through the partner network.
  • Use to confirm delivery ownership before suggesting contact.
  • Use the contact route when actual outreach or scheduling is needed.

Engage