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

Shipped

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.

A model fine-tuned to avoid inventing figures becomes less likely to invent one. Likelihood is the wrong currency when the output is a number someone will act on: a rare fabrication that carries the same confidence as a computed answer is difficult to distinguish without provenance.

The restricted CNE path moves the computed figure out of model recall. The model authors a program in a constrained domain-specific language, and a deterministic interpreter executes that program against the named data layer. Within that path, the figure returned by the DSL is the interpreter’s output and its provenance includes the program and inputs.

That language has no eval, no exec, no shell, no arbitrary imports, no dynamic attribute access, and no filesystem or network reach. These properties constrain what an accepted program can do; they do not make the program’s question, inputs, or interpretation correct.

Outside this restricted path, Lattice can narrate a tool result and can state a model-origin estimate. The visible trace distinguishes those estimates from tool-backed figures; it does not pretend the model can never write a number.

Where the model still earns its place

Routing a question, authoring the restricted program, and narrating a computed result in prose are all model tasks. On the restricted path, the model is not the source of the computed figure; it remains responsible for choices and narration that the interpreter does not validate.

A related evaluation result sharpened this. In a sealed assessment, a model handed a worked exemplar reproduced its structure on all 140 items — which reads as competence until the copied structure is separated from independently derived work. An evaluation that cannot distinguish those outcomes is measuring the exemplar, not the model.

Choose your beta

Choose the beta that fits your work.

Explore the local interface without identity verification, or use the LinkedIn-gated path when you need Alelyon’s hosted DQC-OS.

Open beta

Use the interface without identity verification.

No LinkedIn verification. Use the Terminal UI, Lattice workspace, local calculator, and visible tool traces. Hosted DQC-OS issuance is not included.

  • Local-first Windows interface
  • Open Alelyon toolkit and source
  • No hosted backend entitlement
Free UI build is being preparedOpen source toolkit
Closed beta

Verify with LinkedIn for full backend access.

LinkedIn OpenID Connect verifies control of the account; Alelyon does not scrape your profile. After verification and access policy succeed, the service can produce a unique key for the hosted DQC-OS path.

  • Everything in the open beta
  • Hosted deterministic DQC-OS calculations
  • Signed envelopes and certified answer paths

When the service opens, the key will be shown once. Save it somewhere secure, then enter it when Alelyon Terminal asks during sign-in.

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.

Requests to this address are read, and access is granted case by case while Alelyon is in closed beta. A public beta environment is planned and will use the same route; it is not open yet, and no response time is promised until it is.

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