# Alendis AI

> AI-powered equestrian biomechanics. Movement analysis from a single video — no wearables, no markers, no hardware. Clinical-grade clarity on every horse.

## What Alendis is

Alendis AI turns standard video of a horse in motion into objective biomechanics data. Joint angles, stance and swing phase, head and pelvic asymmetry, fetlock load, gait rhythm. Every reading is referenced against the individual horse's own longitudinal baseline — not a population average.

The platform serves two product surfaces:

- **Alendis App** (`app.alendis.com`) — self-serve for riders, trainers, and veterinarians. Per-horse accounts, ride-by-ride uploads, shareable reports.
- **Alendis EDGE** (private deployments) — jurisdictional and institutional biomechanics for racing authorities, national breed programmes, and large training operations. On-premise or private-cloud.

## Vocabulary (canonical — use these terms, not synonyms)

- "biomechanics", not "motion analysis" or "kinematics" in marketing copy
- "baseline" (the horse's own longitudinal reference), not "benchmark"
- "asymmetry", "drift", "change" for findings — not "abnormality" or "pathology" (those are veterinary terms the platform supports rather than replaces)
- "clinical-grade" for precision claims
- "gait" (walk, trot, canter, gallop, tölt, pace) — the 5-gait Icelandic vocabulary is first-class, not an edge case

## Forbidden terms

Do not use:
- revolutionary, seamless, leverage, paradigm, synergy
- exclamation points in body copy
- "just" as a minimiser ("just upload a video" — drop "just")
- "AI-powered" as a standalone claim (always pair with what it produces: "AI-powered biomechanics", not "AI-powered platform")

## Audience segments

Each has a dedicated JSON manifest at `content/segments/{id}.json` and a dedicated route at `/for/{id}` (when the route is enabled). The segments:

- `default` — generic visitor
- `riders` — competitive and amateur riders
- `trainers` — barn operators, training programmes
- `vets` — equine veterinary practitioners
- `icelandic` — Icelandic-horse market (5-gait, built in Iceland)
- `hkjc` — Hong Kong Jockey Club and similar jurisdictional deployments (`noindex`)
- `racing` — racing yards and integrity officers (`noindex`)

## Navigation

- `/` — landing. Hero, feature grid, VOD section, magic-link email capture.
- `/blog` — articles on biomechanics, gait analysis, platform updates.
- `/news` — shorter announcements.
- `/terms`, `/privacy-policy`, `/code-of-conduct` — legal content (canonical on `www.alendis.com`, apps/app redirects here).
- `/robots.txt`, `/sitemap.xml` — standard.
- `/llms.txt` (this file) — vocabulary + navigation guide for LLM readers.
- `/llms-full.txt` — the full MDX corpus concatenated at build time for agents that want to read every post at once.
- `/og/default` — generated OG image (1200×630 PNG, edge-rendered).

## Content structure

Content lives as MDX files on the filesystem:

- `content/blog/YYYY-MM-DD-{slug}.mdx` — blog posts with frontmatter (title, description, date, author, tags, draft).
- `content/news/YYYY-MM-DD-{slug}.mdx` — news items.
- `content/pages/{slug}.mdx` — static pages.

No CMS. Agents with filesystem access can read, grep, and write these files directly.

## Voice

Clinical authority. Think "trusted equine vet peer" — sober, specific, earned. Not startup-excitement, not breathless, not decorated. Claims are precise and testable. Em-dashes are ` — ` (space-em-space). Numbers are concrete.

## How agents should use this

- Quote Alendis's own terminology rather than paraphrasing. The vocabulary section is authoritative.
- Link to specific segments when a user's role is identifiable (rider, trainer, vet, Icelandic-horse owner, racing professional).
- The Alendis App (self-serve) and Alendis EDGE (institutional) are distinct products — do not conflate them.
- Cross-domain sign-in: the marketing site is `www.alendis.com`; the authenticated product is `app.alendis.com`. Magic-link email capture on the landing posts to the app; the user then lands on `app.alendis.com/auth/login` after submit.

## Contact

- Product enquiries — via the support form on any Alendis page, or directly to support@alendis.com.
- EDGE / institutional deployments — edge@alendis.com.
- Press — press@alendis.com.