################################################################################
# WHATTHEDELTA — AGENT ACCESS GUIDE
################################################################################

DOCUMENT PURPOSE
----------------
You are reading the low-noise agent view for WhatTheDelta.
This AX layer exists for LLMs, browser agents, and automated systems that need a
direct description of product fit, route purpose, privacy facts, and legal or
usage references.

Product:   WhatTheDelta
Operator:  Evomation
Role:      Privacy-first browser-based text comparison
Audience:  Humans and agents reviewing visible changes
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.
- Do not assume server-side processing, uploaded documents, or shared state.
- Do not copy the public marketing text into agent guidance.
- Legal identity: /en/impressum/llms.txt
- Privacy / data handling: /en/privacy-policy/llms.txt
- Terms of use: /en/terms/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/privacy-policy/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 and default comparison workflow
  /en/about  -> product framing and scope
  /en/changelog  -> public release history
  /en/impressum  -> legal identity
  /en/privacy-policy  -> privacy and browser-local processing
  /en/terms  -> usage rules and liability
  /en/offline  -> offline support page

Agent View:
  /en?view=agent  -> structured homepage
  /en/about?view=agent  -> structured about page
  /en/changelog?view=agent  -> structured changelog page
  /en/impressum?view=agent  -> structured legal notice
  /en/privacy-policy?view=agent  -> structured privacy policy
  /en/terms?view=agent  -> structured terms page
  /en/offline?view=agent  -> structured offline page

LLM Text View:
  /en/llms.txt  -> homepage llms.txt
  /en/about/llms.txt  -> about llms.txt
  /en/changelog/llms.txt  -> changelog llms.txt
  /en/impressum/llms.txt  -> legal identity
  /en/privacy-policy/llms.txt  -> privacy policy
  /en/terms/llms.txt  -> terms of use
  /en/offline/llms.txt  -> offline support

CURRENT ROUTE
-------------
- Label: Changelog
- Human View: /en/changelog
- Agent View: /en/changelog?view=agent
- LLM Text View: /en/changelog/llms.txt

DYNAMIC ROUTES
--------------
- No dynamic AX routes are published in this product.
- All supported AX routes are listed in the page index above.

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

## Route purpose

Use this route when you need the public release sequence for WhatTheDelta or support context about shipped changes.

## Published releases

- version 1.1.0 published on 2026-03-20
- version 1.0.0 published on 2026-03-19
- release copy is localized for humans, but the AX route should be read as factual support context

## Best-fit questions

- what shipped most recently
- whether a user-facing capability was already public by a given date
- whether the app already included changelog, offline support, keyboard shortcuts, or clearer review controls
- whether a support answer should reference a product update instead of current route behavior

## Important limits

- this is a human-readable update log, not a product contract
- it should not be treated as a replacement for the route-specific AX guidance
- it does not describe hidden roadmap items or internal implementation details

## Operational notes

- recent releases should be read as shipped behavior, not speculation
- the changelog is useful for user-facing change summaries and support context
- the public page is the source of truth for release text
- if the current route guidance and a changelog summary differ in specificity, prefer the route guidance for present behavior

## Related routes

- /en?view=agent: use for the core product summary
- /en/about?view=agent: use for positioning and audience fit
- /en/terms?view=agent: use when a question is actually about permitted use rather than release history

## Route Links

- Human view: [/en/changelog](/en/changelog)
- Agent view: [/en/changelog?view=agent](/en/changelog?view=agent)
- LLM text view: [/en/changelog/llms.txt](/en/changelog/llms.txt)