BEDIM SECURITY

Laya × discrete mathematics.

A measured capability study: what a decision model can honestly do around discrete mathematics — and what a deterministic engine does instead. Six suites, seven runnable tutorials, a fine-tune dataset kit, and every run recorded.

The capability study.

What the shipped checkpoints do zero-shot around discrete mathematics, measured against a live decision server on 2026-10-12 — and what the deterministic engine answers instead, exactly, offline. The pattern that ships: the model routes, tags, and gates; the engine computes, proves, and answers.

0.875domain-routing accuracy
80probe calls, sequential
0.25numeric quiz = exact chance
1.000engine verdicts, always
SuiteNDecision modelThe system answer
Domain routing (choice)240.875dispatch the routed engine; escalate on humility
Formula verdicts (noul)160.688 directtau gate → engine; 0.688 → 0.938 gated in the probe framing — and 0.375 direct under a one-line-different state template (prompt-sensitivity is real)
Formalization check (noul)100.700confident misses on subtle quantifier/implication swaps; counterexamples adjudicate
Graph properties (noul)8×20.750 / 0.250BFS + 2-coloring: 1.000, microseconds, offline
Answer audit (noul)100.600 (mixed) / 0.400 (worded)systematically nay-biased — a filter a human reads, never a verdict
Numeric quiz (choice×4)120.250 = exact chancecompute first, ask later; the model grades the learner
The honest limits: a decision model never generates text — it cannot write a proof, an explanation, or code. Numbers are not magnitudes to it (the numeric quiz landed at exact chance while honestly reporting low confidence). The tau gate catches indecision, never confident error. Answer-validity audits skew “no”. So: the engine stays the calculator and the court of record; the model does the language-side triage where it measured strongest — routing and learner tagging — and every deployment threshold is picked from a measured baseline, not hoped into place. Latency over 80 sequential calls: median 295 ms, p95 518 ms on CPU.

Where everything lives.

Contact

For contracting and capability inquiries:

Get the daily briefing — email us with subject “briefing”, or read the latest issue.