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

# Platform model

> Understand tenant scope, immutable scoring science, programs, and evaluation results.

# Tenant scope and immutable science

Every request is bound to an organization, app, and environment. Every result
is bound to immutable definition versions.

## Tenant hierarchy

<CardGroup cols={2}>
  <Card title="Organization" icon="building">
    The company and membership boundary. Roles include owner, admin, builder,
    developer, analyst, and viewer.
  </Card>

  <Card title="App" icon="cube">
    One product or use case, such as Savart EFG or a customer onboarding
    journey. Scores are meaningful only inside their app.
  </Card>

  <Card title="Environment" icon="layer-group">
    Every app has isolated test and live environments with separate subjects,
    keys, programs, webhooks, quotas, and analytics.
  </Card>

  <Card title="Subject" icon="user">
    Your app's end user. The public ID is opaque; external identifiers and PII
    live in a separate encrypted identity vault.
  </Card>
</CardGroup>

<Tip>
  Scope comes from the credential. Never accept organization, app, or
  environment scope from an untrusted browser and pair it with a broad key. The
  environment key or human session is authoritative.
</Tip>

## From definitions to results

| Stage          | What it represents                                                     |
| -------------- | ---------------------------------------------------------------------- |
| Definitions    | Experience, scorecard, context, guardrail, adaptive policy, and report |
| Version bundle | Immutable references to the exact six definition versions              |
| Program        | One-time or recurring deployment in an environment                     |
| Evaluation     | One subject's pinned evidence and scoring cycle                        |
| Result         | Primary result, axes, alignment, trace, coverage, and confidence       |

## Lifecycle rules

* Definitions move through `draft → validated → published → deprecated → archived`.
* Published versions never mutate; edit by creating a new draft revision.
* Live environments begin in managed review and accept mutations only after
  platform approval.
* Hard guardrails stay authoritative. An LLM cannot improvise questions or
  change scoring during an evaluation.
* Context precedence is organization → app → program → subject/session, and
  every merged fingerprint is stored with the result.

## Credential roles

Human owners and admins publish science and activate programs.
`admin`/`ops` environment keys run trusted server integrations.
`ingest` keys are restricted to subject import and continuous-evaluation host
writes. Participant and report tokens grant access to exactly one public
journey or report.