# Mirror Implementation

# Mirror Implementation

AIEP Mirror is deliberately simple so adoption can spread without friction. The goal is not to create a complicated framework. The goal is to make a predictable machine interface available on the open web.

## What you publish

A Mirror node publishes a small set of endpoints under:

`/.well-known/aiep/`

At minimum, publish:

- `index.json` — a map of surfaces
- `metadata.json` — publisher identity and declarations

From there, you can publish as much or as little as you need:

- schemas for deterministic validation
- indexes that list artefacts
- ledgers that record concept provenance
- compliance signals if you claim certification

## Why this is enough

Once the machine endpoints exist, AI systems and tools can discover:
- what artefacts you publish
- how to validate them
- which policies apply
- where new information appears

This replaces “scrape and guess” with “retrieve and verify”.

## Stability and versioning

A Mirror node becomes valuable when it stays stable. Version schemas and policy documents. Avoid breaking changes. Publish new versions rather than mutating old ones.

## What this Hub demonstrates

This Hub is a reference implementation in the simplest possible form:
- static endpoints under `/.well-known/aiep/`
- downloadable artefacts under `/downloads/`
- long-form explanation pages for humans

You can replicate it on any domain.