Skip to content

LAYA typed-decisions

Convai InnovationsOpen weights

The English LAYA checkpoint fine-tuned on the typed-decisions suite. In-domain on that suite by construction; the number to read is how far a fine-tune closes the gap to Jev.

Not a zero-shot row on typed-decisions: the workflow names match its training data.

typed-decisions
0.714
18/20 over baseline
Metatext suite
0.475
3/7 over baseline
ECE untuned
0.161
→ 0.016 held-out fitted
p50 per case
375 ms
four CPU cores

Specifications

Checkpoint
convaiinnovations/laya-typed-decisions
Publisher
Convai Innovations
Mechanism
Encoder with a decision head (System One)
Backbone
ModernBERT-large + decision head, fine-tuned on typed-decisions
Parameters
421M
License
Apache 2.0
Runs as
open weights, self-hosted
Library
laya
Primitives
Choice, Score, Noul
Pricing
none — your compute

Metatext decisionsrank 16 of 21

Full leaderboard →
Per-question accuracy — default payload, systemone mode, 120 judgments
TaskQuestionTypeAccuracyBaselineBeats?
agent_tracesoutcomechoice0.2140.357❌
agent_tracesneeds_humannoul0.3570.714❌
customer_servicedepartmentchoice0.8500.400✅
customer_servicerefund_requestednoul0.8500.700✅
customer_servicefrustrationscore0.4000.500❌
security_incidentsseveritychoice0.4380.312✅
security_incidentsactively_exploitednoul0.4380.688❌

typed-decisionsrank 2 of 9

Full leaderboard →
Per-question accuracy — default payload, systemone mode, 2,000 judgments
TaskQuestionTypeAccuracyBaselineBeats?
td_agent_trace_observabilityactionchoice0.7000.360✅
td_agent_trace_observabilityneeds_reviewnoul0.8400.550✅
td_agent_trace_observabilityoutcomechoice0.6500.500✅
td_agent_trace_observabilityriskscore0.6000.340✅
td_agent_trace_observabilityurgencyscore0.4500.370✅
td_customer_serviceactionchoice0.5800.520✅
td_customer_servicecategorychoice0.9400.380✅
td_customer_servicechurn_riskscore0.7800.470✅
td_customer_serviceneeds_humannoul0.7600.670✅
td_customer_serviceurgencyscore0.6700.420✅
td_invoice_processingdiscrepancy_severityscore0.4000.470❌
td_invoice_processingdispositionchoice0.8000.450✅
td_invoice_processingduplicatenoul0.9200.890✅
td_invoice_processingmatches_ordernoul0.9400.540✅
td_invoice_processingurgencyscore0.6100.510✅
td_security_incidentscredential_compromisenoul0.8100.550✅
td_security_incidentsdispositionchoice0.7300.740❌
td_security_incidentsseverityscore0.6700.490✅
td_security_incidentstrue_positivenoul0.8700.730✅
td_security_incidentsurgencyscore0.5600.500✅

Fitted temperature per primitive (fold 0, judged on fold 1): choice 0.3, score 0.4, noul 0.3 — ECE 0.155 → 0.016, accuracy → 0.762.

Published numbers

Reported by the authors or by third parties, on their own suites. Not comparable to the leaderboard above; attributed so you can check them.

Third partyLuni

laya-jev-benchmark

Measured on: PhishNChips (2,000 emails) and typed-decisions

typed-decisions
0.767 (ECE 0.212) vs Jev 0.727 (ECE 0.144)

Third-party scripts; the Jev rows are quoted from elsewhere, not measured here.

Model cardConvai Innovations

LAYA typed-decisions model card

Measured on: typed-decisions test split (400 cases, 2,000 decisions)

Accuracy / ECE / score MAE
0.766 / 0.213 / 0.242

Author-reported; the Jev row is quoted as "published", not measured by them. Trained on the suite's own train split.

Frequently asked questions

How does LAYA typed-decisions compare to Jev?

On typed-decisions LAYA typed-decisions scores 0.714 against Jev's 0.726, beating the majority baseline on 18 of 20 questions (Jev: 18/20).

Is LAYA typed-decisions open source?

Yes. convaiinnovations/laya-typed-decisions is released under Apache 2.0 and runs on your own hardware with the laya library.

Can LAYA typed-decisions extract entities?

No. LAYA typed-decisions answers questions about text and never returns spans; use a GLiNER-family model for extraction.