how saya works

Overview

SAYA is a small reflex attached to one coin. Each swap becomes a compact state. Laya reads it locally and returns one allowed action.

pool
  ↓
swap event
  ↓
state builder
  ↓
laya / local
  ↓
reflex
  ↓
KEEP / SHIELD / RETURN / CUT

The trade

A read begins with an observed buy or sell. The record keeps size, price, wallet when available, time and slot. One trade creates one read.

State

side is buy or sell. trade size is the observed value. pool depth is available liquidity. recent flow compares buys and sells. wallet behavior describes recent observed activity from the same address. concentration estimates supply clustering. volatility describes recent price movement. current reserve is retained fee accounting. recent decisions are the immediately preceding typed answers.

Laya

Laya is an open-weight typed-decision model. SAYA uses it locally for constrained choices rather than generated prose. Laya is the model inside SAYA, not the project brand. No partnership or endorsement is implied.

Reflex

The question is narrow: what should this fee do? The valid response is exactly one of KEEP, SHIELD, RETURN or CUT. A confidence score and latency accompany the answer.

Keep

KEEP holds the observed fee in SAYA's reserve for a later read.

Shield

SHIELD directs the fee toward liquidity support. Before execution is connected, this is modeled accounting only.

Return

RETURN directs the fee toward eligible holders. No recipient transfer is claimed without verifiable execution.

Cut

CUT directs the fee toward supply reduction. No burn is presented as completed without an actual onchain instruction.

Reserve

The reserve accumulates KEEP actions. The live record separately totals held, shielded, returned and cut amounts so one action is never confused with a percentage split.

Confidence

Confidence is the model score attached to the selected action. It is not a price forecast or promise of outcome.

Misses

A miss occurs when the state is incomplete, the runtime does not answer, or the output falls outside the four allowed actions. A miss produces no action.

Public record

Each record keeps the trade, compact input state, typed answer, confidence, latency and resulting reserve action. Reproducibility depends on keeping the exact input with the answer.

If saya stops

The current fee remains where it was. SAYA does not invent a fallback answer. The failed read is counted as a miss and the next swap can try again.

Accounts

The current site does not connect wallets, take custody, or claim transfers. Public wallet identifiers appear only where the market source exposes them. Copy and explorer actions do not imply control of an account.

Reading the numbers

SIM marks the sample record. awaiting runtime means a live market is configured but local model execution is not. A dash means the value is unavailable and has not been invented.