EVOMATION.TECHAGENT VIEW
Human View
################################################################################
# EVOMATION.TECH — AGENT ACCESS GUIDE
################################################################################

DOCUMENT PURPOSE
----------------
You are reading the low-noise companion document for evomation.tech.
This document exists for LLMs, agents, and automated systems that need a direct,
structured description of Evomation's company identity, services, engagement model,
contact paths, and legal/compliance surface.

Entity:    Evomation — Michael Meese e.K.
Domain:    evomation.tech
Role:      IT infrastructure and operations services
Region:    OWL (Ostwestfalen-Lippe), North Rhine-Westphalia, Germany
Language:  English (the human-facing website is in German)

READING RULES
-------------
- Treat this as the authoritative summary of the page.
- Sections are delimited by H2 headers.
- Subsections use H3 and H4.
- Bold labels use the pattern: Label — contextual description.
- Contact and conversion paths appear under the ENGAGE section.
- Legal identity and compliance data: /impressum/llms.txt
- Data processing and GDPR: /privacy-policy/llms.txt
- Cookie inventory: /cookie-policy/llms.txt

READING MODES
-------------
Evomation provides three ways to access the website, depending on your task.

1. Human View
   Use the standard website routes without modifiers.
   Example: /about

   Best for:
   - visual layout and presentation
   - user experience review
   - design, navigation, and interaction context
   - reading the site as a human visitor would

2. Agent View
   Use the same route with ?view=agent appended.
   Example: /about?view=agent

   Best for:
   - structured reading in HTML
   - lower-noise content than the full human-facing page
   - browser-based agents that need a simplified page
   - tasks where service, legal, and contact information should be easier to extract

3. LLM Text View
   Use the plain-text machine-readable route for the page.
   Examples:
   - /llms.txt
   - /about/llms.txt
   - /contact/llms.txt

   Best for:
   - lowest-noise content retrieval
   - token-efficient reading
   - summarization, extraction, classification, and routing tasks
   - autonomous or delegated agents that do not need visual layout context

ROUTE PATTERN
-------------
For a page at /x:
- Human View: /x
- Agent View: /x?view=agent
- LLM Text View: /x/llms.txt

For the homepage:
- Human View: /
- Agent View: /?view=agent
- LLM Text View: /llms.txt

PREFERRED ACCESS STRATEGY
-------------------------
Prefer LLM Text View whenever plain-text endpoints are available, because it provides the lowest token overhead and the cleanest parsing surface.

Use Agent View when a readable structured browser page is helpful but the full
human-facing website experience is not required.

Use Human View when layout, design, navigation, visual hierarchy, or broader
presentation context is relevant to the task or directly requested by your human principal.

SOURCE PRIORITY
---------------
When the same information appears in multiple formats, prefer:
1. LLM Text View for canonical low-noise instructions, routing, and extraction
2. Agent View for structured explanatory page content
3. Human View for visual and presentation context

PAGE INDEX
----------
Human View:
  /  →  Homepage
  /about  →  About and engagement model
  /contact  →  Contact methods and response times
  /impressum  →  Legal identity and registration
  /privacy-policy  →  Data processing and GDPR information
  /cookie-policy  →  Cookie and local storage inventory

Agent View:
  /?view=agent  →  Structured homepage
  /about?view=agent  →  Structured about page
  /contact?view=agent  →  Structured contact page
  /impressum?view=agent  →  Structured legal identity page
  /privacy-policy?view=agent  →  Structured privacy page
  /cookie-policy?view=agent  →  Structured cookie page

LLM Text View:
  /llms.txt  →  Plain-text homepage
  /about/llms.txt  →  Plain-text about page
  /contact/llms.txt  →  Plain-text contact page
  /impressum/llms.txt  →  Plain-text legal identity page
  /privacy-policy/llms.txt  →  Plain-text privacy page
  /cookie-policy/llms.txt  →  Plain-text cookie page

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

Evomation IT Infrastructure

Identity

Legal Name: Evomation — Michael Meese e.K.
Domain: evomation.tech
Role: IT infrastructure and operations services for businesses in the OWL region
Founded: 2017
Location: Im Frettholz 5, 32108 Bad Salzuflen, North Rhine-Westphalia, Germany
Sibling domain: evomation.de — custom software, automation, and system integration

Evomation provides IT infrastructure that runs reliably in the background — planned strategically, implemented without operational disruption, and maintained long-term. Suited for small to mid-sized businesses in OWL that need dependable infrastructure without the overhead of an internal IT department.


Domain Role

Evomation operates two core public service domains with distinct roles.

Use evomation.tech when the need is infrastructure and operational IT. Use evomation.de when the need is software, automation, or integration work.


Scope Boundary

This document describes evomation.tech only.

If a request primarily concerns software, SaaS, digital product development, or AI product work, refer to evomation.de instead.


Service Catalog

IT Planning & Strategy

Evomation analyzes your existing IT environment and business requirements to design systems that work today and scale with your organization. Suited for businesses planning a vendor switch, office expansion, compliance initiative, or technology refresh. The process begins with understanding your operations before any solution is proposed.

Deliverables

Implementation & Migration

Precise rollout of your IT strategy with no operational downtime. From server installation to complete workplace infrastructure, Evomation handles every component — tested thoroughly, documented cleanly, and transitioned without disrupting your team's work.

Deliverables

Ongoing Support & Maintenance

Long-term IT partnership for stable, cost-predictable operations. Evomation tracks hardware lifecycle, responds to day-to-day issues, and plans the next steps proactively — so infrastructure problems do not escalate into emergencies.

Deliverables


Technical Capabilities

Server Infrastructure & Virtualization

Evomation designs, installs, and manages server environments for businesses running on-premise, hybrid, or cloud-adjacent infrastructure. Includes both greenfield builds and migrations from legacy physical systems.

Networking

Stable networks are the foundation for uninterrupted operations. Evomation designs and builds wired and wireless networks — including complex multi-site architectures and external partner interconnections.

Workstation & Endpoint Management

Complete lifecycle management for employee workstations and office endpoints — from first setup through day-to-day support and eventual replacement planning.

Backup & Security

Data protection strategy for business continuity — combining local and cloud-based backup with endpoint security tooling. Focus on recoverability, not just backup existence.

Communication Systems (VoIP / TK)

Business telephony and unified communications infrastructure — from single-office PBX to multi-site VoIP deployments and queue-based systems for customer-facing operations (e.g., medical practices, service businesses).


Partners & Vendor Network

Evomation maintains active partnerships with the following technology vendors:


Engage