Choose the boundary you need.
The two beta paths expose different capabilities and trust boundaries. Open beta is the local interface and public toolkit; it requires no LinkedIn account or access key and includes no hosted DQC-OS service. Closed beta is the hosted path, and LinkedIn verification for it is now live.
Pick an open or closed beta path.
- Open beta
Local UI and open toolkit
The public
alelyon-ostoolkit is what this path gives you today, and it needs no LinkedIn account and no beta key. The packaged Terminal and Lattice build is not distributed here.What this tier includes, however you obtain the build:
- Terminal UI, Lattice, the local calculator, and per-answer tool traces
- A local model server, or a cloud provider key you configure
- The separately published verifier, coordinate, compute-DAG, and API-client tools
- No hosted DQC-OS backend or hosted receipt issuance
UI downloads are not published yet.The installer and portable controls stay unavailable until both reviewed artifact URLs are configured. There is no email request or substitute download path.
Installer unavailablePortable unavailablePackaged previews enter through local account sign-in. That local account lives on the user's machine; it is not remote identity or a hosted-service entitlement.
- Closed beta
Hosted DQC-OS access
It is also the hosted path for authorised requests against an Alelyon-operated deterministic backend, and that half is not part of the open beta. LinkedIn verification is live; a hosted DQC-OS key still requires an operator decision, so verifying does not itself produce a key.
- LinkedIn OpenID Connect would establish control of the LinkedIn account, not prove every profile claim
- No LinkedIn scraping or public-profile lookup
- Operator policy and a server-side issuance boundary before a hosted key is granted
- A revocable bearer key for the account that redeems it
Release integrity · 0.1.0-beta.1
Built from commit a5ae7fb545d5. These builds carry no Authenticode signature, so the SHA-256 below is the only integrity check available to you.
Alelyon-Setup-0.1.0-beta.1.exe · 232.3 MB
2f74bbbfea04536533ac7c64db076440ab55e8dd5eb7ead11712b2df76051b76Alelyon-0.1.0-beta.1-win64.zip · 222.2 MB
b522bd2c03655391f6716741426bebba9cf3d981fb30ec4e345f15d526a2a82d
On Windows: certutil -hashfile <file> SHA256. A digest that does not match is the protection working — do not run the file, and report it.
Replay the evidence you actually have.
alelyon-os is published separately from the Terminal and the planned hosted service. Its verifier can replay supported receipts against supplied inputs and policy. An authenticated result still needs a public key obtained out of band: the receipt can detect revision of committed inputs, but it does not prove that a producer did not invent bad inputs at capture.
pip install alelyon-osInstalls the alelyon-verify command. Runalelyon-verify selftest to exercise the bundled conformance fixtures without a network connection.