Company · AI lab
An AI lab that shows its limits.
Alelyon is an AI lab. We are developing our own line of models and the infrastructure around them: a compute kit for expert training kernels, a chat workspace, the Lattice workspace for models and agents, and a verification pipeline with a public checker for applicable replay under independently obtained inputs and a public key pinned out of band.
Operating principles
How the work is held.
Each of these traces to a defect that shipped, or nearly shipped, in this codebase. None of them is aspirational.
- 01
Availability is not correctness
A caught exception, a non-empty dataframe, a bound port, or an HTTP 200 is not evidence that a result is right. Every one of those has stood in for correctness in a system somebody trusted.
- 02
Refusal is a valid outcome
A system that always returns a number is not more capable than one that declines — it is less honest about the same uncertainty. Refusals carry their real reason and are treated as first-class results.
- 03
An absent measurement says so
A blank beside a filled slot reads as "checked, fine". Unmeasured states are named in those words, because silently defaulting them to zero is how a gap becomes an assertion.
- 04
Name the boundary of every claim
Claims travel with their limits attached rather than in a footnote on another page. Anything that leaves the do-not-say list does so through a recorded adversarial review with sources.
- 05
Keep the negative results
Retreats, refuted claims, and abandoned directions stay in the record beside the wins. Rewriting history to make the current direction look inevitable destroys the only evidence of judgement.
- 06
The decision stays with the owner of the risk
Alelyon builds instruments. It does not manage capital, does not advise on it, and does not position software output as a recommendation.
Position
Software, not stewardship.
Alelyon sells software and research infrastructure. It does not manage client money, does not offer personalised investment advice, and is not a registered investment adviser, broker-dealer, or futures commission merchant.
That boundary is architectural, not just legal. Opening Lattice starts no trading engine or control socket and exposes no capital-bearing control; every analytical tool it can reach is read-only. Its coding-agent surface can start a child process only after visible user action. Execution engines exist elsewhere as separate processes, and nothing offered here starts them.
The verification work follows the same instinct. The component that checks a certificate is public and separately installable; the component that computes one is operated. The checker replays scalar and other applicable checks with inputs the recipient supplies and a key pinned out of band. A substrate-sensitive nonzero width may remain explicitly unverified. Replay does not settle whether the data was honest when captured or remove the need to assess the producer; those limits are stated rather than papered over.
Contact operations.
Product, partnership, and technical enquiries reach a mailbox that is read. Access itself waits on nobody — the build downloads freely, and hosted DQC-OS keys are issued automatically to signed-in, LinkedIn-verified accounts — so this route is for the questions a page cannot answer. No response time is promised until one can be kept.
Contact the lab