Neranu
NERANU QUALITY STANDARD

What must be true
before we release a pack.

The production system stays inside Neranu. Every licensed environment ships with its evidence.

Request the full standard
THE RULE

An environment is not finished when the reference solution passes.

It is finished when correct work is rewarded, shortcuts are rejected, clean replays agree, rights are documented, and independent reviewers sign off.

RELEASE REQUIREMENTS

Six forms of evidence.

Deterministic reward

Every outcome resolves to an executable pass or fail contract.

Required
Known-bad rejection

Adversarial and shortcut solutions are tested before release.

Required
Reproducible runtime

Pinned, resettable containers with the network disabled by default.

Required
Independent review

Two reviewers inspect specification, solution, tests, and difficulty.

Required
Rights record

Every source and derived artifact is tied to a documented grant of rights.

Required
Baseline evidence

Multiple model snapshots establish difficulty and expose failure modes.

Required
INTERNAL PRODUCTION

Private source in. Verified environments out.

This is Neranu's operational responsibility, not a workflow the customer has to manage.

01
Acquire

Secure rights to private source material with usable technical depth.

02
Produce

Experts turn real failure surfaces into resettable, reward-bearing environments.

03
Verify

Neranu tests determinism, shortcut resistance, provenance, and difficulty.

04
Release

A frozen pack is licensed for training, evaluation, or managed access.

RELEASE RECORD
ENVIRONMENTAtomic cache recovery
Candidate 01 · revision 8
Reference executionPassed
Known-bad rejection12 / 12
Deterministic replay10 / 10
Independent review2 / 2
Rights recordComplete
Runtime isolationPassed
The evidence ships with the pack.

Customers can audit the release record before running an environment in training or evaluation.

Request access