PRODUCTS & SYSTEMS · 2026 · VERIFICATION AUDIT · EXTERNAL REPLAY PENDING
A corrected evaluator reproduced the result again on the same machine. I still did not call that external reproduction. No different operator or environment has replayed the sealed package, and the Vero maintainers have not confirmed the correction. An official bug, score, leaderboard result or endorsement remains unverified.
The Unicode and Combined branches were kept in separate HOLD packages. This note withholds proof content and private source details; it records the missing evidence that prevented promotion.
Evaluator correction
locally supported
Same-host rerun
internal evidence
Outside replay
none
Maintainer confirmation
none
A local correction is not an upstream correction
The audit revisited how the evaluator handled the selected route, separated the proposed correction from a failing control, and performed clean local reruns plus dependency and ablation checks.
The private packages support that local account. They do not determine whether the upstream implementation is officially defective, whether the correction matches maintainer intent, or whether another environment produces the same result. “Locally audited evaluator correction” is therefore the bounded description.
A second run on one host shares the first run’s blind spots
Repeating the commands on one host can test consistency. It also shares installation state, caches, operating-system assumptions and the same operator’s decisions. A systematic error may survive both runs.
The readiness gate labels those reruns as internal reproduction. Only a sealed replay by another operator or environment counts as external. Because that gate is still open, no journal record was created and the result was not generalized beyond the frozen local instance.
Running the command twice is useful; handing the evidence to someone who did not share the first run’s assumptions is a different test.
What would release the HOLD
One requirement is a no-edit replay of the sealed package by a different operator or environment, retaining the environment fingerprint, command transcript and integrity checks. The other is factual maintainer confirmation of the evaluator delta and its relationship to the named instance.
Neither request asks for endorsement of a paper. They are the minimum checks needed to turn a local interpretation into externally supported fact. Until then, Unicode and Combined remain distinct from each other and from any official Vero result.
Project record
- Period: 2026
- Activity: evaluator-path audit and correction, local reruns, dependency and ablation checks, readiness-gate design
- Internal evidence: separate Unicode and Combined HOLD packages, verifier and same-host replay records
- External validation: no different-operator replay and no maintainer confirmation
- Final outcome: local audit complete; promotion paused pending external reproduction
- Not established: official bug status, upstream approval, leaderboard acceptance or Vero-wide generalization