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

# Glossary

> Definitions of the terms used across Solya.

<ResponseField name="Organization (tenant)">
  Your isolated workspace. All entities — plans, rules, alerts, data — are scoped to
  one organization. Users can belong to more than one and switch between them.
</ResponseField>

<ResponseField name="Data source">
  A system or channel Solya ingests data from: a POS system (Polaris, Kezia), an API,
  or manual file uploads.
</ResponseField>

<ResponseField name="Ingestion spec">
  The contract describing how to detect, parse and transform an incoming file into
  Solya's standard data model.
</ResponseField>

<ResponseField name="Ingestion run">
  A single execution of the ingestion pipeline, with a status and full logs.
</ResponseField>

<ResponseField name="Gold / silver layer">
  The analytics tables (hosted on Databricks) that power dashboards, KPIs, forecasts
  and alerts. Silver is cleaned/normalized data; gold is business-ready analytics.
</ResponseField>

<ResponseField name="Plan">
  A unit of inventory work. Six types exist: restock, rebalance, markdown, pre-season,
  supplier return, and supplier exchange.
</ResponseField>

<ResponseField name="Plan item">
  A line within a plan (typically a variant × size, sometimes × shop). Items carry
  their own status (To review / Ready for order).
</ResponseField>

<ResponseField name="Ruleset / business rule">
  A business rule is a constraint evaluated before a plan action. A ruleset groups
  rules; one ruleset is the organization default.
</ResponseField>

<ResponseField name="Enforcement mode">
  What a rule does when triggered: **Block** (prevents the action), **Warn** (allows
  it with a warning), or **Log** (records it silently).
</ResponseField>

<ResponseField name="Approval policy / approval">
  A policy that reroutes a plan to an approval request when its value exceeds a
  threshold. An approval is the resulting Pending/Approved/Rejected/Expired record.
</ResponseField>

<ResponseField name="Budget envelope (OTB)">
  An Open-To-Buy spending limit for a period, scoped globally or by brand, department,
  or collection. Plans are checked against live consumption.
</ResponseField>

<ResponseField name="Size curve">
  An expected size mix (e.g. S 20%, M 35%…) a plan should align with.
</ResponseField>

<ResponseField name="Alert">
  A monitored condition (metric + operator + threshold over a perimeter) that raises
  an instance when breached.
</ResponseField>

<ResponseField name="Tag / tagging rule">
  A label on an entity. Tagging rules apply or remove tags automatically based on
  metrics or column values.
</ResponseField>

<ResponseField name="Workflow / workflow run">
  An automation (trigger + actions) executed by the data platform. A run is one
  execution, with per-step records.
</ResponseField>

<ResponseField name="Decision vector">
  AI-computed scores per variant/shop (restock urgency, stockout/overstock risk,
  transfer urgency…) that measure how risky or urgent a position is. See the
  [decision layer reference](/en/developers/decision-layer/overview).
</ResponseField>

<ResponseField name="Action vector">
  The resolved recommendation derived from a decision vector — a concrete quantity to
  reorder, units to transfer, or a discount percentage, with a confidence and an
  explanation. What the app pre-fills and acts on.
</ResponseField>

<ResponseField name="Audit log / activity">
  The immutable trail of every plan change — who did what, when, why, and which rules
  applied.
</ResponseField>

<ResponseField name="Service-account token">
  An API token (`solya_sa_…`) used by external programs and agents to call the Solya
  API on behalf of an organization. See [Authentication](/en/developers/authentication).
</ResponseField>