NEO AI · Evaluations

NEO AI Evaluations · Official Test No. 2

Verify this report yourself.

Check the published file against its fingerprint, inspect the timestamps and the ledger record, and see exactly what each third party confirmed. Everything runs on your device: nothing is sent to NEO AI and no AI model is called.

Superseded by edition 2Verify the current edition →

NEO AI Evaluations · Official Test No. 2

Official title
NEOLABS - Official LILI Capability Test No. 2 - Public Edition
Report identifier
test-2
Published
18 November 2026
Version
Edition 1 · 18 November 2026
Manifest fingerprint
a58336b0134bd4387051c185113ee187fdbfe2b28edeae29be7276a82a08cea0

The Public Edition was sealed under the programme's former name, NEOLABS. Its file and fingerprint are unchanged.

1 · The file

Is your copy the registered one?

Any change to the registered file can be detected by checking it against its published fingerprint.

Published fingerprint (SHA-256)

149736a95c717e5482c5060c1168e5dbceff79dfe2cbf6fcd5bccf1ea5e2362b

File neolabs-official-test-2-public-edition.pdf, 802,048 bytes. This fingerprint is written in the manifest, which is signed through Sigstore and time-stamped by FreeTSA.

Download report
Check it with one command
shasum -a 256 neolabs-official-test-2-public-edition.pdf
# Windows: certutil -hashfile neolabs-official-test-2-public-edition.pdf SHA256

Compare a PDF on your device

Choose the PDF you received. Its fingerprint is computed here, in your browser; the file never leaves your device.

2 · External proofs

What each service confirmed, for this edition.

Open each proof directly. A service confirms only what it covers: a date, a signature or the integrity of a record, never the performance itself.

Operated by NEO AIIntegrity checkable by anyone

Proof Ledger

NEO AI (built-in register; not a third party)

Role. The hash-chained, append-only register of NEO AI. Each entry contains the fingerprint of the one before it.

What it confirms. Proof Ledger entry no. 1285 has not changed since it was sealed, and it is chained to every entry before it. It holds the fingerprint of all 170 answers and 396 judgements of the test.

Applies to. Official Test No. 2: Proof Ledger entry no. 1285 (results of 170 answers and 396 judgements)

Scope. Operated by NEO AI: on its own it proves integrity, not a date. The date comes from DigiCert.

Technical detail
Entry
No. 1285 · sealed 18 November 2026, 12:10:44 UTC
Hash
b6aec2b0fd46d143fac82b8ba9c63e0edf960084c93b2fbb24456fd2baedb7f2
Previous hash
cdf86806c642e1438b1f34cc5987022e8b20301a9bf3ab61be773894ce1cc756
Results digest
fb70d29bf897f490f7e131efa6bf54a3b80ee30fde3d8693c5a59682e23a8c5b

Check it yourself, without NEO AI:

node verify-entry.mjs ledger-entry-1285.json
Independent third partyTimestamp confirmed

DigiCert (official site, opens a new tab)

DigiCert, Inc. - public certificate authority

Role. A public certificate authority that issues RFC 3161 time-stamps.

What it confirms. The fingerprint of Proof Ledger entry no. 1285 existed, unchanged, on 18 November 2026 at 12:10:44 UTC.

Applies to. Official Test No. 2: the hash of Proof Ledger entry no. 1285

Scope. DigiCert certifies a date for a fingerprint. It has not reviewed the report, the tasks or the scores.

Independent third partyTimestamp confirmed

FreeTSA (official site, opens a new tab)

FreeTSA (freetsa.org) - free RFC 3161 time-stamp authority

Role. A free, community-run time-stamp authority (RFC 3161).

What it confirms. The manifest of the evidence pack existed at the stated time. The manifest lists the PDF report, the per-task results and the ledger entry with their SHA-256 fingerprints.

Applies to. Official Test No. 2, evidence pack edition 1: the manifest a58336b0134bd438… (PDF report, per-task results, ledger entry)

Scope. Certifies a date for the manifest. It does not review its content.

Independent third partyFile integrity verified

Sigstore (Fulcio and Rekor) (official site, opens a new tab)

Sigstore - open-source project of the OpenSSF, Linux Foundation

Role. Fulcio gives the public GitHub workflow a short-lived signing certificate. Rekor records the signature in a public, append-only transparency log.

What it confirms. The manifest was signed by the public workflow of github.com/myneogroup-ai/neolabs-proofs, and that signature is recorded in the public Rekor log.

Applies to. Official Test No. 2, evidence pack edition 1: the manifest a58336b0134bd438… (PDF report, per-task results, ledger entry)

Scope. Confirms who signed the manifest and that it is unchanged since. It does not judge the figures inside it.

Technical detail
Signer identity
https://github.com/myneogroup-ai/neolabs-proofs/.github/workflows/proofs.yml@refs/heads/main
Rekor log index
4020917910
Logged at
20 November 2026, 07:13:53 UTC
Data signed
manifest a58336b0134bd4387051c185113ee187fdbfe2b28edeae29be7276a82a08cea0

Check it yourself, without NEO AI:

cosign verify-blob --bundle proofs/manifest.sigstore.json --certificate-identity https://github.com/myneogroup-ai/neolabs-proofs/.github/workflows/proofs.yml@refs/heads/main --certificate-oidc-issuer https://token.actions.githubusercontent.com proofs/manifest.jcs
Independent third partyProvenance attested

GitHub Artifact Attestations (official site, opens a new tab)

GitHub, Inc. (through Sigstore)

Role. Signed build provenance issued by GitHub Actions and recorded in the Rekor log.

What it confirms. The published verifier and scorer (verify/*.mjs) come from the public workflow of the neolabs-proofs repository, at a given commit.

Applies to. The published verifier and scorer of the public proof repository (verify/*.mjs)

Scope. Confirms where the verification code comes from, not that the tested system performs well.

Technical detail
Checked
2026-11-20: GitHub attestations API: 5 provenance attestations for verify/*.mjs, recorded in Rekor (log index 4022392754 for score.mjs).

Check it yourself, without NEO AI:

gh attestation verify verify/score.mjs -R myneogroup-ai/neolabs-proofs
Independent third partyTimestamp confirmed

OpenTimestamps (Bitcoin) (official site, opens a new tab)

OpenTimestamps - open protocol and public calendars, anchored in Bitcoin

Role. A free, open time-stamping protocol anchored in the Bitcoin blockchain, with no company to trust.

What it confirms. Once confirmed: the manifest existed before a given Bitcoin block.

Applies to. Official Test No. 2, evidence pack edition 1: the manifest a58336b0134bd438… (PDF report, per-task results, ledger entry)

Scope. Confirms a date only, with no company to trust. Anyone can check it on their own node with ots verify.

Technical detail
Bitcoin block
976709
Data certified
manifest a58336b0134bd4387051c185113ee187fdbfe2b28edeae29be7276a82a08cea0
Checked
20 November 2026, 09:33:35 UTC

Check it yourself, without NEO AI:

ots verify proofs/manifest.jcs.ots
Public hostPublic

Public proof repository (GitHub) (official site, opens a new tab)

Published by NEO TECH LABS TECHNOLOGY L.L.C. on GitHub

Role. Hosts the evidence packs, the verifier and the workflow that signs and time-stamps them, with their full public history. Code under MIT, data under CC BY 4.0.

What it confirms. Nothing by itself: it is where anyone can download the files and rerun the checks offline (node verify/cli.mjs verify).

Applies to. Every edition of the evidence pack and the code that verifies it

Scope. A host, not a certifier.

Not yet performed

Shown so that nothing is implied: these services or reviews are planned or waiting for a decision. None of them has confirmed anything yet.

  • Not yet performedSoftware Heritage (opens a new tab)Permanent archive of the public proof repository. Built into the publication workflow; not yet requested.
  • Not yet performedZenodo / DataCite (DOI) (opens a new tab)A permanent identifier (DOI) for each evidence pack. Built into the publication workflow and rehearsed; no permanent deposit yet.
  • Not yet performedHugging Face (opens a new tab)The per-task public results as an open dataset. Planned, not yet built.
  • Not yet performedOSF preregistration (opens a new tab)The protocol of a test registered before it runs, from Official Test No. 3. Planned.
  • Not yet performeddrand (League of Entropy) (opens a new tab)Public randomness to draw the audited sample. Built into the publication workflow; used from Official Test No. 3.
  • Not yet performedExternal auditNot yet performed. No external party has audited a test.
  • Not yet performedIndependent replicationNot yet performed. No outside party has reproduced a test.

Checking a document is not validating its results.

A

Verifying a document

A fingerprint (SHA-256) is published for each file. Recompute it on your copy: if it is the same, the file is exactly the registered one. Any change to the registered file can be detected by checking it against its published fingerprint.

Done by: you, in your browser or with one command.

B

Dating and registering it

A time-stamp authority or a public log confirms that a fingerprint existed at a given time and was signed by a given identity. It confirms only what its service covers: a date or a signature, not the content.

Done by: DigiCert, FreeTSA, Sigstore, OpenTimestamps.

C

Validating the results

Only an outside party that runs the published protocol and obtains comparable results confirms the measured performance. Checking a document does not do that.

State: not yet performed. No third party has reproduced or audited a test.

3 · All checks

Every check, run now in your browser.

The files of the pack against their fingerprints, the dates against the time-stamps, and the published figures recomputed from the per-task results. A check never reports more than it did.

Checking the files...

Verify a downloaded copy of the pack instead

The same checks run offline from the public repository: node verify/cli.mjs verify packs/test-2-v1

Report signed and time-stamped; scores recomputable from the published data where the checks above say "Verified". These checks do not replace an independent validation of performance: none has been performed yet.

5 · Versions

Every public edition, at a permanent address.

  1. Edition 2 · 20 November 2026 Current

    Report text only (Public Edition PDF): the six comparisons not shown besides judged quality are the exact-match comparisons, not time-to-first-text comparisons. Figures changed: no.

    Manifest d98d2df7d7eadfcf0175d4f9e927830d96471b917020476c03fdb857b77ad833 · PDF 108b44330f0d5a81b566d14bb8f067980720c09e053368943ec15c74a6915779

  2. Edition 1 · 18 November 2026 Superseded

    First published edition.

    Manifest a58336b0134bd4387051c185113ee187fdbfe2b28edeae29be7276a82a08cea0 · PDF 149736a95c717e5482c5060c1168e5dbceff79dfe2cbf6fcd5bccf1ea5e2362b

When a new edition is published, its manifest names the fingerprint of the one it replaces, and receives its own signature and time-stamps. Earlier editions stay online with their proofs at their permanent addresses: each file always matches the fingerprint of its own edition.