> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atlasyield.club/llms.txt
> Use this file to discover all available pages before exploring further.

# What AtlasYield is

> The independent judgment layer for on-chain yield.

<Note>
  Everything in these docs — scores, bands, allocations, and methodology — is research and
  general information, **not investment advice**. See [Limitations and disclaimer](/limitations).
</Note>

DeFi produces thousands of yield-bearing vaults, and almost no neutral way to judge them.
Yields are advertised by the protocols that earn fees from them; aggregators rank by APY;
the risk that actually destroys principal — exploits, admin keys, emission cliffs, frozen
withdrawals — is left for the depositor to price alone.

AtlasYield is built as the judgment layer that sits between depositors and that universe.
It does three things:

<CardGroup cols={1}>
  <Card title="The Atlas Score" icon="gauge-high" href="/score/pillars-and-factors">
    A 0–100 rating of every vault it covers, built from four pillars and sixteen factors,
    published on a timestamped, git-verifiable public record.
  </Card>

  <Card title="The Atlas Engine" icon="diagram-project" href="/engine/how-it-works">
    A deterministic portfolio builder that turns scored vaults into a risk-adjusted
    allocation under explicit, published policy constraints.
  </Card>

  <Card title="Monitoring and calls" icon="tower-observation" href="/monitoring">
    Continuous re-scoring of every covered vault, with dated, evidence-backed risk calls
    when the model's judgment of a vault changes materially.
  </Card>
</CardGroup>

The consumer app at [atlasyield.club](https://atlasyield.club) is the live demonstration of
all three: you can read the scores, have the Engine propose a portfolio, and deploy into it
from an account you control — non-custodially, signing every transaction yourself.

Scoring has been live since **May 5, 2026**; verifiable public snapshots since
**July 8, 2026**.

## System overview

The score rates one vault at a time. The Engine composes scored vaults into a portfolio.
Execution moves the user's funds into that portfolio under hard safety rules. Monitoring
watches everything after the fact and feeds back into the score.

```
 On-chain + protocol data
          │
          ▼
 ┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
 │   Atlas Score    │ ──▶ │   Atlas Engine   │ ──▶ │    Execution     │
 │ 4 pillars,       │     │ eligibility →    │     │ user-signed,     │
 │ 16 factors,      │     │ mean-variance →  │     │ non-custodial    │
 │ 0–100 composite  │     │ policy caps      │     │ deposits         │
 └─────────────────┘     └─────────────────┘     └─────────────────┘
          │                                               │
          ▼                                               ▼
   Daily public snapshots                    Continuous monitoring,
   (git-stamped, ex-ante)                    risk calls, rebalancing
                                             calls (future)
```

<Card title="Read the Litepaper" icon="file-pdf" href="/litepaper">
  The full v1.0 litepaper — the Score, the Engine, asset-flow mechanics, and limitations —
  as a single document, with a downloadable PDF.
</Card>