################################################################################
# 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
- General terms and conditions: /agb/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
  /agb  →  General terms and conditions (AGB)

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
  /agb?view=agent  →  Structured AGB 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
  /agb/llms.txt  →  Plain-text AGB page

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

Evomation — General Terms and Conditions (AGB)

Use this route to retrieve Evomation general terms for IT services and the sale and delivery of standard hardware and software.

Version date: December 15, 2025

Route Usage

• Treat as the contractual terms reference for B2B engagements with Evomation.
• Use for questions about offers, payment, delivery, warranty, liability, confidentiality, data processing, jurisdiction, or arbitration.
• Not a substitute for case-specific contract amendments or individual SLA terms.

Legal Entity

Entity: Evomation-Michael Meese e.K.
Address: Im Frettholz 5, 32108 Bad Salzuflen, Germany
Commercial Register: HRA 6224
Registrar: Amtsgericht Lemgo
VAT ID: DE354802166

Scope

These terms apply to contracts covering IT services (consulting, support, administration, project services) and the sale and delivery of standard hardware and software, including third-party licenses and subscriptions procured on behalf of the client. They apply to all future business relationships unless expressly deviated from in text form.

Client general terms are rejected unless expressly accepted by Evomation.

1. Offers, Contract Conclusion, Scope Changes

• Offers and effort estimates are non-binding unless expressly marked as binding.
• Contracts form via order confirmation, acceptance of a binding offer in text form, or commencement of performance.
• Scope changes require agreement in text form.
• Hardware and software are generally procured by Evomation in its own name and resold to the client; manufacturer license terms take precedence.

2. Performance, Cooperation, Acceptance, Deadlines

• Unless a work contract is agreed, Evomation provides services, not a guaranteed outcome.
• Deadlines are binding only if agreed in text form as binding.
• Client cooperation obligations are required for timely performance.
• Support hours and response times apply only where agreed in an SLA or offer.
• Work acceptance: 10 business days for review after provision unless defects are notified.
• Force majeure events suspend obligations for the duration of the disruption.

3. Remuneration, Billing, Payment

• Prices are net plus statutory VAT unless stated otherwise.
• Services are billed time-and-material unless otherwise agreed.
• Billing occurs after project end, milestones, or month-end; interim invoices are permitted.
• Hardware and software are billed when setup/use begins; advance payment may be required.
• Invoices are due within 14 days without deduction.
• Set-off and retention rights are limited to undisputed claims on the same contract.

4. Delivery, Risk Transfer, Retention of Title

• Delivery dates are binding only if expressly agreed.
• Risk passes to the client upon handover to the carrier.
• Retention of title applies until full payment of all claims from the business relationship.

5. Usage Rights to Work Results

• Client receives a simple, non-transferable usage right upon full payment for created work results.
• Evomation may reuse abstracted components and methods without disclosing client secrets.
• Standard software usage is governed by manufacturer license terms.

6. Defect Claims / Warranty

• Statutory rules apply unless otherwise agreed below.
• B2B defect limitation period: 12 months from delivery or acceptance.
• Client must inspect goods and notify defects promptly; Section 377 HGB applies in commercial trade.
• For services, no specific outcome is owed; manufacturer warranties apply per manufacturer terms.

7. Liability

• Damage claims are excluded beyond the scope described in these terms.
• Liability for slight negligence on essential duties is limited to typical foreseeable contractual damage.
• Certain claims have a one-year limitation period unless mandatory law provides otherwise.
• Liability exclusions also apply to employees and vicarious agents.

8. Confidentiality

Parties must keep confidential information secret and use it only for contract performance, subject to standard exceptions for public knowledge, lawful third-party receipt, and statutory disclosure duties.

9. Data Protection

• A data processing agreement (Art. 28 GDPR) is concluded before processing personal data on behalf of the client.
• Evomation does not process client data content for its own purposes without express agreement.

10. Place of Performance / Jurisdiction / Applicable Law

• Place of performance: Bielefeld, unless otherwise agreed.
• Jurisdiction: Amtsgericht or Landgericht Bielefeld, with additional options and obligations as stated in the German terms.
• German substantive law applies; CISG is excluded.

11. Arbitration

Evomation may elect DIS arbitration rules for dispute resolution, excluding ordinary courts, with German as the language of proceedings unless otherwise agreed.