Syntaxe — a deep-tech research lab

Syntaxe is a private research lab turning dead artifacts into living understanding through real mathematics — reasoning engines for truth, justice, memory and craft, with proof rather than heuristics.

Reach the lab at hello@syntaxeltd.com · Syntaxe Ltd.

move — it knows you're here
Syntaxe Ltd  ·  Building advanced computational systems for complex domains
Syntaxe Ltd · the lab

Not a startup.
A research lab.

We turn dead artifacts into living understanding through real mathematics. The world's meaning is locked inside things no living person fully understands anymore — old systems, frozen photographs, the law, the scientific record, a human mind. We build reasoning engines that make them legible and alive again, with proof rather than heuristics.

the thesis

Meaning is locked. We build the key.

Every engine takes something the world had given up on understanding and makes it reason for itself again — checkably, from primary sources, showing its work. Where the field ships a plausible guess, we ship a result you can verify. The output is not an opinion. It is a line of reasoning you can follow to its source.

the depth

Many engines. These are ready to meet the world.

A lab of many. The ones that wait in the Well are ready for daylight — each its own discipline, each already real. Behind them the work runs deeper than any one page should say.

Verity
integrity engine — defend what is true
Awatum
legal core — justice, for everyone
Kern
containment core — contained, and proven
Anneal
hardening engine — hardened under fire
Codec
genomic engine — the genome, computed
why now

Reasoning is finally rigorous enough to do this for real.

For the first time, reasoning systems are precise enough to take on the world's hardest, oldest meaning and not merely paraphrase it. The moat is not the model — every lab has the model. The moat is the mathematics underneath each engine, and the depth of the bench behind them.

what we hold to

The lines we don't cross.

Proof over heuristics
We do not ship a confident guess. Every claim an engine makes traces to a source you can check — or it tells you, plainly, that it does not know.
A line each engine won't cross
Each engine names the thing it will not do — accuse, diagnose, replace the human judgment that has to stay human. The instrument points; the person decides.
Built to outlast its makers
We build the way you build an heirloom, not a quarter. The work is meant to still be reasoning correctly long after we are gone.
This is a long game. The engines reveal themselves slowly, and on their own terms. If the work is for you, there is a quiet way to reach the lab.
syntaxe ltd · a research lab
Syntaxe Ltd · work

We hire rarely,
and deeply.

The lab grows by a person at a time. We look for minds that want to build things that outlast them — people who prefer proof to opinion, who would rather be right and slow than fast and plausible, who are drawn to the hardest problems because they remain unsolved.

If that is you, do not send a résumé. Send us the thing you would build, and why no one has built it yet.

Tell us what you'd build →
Syntaxe Ltd · contact

Reach the lab.

Syntaxe Ltd · investors

The reasoning layer
for the world's locked-up meaning.

A research lab building the engines that turn dead artifacts into living understanding — with proof, not heuristics. A long game, and a deep one.

Syntaxe Ltd · archive

Not a blog.
An archive.

Notes, observations and field reports from inside the lab — the thinking as it happens, kept as it was written. An evolving body of work, not a feed.

Fragment 2026 · 05
The well and the lonely edge

We all drink from the same well. Given the same inputs, capable minds converge on the same ideas — which is why the idea is rarely the moat. Value is what is not in the well: a position, a dataset, a proof only you can generate. Novelty doesn't live in the water. It lives at the edges no one else is standing on.

Field Report 001 2026 · 06
The builder cannot grade its own novelty

We turned an independent adversary loose on our own best ideas — a dozen of them, across a dozen domains. Every one cleared its own gate; the outside check killed or sketched all twelve, almost always on prior art the builder couldn't see from inside the well. The lesson was cheap and total: enthusiasm is not evidence. A thing is novel only when someone who wants it to fail can't.

Note 003 2026 · 06
A proof beats a promise

Every guard in the agentic-security market ships an alarm — a probabilistic flag that something looks wrong. We ship a proof: a certificate an outsider can re-derive in an air-gapped room, trusting no one but the math. The whole product is the distance between "we checked it" and "check it yourself."

Paper 2026 · 06
AI Accountability in the ACTA Ledger

When an autonomous agent acts, who is accountable? Not the prompt, not the model — the verified outcome. A signed attestation written at the moment of execution and anchored where no one can rewrite it. Accountability as a primitive, not an afterthought.

Note 002 2026 · 05
The most important systems are often indirect

The systems that move the world rarely announce themselves — double-entry bookkeeping, the handshake beneath every connection, the ledger no one reads until it is the only thing that matters. We build for the indirect: the substrate beneath the thing you actually see.

Note 001 2026 · 05
Human → Agent → System

For thirty years we designed for the human at the keyboard. That human is becoming the one who delegates. The chain is no longer human → software; it is human → agent → system. The design question stops being "is it usable" and becomes "is it containable."

more, as the work accrues
subsystem online · syntaxe reasoning core
← back
SYX·VRT · syntaxe reasoning core
VERITY
defend what is true
subsystem online · integrity engine
enter ↓
the compiler for science · a live read
“Compound X reduces tumour growth by 40% (p < 0.01).”
illustrative manuscript · reading every claim
an integrity profile — not a verdict. Verity flags signals for expert review; it does not accuse.
scroll — the methods, and why it matters ↓
the stakes
10,000+

papers retracted a year — and the curve is steepening.

A reviewer gets two to four hours per paper — no time to re-derive every statistic, trace every citation, or inspect figures at the pixel level. Verity does that pass in under a minute and hands back a map of exactly what to examine. The hours they never had, spent where they matter.

the methods

Six layers. Every one a published method.

Statistical
GRIM · SPRITE · p-curve
Recomputes whether reported means, SDs and test statistics are even achievable at the stated N.Brown & Heathers, 2017
Image
copy-move · splice · clone
Pixel-level duplication, splicing and gel-band manipulation, via ELA and PRNU analysis.
Reference
citation forensics
Citation rings, retracted-source references and phantom citations, with DOI verification.
Text
paper-mill fingerprints
Tortured phrases and synthetic-text markers characteristic of paper mills.Cabanac & Labbé
Methodology
power & reproducibility
Sample-size adequacy, protocol consistency and reproducibility signals — surfaced, never judged.
Data
internal consistency
Cross-validation of tables, figures and reported numbers against one another.
how we validate

Every finding carries its method, evidence, and confidence.

No black-box "accuracy" score. We report precision and false-positive rate per layer — the numbers that decide whether a tool is safe to point at a colleague's work — validated against the Retraction Watch corpus of documented retractions. Every signal links to the method that raised it. And when the evidence is insufficient, Verity says so: "unverifiable" is a first-class result. (Operating characteristics published as the corpus is processed — we won't quote a number we can't show.)

the line we don't cross

Verity flags. A human decides.

It does not replace peer review, and it never makes a finding of misconduct. Every output is a signal — its evidence shown — handed to an editor or integrity officer to adjudicate. The instrument points; the scientist judges.

who it's for

Journal editors screening before publication. Integrity offices triaging allegations. Funding agencies verifying the work they pay for. Reviewers who want their hours spent where they matter.

Evidence, not verdicts.

A compiler for science — it doesn't accuse you of error. It points to the line and says: look here.

Request a demo →
verity · a syntaxe reasoning engine
Request a demo →
SYX·AWT · syntaxe reasoning core
AWATUM
justice, for everyone
subsystem online · legal core
enter ↓
watch it reason

A few plain words in. A reasoned case out.

a real situation · in plain words
The issue, identified
Tenancy deposit protection — your landlord's statutory duty, and whether it was met.
The law, cited
Your deposit had to be protected in an approved scheme within 30 days. It wasn't.Housing Act 2004 · s.213Hashmi v Gladhart [2011] EWCA Civ 1411✓ every word checked against primary law — nothing invented
The other side, pre-empted
The landlord will claim "fair wear and tear." Your dated check-in / check-out photos rebut it.
Your position
You may recover the deposit plus 1–3× as a penalty — up to £5,400. Letter before action drafted.
case strength
78%
Awatum is not a law firm. It shows you the law in plain words and what to do next — and points you to a solicitor when you need one.
scroll ↓
the crisis
5.1bn

people have no real access to justice.

Eighty-five percent of people with a civil legal problem get no professional help. The system exists — but only for those who can afford it. The law is written for solicitors. Awatum rewrites it for humans.

the difference

Most legal AI searches. Awatum reasons.

a chatbot

Finds documents containing the word "negligence," summarises them — and can confidently cite a case that does not exist.

awatum

Decomposes negligence into its legal elements — duty, breach, causation, damage — scores each against your facts, computes the odds, and models what the other side will argue. Every step inspectable.

justice with certainty

It cannot make up the law.

Every claim Awatum makes carries citations to primary authority — the actual statute, the actual judgment. Any sentence whose citation isn't in the verified source is dropped before it ever reaches you. Where others guess, Awatum shows its work — or tells you, plainly, that it doesn't know.

the legal life graph

Not a chat that forgets. A memory that grows.

Every person has a living map of their legal existence — the people, the contracts, the rights accruing, the deadlines approaching. Every conversation enriches it; every engine reads from it. Awatum doesn't answer a question and forget you — it holds your whole situation, and watches it over time.

the shadow

The other side's best argument — before they make it.

After every new fact, Awatum quietly runs the opposing case against you: the strongest attack, the weakest joint in your position, the three moves a sharp opponent would try. You never walk in unprepared.

drift

The law changes. You know in two seconds.

When a statute is amended, every case it touches re-reasons automatically — and the people affected see their position move in about two seconds. You are never quietly out of date.

twenty-eight engines

One mind. Four kinds of power.

🛡
Shield
Catch the harm before it lands — unread clauses, missed rights, deadlines you didn't know you had.
Sword
When you must fight: strategy, precedent, the document drafted, the opponent modelled.
Map
See the landscape — simulate ten thousand outcomes, read the judge, know the odds before you act.
Bridge
Cross every border — jurisdictions, languages, and the gap between human worry and formal law.
see it

A complete legal mind, in your hand.

Start with a few plain words. Watch it reason — citing real law, weighing the odds, tracking every deadline — and hold your whole legal life in one place.

with dignity

It simplifies the languagenever the respect.

Awatum meets you where you are — your situation, your language, the urgency in your voice — and never questions your intelligence. It says "you have the right to," not "you should have known." End-to-end encrypted. It never trains on your case. Your data is never sold.

the line it won't cross

It informs. It never pretends to be your lawyer.

Awatum makes the law legible and your options clear — and tells you, plainly, when you need a solicitor, then helps you find one. You stay in control of your own case.

who it's for

The tenant whose deposit vanished. The worker fired without notice. The parent in a custody fight. The migrant facing a system in a language not their own. Anyone the law was meant to protect — and didn't, until now.

A complete legal mind. For everyone.

Not when you can afford it. Not when you find the right lawyer. Now — in words you understand.

Request early access →
awatum · a syntaxe reasoning engine
Request early access →
SYX·KRN · syntaxe reasoning core
KERN
contained, and proven
subsystem online · containment core
enter ↓
watch it contain a mesh

An AI agent that cannot leak your data. Proven — not hoped.

an agent mesh · compiled to a runtime monitor + a re-checkable proof · a leak attempt, caught at the boundary
why it exists

Every other guard ships an alarm. KERN ships a proof.

The whole agentic-security market — the funded names included — watches your AI agents and raises a probabilistic flag when something looks wrong. KERN takes the agent mesh's declared tools and data labels and proves it cannot route protected data to an undeclared sink, or exceed its authority, for any input or prompt injection — or it hands you the exact path that can.

how it works

Declare. Compile. Prove. Certify.

01 — Declare
Tools & labels
Point KERN at the mesh: its agents, the tools they hold, where sensitive data lives, and who's allowed to delegate to whom. A tiny, total policy — no escape hatch.
02 — Compile
A finite world
The bounded action-space lowers to a finite containment system — every flow an edge, worst-case wiring assumed. That finiteness is what makes "for all inputs" decidable.
03 — Prove
Non-interference
A monotone fixpoint settles the question: can a protected label ever reach a forbidden sink? Contained — or a concrete counter-example path you can read.
04 — Certify
A portable proof
Out comes a runtime monitor that enforces the verdict, and a certificate an outsider can re-check offline — trusting no one but the math.
the certificate

Trust no one. Re-run the math.

KERN's proof carries no signature on purpose. A signature lets a vendor assert safety; KERN lets an insurer, an auditor, or a counterparty agent re-derive it — in an air-gapped room, depending on nothing KERN controls. Trust comes from re-running the proof, not from believing the prover.

$ kern verify ./mesh.cert lattice ……… re-derived from cert tables ok non-interference … no protected→sink path CONTAINED value obligation … amount ≤ position ∀ inputs UNSAT of ¬obligation → holds ────────────────────────────────────────────── verdict: CONTAINED · re-checked offline, trusting no one
the value layer · first room: on-chain agents

Not just "no leak." amount ≤ position.

For agents that move money, "don't leak" isn't enough. KERN's value predicates prove the arithmetic too — that a keeper agent can never withdraw more than a position holds, for every input — the Certora-shaped guarantee, discharged as a proof rather than a fuzzing campaign that merely failed to find a bug.

the line it won't cross

It proves what it can. And says plainly what it can't.

KERN does not bluff. Its guarantee holds over the declared, bounded mesh — not over code it never saw. Multi-step running invariants and live on-chain label capture are named, on the roadmap, and honest about their status. A proof that overclaims is worse than an alarm; KERN would rather show you its edge than hide it.

who it's for

The team shipping autonomous agents into production who need more than a dashboard's good feeling. The insurer underwriting an agent and pricing real, re-checkable risk. The auditor and the counterparty who must trust an agent they didn't build — and now can, because the proof re-runs in their hands.

Containment you can re-check.

Request access →
kern · a syntaxe reasoning engine
Request access →
SYX·ANL · syntaxe reasoning core
ANNEAL
hardened under fire
subsystem online · hardening engine
enter ↓
watch it harden an estate

It attacks you on a loop — so no one else's attack lands.

an estate · continuously red-teamed · the reachable path found, sealed, and re-proven closed
why now · the threshold
181

working exploits one model found in a single browser. The generation before it found two.

That discontinuity is the whole reason ANNEAL exists. Frontier models now find and chain real vulnerabilities at a level that used to take a specialist — and over 99% of what they find is unpatched the day it's found. Finding was never the bottleneck. Closing, faster than an attacker who now moves at machine speed, is the game.

the difference

A scanner ranks by CVSS. ANNEAL ranks by what reaches you.

a scanner

Sorts thousands of findings by a static severity that knows nothing about your estate — most of them unreachable — and leaves the fixing, and the risk, to you.

anneal

Scores each exposure by an Attacker Priority Score — exploitability, dormancy, blast radius, reach, and chain position — surfaces the few paths that reach a crown jewel, and closes them behind a health-gate.

how it works

One loop. Sense. Score. Hunt. Close.

Sense
behavioral dormancy
Read-only connectors watch what assets actually do. TORPOR flags the behaviours that mean an attacker is present — a dormant box waking, a key never rotated, the quiet ones touched first.
Score
attacker priority, not CVSS
A weighted geometric mean of exploitability, dormancy, blast and surface, lifted by a finding's betweenness in the attack graph. Every component stored, every score re-derivable.
Hunt
autonomous red-team
An LLM red-team works each high-priority asset — and the chains between them — in an isolated, network-less container. A finding counts only if an exploit script reproduces it.
Close
patch · virtual patch · isolate
Container-tested, canary → pilot → full, health-gated with auto-rollback and a 48-hour behavioural watch after. ANNEAL never writes to your estate without your approval.
torpor · the tell

Attackers move differently than you do. TORPOR reads the difference.

first_pick
the quiet one, first
A dormant asset touched while ≥70% of its neighbours stay untouched — the signature of picking the forgotten system before the watched ones.
stillness_break
awake after silence
A service untouched for 14+ days suddenly active — reactivation, or reconnaissance on something everyone forgot.
rotation_breach
a key never turned
A credential unrotated past 90 days on a high-blast asset — a stale, silent surface waiting to be used.
wake_on_crisis
three at once
Three or more dormant assets waking inside an hour — the shape of lateral movement through the segments no one monitors.
no black-box score

Every number, re-derivable.

ANNEAL's priority isn't a vendor's opinion. Each exposure stores all five components and the chain multiplier — so an auditor can re-compute the 0.91 by hand, and a closed path carries a record anyone can re-check.

$ anneal score prod-api-gateway → payments-db epss ………… 0.97 CISA KEV → pinned to 1.0 dormancy …… 0.61 first_pick fired · 14:23 UTC blast ……… 0.84 reaches payments-db (0.97) surface …… 0.90 internet-facing entry chain ……… ×1.30 betweenness · 3 shortest paths ────────────────────────────────────────────── APS: 0.91 window 14h every term stored, re-checkable
see it

One screen. The whole race.

Everything above, on one console: the highest-reachable path scored 0.91, the hunts running now, the CLOSE pipeline staging fixes — and the live SENSE feed where TORPOR catches the behaviours that mean an attacker is already inside. Velocity 1.34 — closing faster than they arrive.

the line it won't cross

Read-only by design. It never touches your estate without you.

Connectors are read-only; hunts run against snapshots, never your live systems — and no patch reaches production without an operator's approval. It also refuses to drown you: four alerts fire, not forty — a new CISA-KEV match, velocity slipping below 0.8, a validated critical finding, a deploy that landed or failed. A tool that cries wolf is a tool you switch off.

who it's for

The team drowning in findings it can't fix fast enough, that needs the path that matters closed — not a longer list. The CISO who has to answer "are we actually harder than last week" with a number that re-checks. The insurer pricing an estate's real, moving risk.

A fix you can prove held.

Request access →
anneal · a syntaxe reasoning engine
Request access →
SYX·CDC · syntaxe reasoning core
CODEC
the genome, computed
subsystem online · genomic engine
enter ↓
watch the program settle

The genome isn't a text to read. It's a program that runs.

regulatory dynamics · the same code settling into its stable states — the cell identities it can hold
why it exists

The most-sequenced program on Earth — and we still read it as text.

Twenty thousand genes, twenty-eight million methylation sites, one program — running right now in every one of your 37 trillion cells. We have billions of genomes on disk and almost no account of what the program does. CODEC treats regulatory interaction as a vector field over gene-expression state and computes its structure — on real dynamical-systems mathematics, not metaphor.

what the math says
384

stable identities the same code can hold. Counted, not catalogued.

A cell type is a reflexive fixed point — a state where the genome's own dynamics come to rest. Morse-type inequalities bound how many such rests the program admits — #stable ≥ 1 + b₁ — and the structure resolves to 384, spread across eight body systems, the nervous system alone holding 86. Not a list someone wrote down; a count the topology forces.

the difference

A browser reads the letters. CODEC runs the program.

a genome browser

Shows you the sequence — three billion letters, the genes, the variants — as a static text to be searched and annotated.

codec

Treats that sequence as a running dynamical system, solves for the stable states it settles into, and maps the routes between them — the genome's behaviour, computed.

how it works

Read. Model. Settle. Map.

Read
a reflexion field
The regulatory network — who activates and represses whom — becomes a map ρ that hands every expression state the vector field the genome would impose on itself there.
Model
dynamics, not metaphor
Each state flows where the network pushes it, across a 47-dimensional manifold. A numerical system you integrate — not a story, a solver.
Settle
reflexive fixed points
Solve ρ(s)(s)=0 by damped Newton, then classify each rest by its Jacobian eigenvalues — stable (a cell type), saddle (a transition), or unstable.
Map
basins & filtration
Chart the basin of each identity and the 14-level filtration of possibility — the commitments that, one by one, close the doors a cell can still walk through.
the readout

It computes structure. And shows its work.

CODEC's output is a re-checkable computational readout — the stable states it found, their basins, the routes between them — derived from a model you can inspect, not asserted. Every number traces back to the dynamics that produced it.

$ codec solve ./regulatory.model manifold …… 47-dim · kernel rank 300 built fixed points … reflexive states located 384 stability …… Jacobian eigenvalues classified filtration … 14 levels · basins charted resolved ────────────────────────────────────────────── readout: computational · every value re-derivable from the model
see it

The program, made visible.

The same dynamics, on screen: your 384 stable identities across eight systems, the regulatory circuits that hold a cell's program in place, and the filtration of possibility — every commitment a door that closes behind you.

the line it won't cross

It is a research instrument. It is not a medical device.

CODEC computes structure in the genome's dynamics — nothing more. It does not diagnose, predict disease, or advise treatment, and it makes no clinical claim about any individual. It is a lens for researchers studying how regulatory programs behave. Where the model's assumptions end, CODEC says so — and stops.

who it's for

The computational biologist who wants the genome's dynamics as a solvable system, not a spreadsheet of reads. The systems-biology lab studying cell-state stability and reprogramming. The researcher who needs every number to trace back to a model they can interrogate.

The genome, as a system you can solve.

Request access →
codec · a syntaxe reasoning engine
Request access →