Alelyon / ResearchFindings, with their limits

Follow the question.
Inspect the evidence.

The reasoning behind the ecosystem: what we built, what remains open, and which claims did not survive review. Every note carries its scope and limitations with it.

Selected public notes, not a complete research inventory. A publication date is not a new experiment or an independent replication.

How to read this record

A result is useful when its scope is clear.

Start with the summary, read the “Does not establish” boundary, then follow the note’s sources. Implementation, a dated experiment, and third-party reproduction are different forms of evidence.

What the status labels mean
Shipped
Implemented in the scope described by the note.
Active
Under investigation; no settled result is implied.
Gated
A named prerequisite must be met before proceeding.
Retreat
A direction was set aside with a recorded reason.
Refuted
A proposed claim did not survive review.

Verification

Public notes
  • Shipped

    A certificate cannot authenticate a quantisation step by repeating its own claim

    A certificate that reports its own quantisation step can simply declare it to be zero. Signed transparency leaves make later revision detectable when a verifier retains or independently obtains the required leaves and checkpoints.

    Does not establish

    The current log, witness, and signing key are issuer-operated. Anchoring does not prove correct capture or prevent an undetected issuer fork when nobody outside the issuer retains the comparison evidence.

  • Refuted

    A twelve-domain expansion went to referees and came back overclaimed

    The recorded prior-art and buyer-side referee passes rejected a proposed twelve-domain expansion of the certified-number pipeline. Two domains survived as gated candidates; ten did not.

    Does not establish

    This records the verdict on the expansion, not a finding about the underlying method. The surviving domains remain gated behind platform prerequisites.

  • Shipped

    The receipt detects revision, not invention

    Replay compares supplied inputs with committed digests and re-executes the named program. A successful check can detect inconsistent evidence; it cannot establish that the producer captured truthful inputs.

    Does not establish

    Nothing here establishes that the underlying data is correct. Verification also requires inputs you obtained independently and a public key you pinned out of band.

Numerics

Public notes
  • Shipped

    The execution bound covers storage quantisation, and nothing wider

    The execution-bound path estimates variation from dither-quantised storage. Its tier scheme refuses unsupported programs; the error model and branch assumptions remain part of the claim.

    Does not establish

    It is a probabilistic order statistic over storage quantisation alone — not a guaranteed enclosure, and not coverage of rounding, truncation, or discretisation error.

Machine learning

Public notes
  • Shipped

    A restricted CNE program keeps the model from supplying the computed figure

    On the restricted CNE path, the model authors a program and an interpreter computes the result. The accepted DSL output therefore does not take its computed figure from model recall.

    Does not establish

    This applies only to the restricted CNE/DSL result. Lattice narration and open mode can contain model-origin estimates, and the constraint does not establish that the chosen program, inputs, or conclusion were correct.

Data engineering

Public notes
  • Shipped

    Point-in-time data needs the vintage, not only the observation date

    Revised macroeconomic observations can introduce knowledge unavailable at a historical decision date. A point-in-time query must identify the release vintage as well as the period being measured.

    Does not establish

    Vintage discipline removes one specific look-ahead channel. It does not make a backtest realistic on execution, liquidity, or transaction costs.

Read the longer argument

Public manuscripts

Author-published manuscripts in the open repository. These links are a reading list, not a claim of external peer review or independent reproduction. Read each manuscript’s assumptions and evidence record.

Use the ideas

Turn understanding into a careful integration.

The developer and agent handbook connects these findings to the public toolkit, replay workflow, and decision boundaries.

Open the handbook
Choose your beta

One build. Two tiers.

The Windows build downloads with no sign-in, no LinkedIn and no key. Which tier you are in is decided when the app signs in: without a beta key you run everything locally, and a key — issued automatically to a signed-in, LinkedIn-verified account — is what adds Alelyon’s hosted DQC-OS.

Open beta

Run the app without a beta key.

There is one build, and this is the same one the closed beta uses — the tiers differ at sign-in, not at download. Sign in without a beta key and you get the local tier: Terminal UI, Lattice workspace, local calculator, and visible tool traces. A beta key is what adds hosted DQC-OS issuance.

  • Local-first Windows interface
  • Open Alelyon toolkit and source
  • No hosted backend entitlement

Windows 10 / 11, 64-bit · 0.6.1

Closed beta

Verify identity with LinkedIn to unlock hosted DQC-OS.

LinkedIn OpenID Connect verifies control of the LinkedIn account; Alelyon does not scrape your profile. It records a verified access request, and when you verify from your signed-in account page, your hosted DQC-OS key is issued automatically— no review, no queue, nobody to wait for. It does not create or sign you into an Alelyon account, and an anonymous verification issues no key: the key needs a signed-in account to attach to.

  • Everything in the open beta
  • Hosted deterministic DQC-OS calculations, unlocked by your key
  • Signed envelopes and certified answer paths

Signing up uses Alelyon’s own email-and-password account flow, which is separate from LinkedIn verification below. One Alelyon account signs you in to every Alelyon application, and it keeps working until you delete it. Verifying with LinkedIn comes next and links that identity to this account.

Verify with LinkedIn

Verify from your signed-in account page and your hosted DQC-OS key is issued automatically — it appears on that page the moment verification completes. Copy it into a password manager and enter it when Alelyon Terminal asks during sign-in; if it expires, opening your account page issues a fresh one.

Available now

Ask, and a person reads it.

Prefer to talk to someone first, or need access sooner than the self-serve paths allow? Ask directly.

Nothing about access waits on a person. The build downloads with no sign-in and no key; a hosted DQC-OS key is issued automatically when a signed-in account verifies with LinkedIn, and it appears on that account’s page. This address is for everything else — questions, problems, deletion requests, and anything a page cannot answer. It is read by a person, so no response time is promised.

Do not include credentials, account numbers, API keys, or position data in the message.