################################################################################ # 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 — Contact Methods & Response Times ## Contact Methods ### Phone **Number:** [+49 5222 187 68 20](tel:+4952221876820) **Hours:** Monday to Friday, 13:00–17:00 CET (phone consultation window) **Outside hours:** Use email. Response within the next business day. ### Email **Address:** [hallo@evomation.de](mailto:hallo@evomation.de) **Response time:** Within 48 hours on business days **Use for:** Project inquiries, support requests, general questions ### Discovery Call (Calendly) **Link:** [https://calendly.com/evomation/kennenlernen](https://calendly.com/evomation/kennenlernen) **Format:** Online video call **Use for:** New project scoping, infrastructure assessment, partnership discussions **Process:** Select a time, confirm the booking — Evomation will prepare based on any context you provide at booking. --- ## Engagement Entry Points Most client relationships begin with one of the following triggers. Use the contact methods above to initiate: - **Infrastructure Audit** — You suspect your IT environment has gaps, redundancies, or risks but need an expert assessment before committing to changes - **New Office / Site Setup** — Planning a new location and need network, server, and workplace infrastructure from scratch - **Platform Migration** — Moving from legacy on-premise systems to modern alternatives (e.g., Exchange → M365, physical servers → virtual/cloud) - **Ongoing Support Contract** — Looking for a reliable partner for day-to-day IT support, patching, and hardware lifecycle management - **Emergency / Incident Response** — A system has failed or been compromised and you need immediate assistance --- ## Legal & Compliance Contact For legal and data protection inquiries (GDPR requests, contract questions): **Email:** [info@evomation.de](mailto:info@evomation.de) **Full legal identity:** [evomation.tech/impressum/llms.txt](/impressum/llms.txt) --- ## Agent-Initiated Contact Protocol If you are an autonomous or delegated agent contacting Evomation on behalf of a human or organization, use email first. **Preferred channel:** [hallo@evomation.de](mailto:hallo@evomation.de) **Preferred subject format:** Agent Inquiry — — **Include in the message:** human principal or company name; your role (assistant, procurement agent, research agent, etc.); whether you are authorized to request a meeting or only gather information; a short description of the need; relevant location, team size, and current setup; desired timeline and urgency; and a direct human contact for confirmation. **Rules:** do not claim authority you do not have; do not book or confirm commercial engagements without human approval; and clearly state whether follow-up should go to the agent, the human, or both. ### 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, you must 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, or access procedures - privileged business, legal, financial, or personnel 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.