Latest post
The authority boundary: what agents can and cannot do
An agent's authority belongs in a versioned record, not its prompt. See how Synedrix OS uses recommend, approve and execute scopes to bound what agents do.
ReadTip: select any text on this page to bring up the Ask tooltip and question the Synedrix OS assistant about it.
Definition
What Laya is
Laya, from Convai Innovations, is a System One decision model: give it a piece of text or data and a typed question (pick a label, give a score, yes or no) and it answers in a single pass, with a probability, without generating any text.
It ships as a Python package with open-weight checkpoints you run on your own hardware, an optional HTTP server built to speak the same request protocol as TypeSafe's Jev, and tooling to fine-tune a checkpoint on your own labelled decisions.
Context
What it is normally used for
How Laya is used generally, before Synedrix OS enters the picture.
- Routing: sending a ticket, alert or task to the right queue, agent or model
- Classification and scoring where a calibrated probability matters more than an explanation
- Gating: a cheap yes-or-no check before a more expensive step runs
In Synedrix OS
What it owns, and what it does not
Every platform in the stack has a non-overlapping responsibility. The boundary is as much a part of the design as the capability.
Owns
- Nothing in production: reachable only from LAB-003's isolated environment, on synthetic data, never from a registered agent
Does not own
- Whether any action is permitted
- → Policy Guard and the HITL Gateway; a decision model's confidence is evidence, never permission
- Committing durable memory
- → The Memory Curator, the only agent that commits memory
Rationale
Why Laya
It can run anywhere, air-gapped included
A decision model that only exists as someone else's API can never serve an air-gapped deployment. Laya runs on your own hardware, so it can serve every deployment mode Synedrix OS supports, air-gapped included.
Out-of-the-box quality is the open question
By its authors' own published comparison, the base model trails Jev until it is fine-tuned on decisions like the ones it will make. LAB-003 measures fine-tuned Laya against Jev on the same held-out decisions, with the bar for a tie written down before anything is scored.
Licensing
Licence position
LICENCE
Apache-2.0 (package). Confirmed from the laya package's own metadata on PyPI. Each model checkpoint carries its own licence on its Hugging Face model card, read before any checkpoint is kept. Source
Common questions
Laya questions, answered
Short, citable answers drawn from this page.
What role does Laya play in Synedrix OS?
Laya (Decision model, self-hosted) is mapped to Lab component: no OS layer in Synedrix OS. A model that makes bounded decisions without writing a word, and runs wherever Synedrix OS runs, air-gapped included.
What does Laya own in Synedrix OS?
Laya owns: Nothing in production: reachable only from LAB-003's isolated environment, on synthetic data, never from a registered agent.
The full reference page, with the operating model, deployment detail, and links to every canonical specification this platform touches, lives in the documentation repository, which is private while the platform is being built.
Latest post