# Example Mirror

# Example Mirror

The easiest way to understand AIEP Mirror is to see an example structure. A Mirror node is simply a site that publishes a machine interface and makes its artefacts discoverable.

## Minimal structure

A minimal Mirror node publishes:

- `/.well-known/aiep/index.json`
- `/.well-known/aiep/metadata.json`

That alone is enough for machines to discover participation and basic policy.

## Recommended structure

A practical structure for a small organisation might look like:

- `/.well-known/aiep/index.json`
- `/.well-known/aiep/metadata.json`
- `/.well-known/aiep/schemas/`
- `/.well-known/aiep/artefacts/index.json`
- `/.well-known/aiep/compliance/` (only if claiming certification)
- `/.well-known/aiep/innovation-ledger/` (optional)

Artefacts can live anywhere. The point is that the machine interface tells the world where they are.

## Why “well-known” matters

The web already uses well-known URIs for predictable discovery. AIEP uses the same habit. This keeps adoption simple and compatible.

## This Hub as the exemplar

This Hub is designed to be an exemplar Mirror node. You can inspect it directly under:

`/.well-known/aiep/`

and replicate the pattern in your own domain.