> ## 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.

# Monitoring and calls

> Scoring does not stop at publication.

Scoring does not stop at publication. Every covered vault is re-scored continuously as
new data arrives, and the daily snapshot commits the full set to the
[public record](/score/public-record).

## Risk calls

When the model's judgment of a vault changes materially — a score cut on deteriorating
safety or sustainability — AtlasYield publishes a dated, narrated call with its evidence:
what was cut, when, why, and (over time) what happened next. A ratings brand is built on
calls, not dashboards, and the git-stamped history keeps the calls honest.

<Card title="Published risk calls" icon="bell" href="https://atlasyield.club/calls">
  Every call, dated and narrated, on the live site.
</Card>

## Rebalancing calls (future)

The same machinery points forward: when the Engine's optimal portfolio for a tier drifts
materially from a user's held portfolio — because scores moved, yields decayed, or a
position was cut — Atlas will surface a *rebalancing call*: a concrete proposed set of
exits and entries, with the reasoning attached. Like everything else, a rebalancing call
is a proposal the user signs or ignores. Atlas will never rebalance autonomously; the
non-custody invariant is permanent.